![cannot install microsoft visual studio 2017 in windows 10 cannot install microsoft visual studio 2017 in windows 10](https://visualstudio.microsoft.com/wp-content/uploads/2019/04/MacbookwithASPNET.png)
(I know, if you are doing this you already know this, but I just feel it was missing from my notes.)įrom the Administrative Command Prompt, execute the following command SSDT-Setup-ENU.exe /layout, which will download the install files to the folder in which you run the command. Then open an Administrator: Command Prompt using a right click on the command prompt menu item. All show in the log that is returned, that the EXE Failed to execute the package.Īfter some R&D I was able to get the setup working with the help of a community post on Stack Overflow from last year !! This article details the steps I used to get these tools installed in more detail.įirst, Download and save the SSDT-Setup-ENU.exe package a directory with a short path, I used C:\SSDT as this will not be the last time I do this. The errors will vary with most of the time the return is that a path is too long. When Installing SSDT for Visual Studio 2017, I normally select all the options or even just the SQL Server Integration Services, many times only to have it return in failure. Note: These steps worked for me and I cannot guarantee that this will solve your issue. The Setup Failed screen referenced an install log and all failed with rough the same error as shown below.
![cannot install microsoft visual studio 2017 in windows 10 cannot install microsoft visual studio 2017 in windows 10](https://venturebeat.com/wp-content/uploads/2019/03/configuration-manager-intune.png)
I had the same setup failure, no matter what configuration I was using. In order to develop SQL Server Integration Services (SSIS) packages for Azure Data factory v2, I needed to install the SSDT on a workstation and also a number of developer workstations at a client site. There is an odd error when trying to install SQL Server Data Tools (SSDT), either as a stand alone, or adding to an instance of Visual Studio 2017.