Error installing SSDT for VS2017: Failed to acquire payload

UPDATE 03-09-2018: The newest version of SSDT for Visual Studio 2017 works correct, and can now be installed. See the post here

I recently had to install VS2017 with KingswaySoft on a computer, and I ran into some issues in regard to the installation. After I had installed the Visual Studio software, I needed to install SSDT (15.5.0).

When I attempted to install the software, it threw an error, saying a file was missing. In the log, I could see the installer was attempting to download a file from Microsofts’ website. This was the error thrown:

Error 0x80070002: Failed attempt to download URL: ‘’ to: ‘C:\Users\tpl\AppData\Local\Temp\{E0D5BAFF-C46F-44AB-990B-C9CD44FC1B7B}\SSISOneDesigner2016’

Error 0x80070002: Failed to acquire payload from: ‘’ to working path: ‘C:\Users\tpl\AppData\Local\Temp\{E0D5BAFF-C46F-44AB-990B-C9CD44FC1B7B}\SSISOneDesigner2016’

Failed to acquire payload: SSISOneDesigner2016 to working path: C:\Users\tpl\AppData\Local\Temp\{E0D5BAFF-C46F-44AB-990B-C9CD44FC1B7B}\SSISOneDesigner2016, error: 0x80070002.

I checked if others had this issue, and after a while, the only suggested fix, was to run the installer as Administrator – this didnt help. I then tried following the link in the error, and I could freely download the software manually, and install it.

After the install, I tried running the installer for SSDT again, but it threw a new error:

Acquiring package: SQL_AS_AMO2012, payload: SQL_AS_AMO2012, download from:

Error 0x80070002: Failed attempt to download URL: ‘’ to: ‘C:\Users\tpl\AppData\Local\Temp\{7F3383A1-EA49-44F1-8CE0-B6501986CB91}\SQL_AS_AMO2012’

So, this is atleast progress, as it is new failing in a new download. I tried following this aswell, and I was then able to manually download and install the SQL_AS_AMO2012 file. After running the SSDT installer again, it then again threw a new error – this time, it was a registryfile it couldnt open.
The configuration registry key could not be opened (0x800703F3)

After a few days taking some steps forward and backwards, I ended up simply installing VS2015. I have successfully installed VS2017 previously, but this time it simply didnt work out.

If anyone knows what the issue I was facing was, feel free to contact me with a fix/workaround.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *