SSDT Installation for VS2017 Team Explorer Fails

Question

I am attempting to install SSDT v15.6.0 into an existing Visual Studio Team Explorer 2017 instance. When I run the SSDT installer, I can select Visual Studio Team Explorer 2017 from this list of existing Visual Studio instances. If I do not choose a any options (other than the required SQL Server Database option). The installation completes successfully.

If I however attempt to pick any/all of the other options the installation fails. From looking at the log files, it appears that the installation of the VSIX is failing due to a required component missing.

Below is the snippet of the SSDT-Setup installation log file which indicates that the VSIX failed to install.

[167C:1A6C][2018-05-16T15:40:41]i301: Applying execute package: Microsoft.DataTools.IntegrationServices, action: Install, path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe" /q /admin /instanceIds:"68f392fc" /logFile:"C:\Users\golaat\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20180516153141_009_Microsoft.DataTools.IntegrationServices.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"'
[167C:1A6C][2018-05-16T15:41:13]e000: Error 0x80131500: Process returned error: 0x80131500
[167C:1A6C][2018-05-16T15:41:13]e000: Error 0x80131500: Failed to execute EXE package.
[1D80:1858][2018-05-16T15:41:13]e000: Error 0x80131500: Failed to configure per-machine EXE package.

Looking at the log file for the installation of the VSIX it seems like a required component is missing:

 5/16/2018 3:41:05 PM - BEGIN: Targetting Visual Studio Team Explorer 2017,15.0.27428.2043
 5/16/2018 3:41:05 PM - BEGIN: Execute batch install
 5/16/2018 3:41:08 PM - BEGIN: Preparing extension Microsoft Integration Services Projects
 5/16/2018 3:41:08 PM - Loading extension: Microsoft Integration Services Projects
 5/16/2018 3:41:10 PM - JSON file loaded
 5/16/2018 3:41:10 PM - The dependent package of 'Component.D1B09713-C12E-43CC-9EF4-6562298285AB,version=1.4' cannot be found: Microsoft.VisualStudio.Component.SQL.SSDT,version=[15.0,16.0).
 5/16/2018 3:41:10 PM - END: Execute batch install
 5/16/2018 3:41:10 PM - END: Installing
 5/16/2018 3:41:10 PM - Common folder deleted: C:\Users\golaat\AppData\Local\Temp\s0ggmkmo.cwz
 5/16/2018 3:41:10 PM - Microsoft.VisualStudio.Setup.Dependencies.DependencyGraphConstructionException: The dependent package of 'Component.D1B09713-C12E-43CC-9EF4-6562298285AB,version=1.4' cannot be found: Microsoft.VisualStudio.Component.SQL.SSDT,version=[15.0,16.0).

Is there a way to identify this missing component an perhaps install it manually?

Answer 1

I found the .log file you get from the error dialog was referencing a much older version of the SSIS extension. I have visual studio community 2017 installed on the machine with the ssis extension, and it is somehow conflicting with that. I can't uninstall it, so I just put it on another machine which has not previously had SSIS on it and it worked.

To verify this, you follow the paths shown in the log file and see that they go to older SSIS payloads.

Answer 2

G'day,

To anyone reading in 2024; we were running into the following

Error 0x80131500: Process returned error: 0x80131500

As the last error in the Microsoft.DataTools.IntegrationServices_XXXXXXXX_11_ISVsix.log logfile.

We had no possible work around other than escalate privileges on the machine.

Further: the root cause was due to the strictness of our SecOps; where-in the SSIS installer attempts to create/purge shadow drives which is disallowed in our environments.

Answer 3

I found a solution, follow these steps:

1. Download SQL Server and install it. In the Feature Selection step install Integration Service

2. Now download Visual Studio installer and install .NET desktop development and Data storage and processing

3. Now run Visual Studio and go to Extensions > Manage Extensions > Online, and search for SQL Server Integration Services Projects. Download and install that

You are now good to go.

Answer 4

This is how I fixed it :

1. Run installer normally to the end and let it fail.
2. When it fails the window will have a link to the log file, open it.
3. In this log file, 1 or 2 lines before the error(Process returned error: 0x80131500) problem component location will be revealed, something like this:

[6748:674C][2020-07-29T09:44:03]i301: Applying execute package: ISVsix, action: Install, path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe" /q /admin /instanceIds:"5403e431" /logFile:"C:\Users\xxxx\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200729093525_11_ISVsix.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"

You have to combine location of the VSIXBootstrapper with vsix component location. In my case I had vsix file under C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\payload

4. Copy failing component(.vsix), in this case Microsoft.DataTools.IntegrationServices.vsix to some folder before it gets deleted. If it already got deleted then restart the installer and search for this component in parent folders.
5. Restart your computer. I was getting "Another installation running .." error before I did.
6. Go to the folder where you copied the failing component and install the .vsix manually. This time it should install normally.
7. Repeat step 1 but this time hoping it will work normally.

I hope this at least gets you in the right direction.

Answer 5

With the release of SSDT 15.7.1, Team Explorer no longer shows up as an existing Visual Studio install instance option within SSDT. At first I was concerned that the SSDT install would install a Visual Studio shell with no TFS connectivity, however this was not the case. It appears that the SSDT install of the Visual Studio shell picks up on the fact that Visual Studio Team Explorer 2017 is already installed on the machine and the SSDT Visual Studio shell instance has full TFS Connectivity!

Answer 6

This is currently broken due to a bug in Visual Studio - see this post on the Developer Community site: SSDT cannot install onto 15.7 version of Visual Studio

It'll be fixed in a forthcoming Visual Studio update, but if you can't wait for that a workaround is to completely uninstall Visual Studio and install an older version. See my answer here for instructions: https://stackoverflow.com/a/50349464/1184850