I was trying to build a new machine for my demo purposes and wanted to install everything possible related to Data. SQL Server Data Tools (SSDT) is also needed to complete the package. I downloaded it from here.
But I was not able to install it! I followed various articles to find the log location. I was able to find it in the TEMP directory. Here is the error which I saw in those files.
[064D:1C0F][2018-02-01T09:07:40]e020: Error 0x80070002: Failed attempt to download URL: ‘https://go.microsoft.com/fwlink/?LinkId=863932&clcid=0x409’ to: ‘C:\Users\Pinal\AppData\Local\Temp\{FC0F49F2-4875-48A0-A25C-98A0A44F1A67}\SSDTISSingleton’
[064D:1C0F][2018-02-01T09:07:40]e020: Error 0x80070002: Failed to acquire payload from: ‘https://go.microsoft.com/fwlink/?LinkId=863932&clcid=0x409’ to working path: ‘C:\Users\Pinal\AppData\Local\Temp\{FC0F49F2-4875-48A0-A25C-98A0A44F1A67}\SSDTISSingleton’
It was strange that I was able to open this link using internet explorer and google chrome and it was downloading SSDTISSingleton.msi
WORKAROUND/SOLUTION
After a lot of search on the internet, I found the solution which worked for me. Truly speaking, I was cursing myself to make such a silly mistake during installation. I should have selected the option Run As Administrator when I installed SSDT setup. Well, that was it, honestly, the solution is very simple.
Hopefully, someone would be able to find this solution quicker on this blog. If it does, please comment and let me know.
Reference:Â Pinal Dave (https://blog.sqlauthority.com)
2 Comments. Leave new
Selecting download ‘Download SSDT for Visual Studio 2017 (15.5.2)’ ,
from webpage https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017 ,
then trying to install the ‘Download SSDT for Visual Studio 2017 (15.5.2)’ , I get system locale mismatch between Operating system and SSDT. If I right-click the ‘SSDT-Setup-ENU’ file, select Run as administrator, install works fine.
I ran across similar issues with 15.7 SSDT for Visual Studio 2017. I’m on Windows Server 2017 and am getting the same errors listed in this blog. The caveat is thatI am running as administrator and it is failing at the same spot. Several searches mentions running in c:\temp and trying /layout followed by running again as /repair.
The /repair does not present a repair button to click. Could be tied to the CEIP non-option that reaches out to Microsoft to give them feedback?