Add-on components that enhance and customize the Visual Studio integrated development environment
Hi @Chitluri, Durga ,
The 0x80070643 you see in the bundle log is only the generic relay of exit code 0x643 coming from VSIXBootstrapper.exe, so the outer log will never tell us the real reason. The actual failure detail is written to the inner log at %temp%\SsdtisSetup\Microsoft.DataTools.IntegrationServices_{Timestamp}_ISVsix.log, and also to the log file path you can see being passed via the /logFile argument in the command line you quoted. I suggest opening that ISVsix log first, since it will state the exact VSIX error.
That said, based on your setup I strongly suspect the root cause is missing prerequisites in the offline layout. For air-gapped installations, the SSIS Projects extension has three documented prerequisite components that must be present in the Visual Studio offline layout, and the Data workload alone does not guarantee all of them. The one most commonly missing is the .NET Framework 4.7 targeting pack, and its absence causes the VSIX prerequisite resolution to fail exactly the way you describe, including the manual VSIXInstaller.exe /admin attempt failing to register.
Here is what I recommend:
- On your internet-connected machine, update your offline layout so it explicitly includes the required components:
vs_professional.exe --layout D:\VSLayout --lang en-US --noWeb --add Microsoft.VisualStudio.Workload.Data --add Microsoft.VisualStudio.Component.Roslyn.LanguageServices --add Microsoft.VisualStudio.Component.CoreEditor --add Microsoft.Net.Component.4.7.TargetingPack - Transfer the updated layout to the server, run setup from the layout to update the existing F: instance, and reboot.
- Rerun Microsoft.DataTools.IntegrationServices.exe as Administrator. The installer respects whichever registered instance it targets, so the custom F: install path itself is not a problem; there is no separate procedure needed to bind the extension to a non-default drive.
- If it still fails, please check the
ISVsixlog mentioned above. If it contains "Pre-check verification failed with warning(s):AnotherInstallationRunning", Windows Installer is busy with another operation (Windows Server servicing tasks often hold it on fresh builds); wait for it to finish and retry. - As an additional sanity check, run vswhere -all -products * from C:\Program Files (x86)\Microsoft Visual Studio\Installer and confirm only the expected F: instance is registered. A previous
InstallCleanuppass can occasionally leave a stale instance registration that the VSIX bootstrapper resolves instead of the live one.
Regarding SSRS and SSAS in the same offline environment: those two are plain VSIX extensions. You can download Microsoft.DataTools.ReportingServices.vsix and Microsoft.DataTools.AnalysisServices.vsix from the Visual Studio Marketplace on a connected machine, transfer them, and install with "F:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\VSIXInstaller.exe" /admin <file.vsix>. They will install cleanly once the same prerequisites above are present. Also note that Visual Studio Professional supports offline activation via product key, so your edition choice is correct for an air-gapped server.
If the ISVsix log shows something other than a prerequisite or AnotherInstallationRunning issue, please share the relevant error lines from it and I will take a closer look.
Reference documentation:
If you found my response helpful or informative, I would greatly appreciate it if you could provide feedback by interacting with the system or leaving a comment below.
Thank you.