Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, February 8, 2017 5:06 AM
I'm currently using VS2013 for SSDT for BI develpoment. I am now trying to upgrade to VS2015 and keep running into this same setup failure.
- KB3022398 : The system cannot find the file specified.
Microsoft Visual Studio Enterprise 2015 : One or more arguments are not correct.
KB3022398LP : User cancelled installation.
Looking at the log file, this seems to be the error:
"
[20B8:1EBC][2017-02-08T15:17:01]i304: Verified existing payload: kb3022398_enu at path: C:\SQL 2016 files\packages\kb3022398\kb3022398-enu.msp.
[20B8:1EBC][2017-02-08T15:17:01]i338: Acquiring package: kb3022398_enu, payload: kb3022398_enu, copy from: C:\SQL 2016 files\packages\kb3022398\kb3022398-enu.msp
[20E4:20E0][2017-02-08T15:17:04]e000: Error 0x80070002: Failed to install MSP package.
[20E4:20E0][2017-02-08T15:17:04]e000: Error 0x80070002: Failed to execute MSP package.
[20B8:19FC][2017-02-08T15:17:04]e000: Error 0x80070002: Failed to configure per-machine MSP package."
Why is this happening? And how can it be quickly resolved, as I have already lost a full day trying to resolve this installation?
Thanks.
All replies (4)
Thursday, February 9, 2017 6:27 AM
Hi ScottKaysee,
Thank you for posting in MSDN forum.
>>I'm currently using VS2013 for SSDT for BI develpoment. I am now trying to upgrade to VS2015
The VS 2013 and VS 2015 are two separate products, which means that VS 2013 couldn't be upgrade to VS 2015, you need to install it additionally.
Please check a similar issue blog:
Description
The problem is that one of the packages installed with VS2015 is upgraded (Windows Installer major upgrade MSI) but also patched (MSP). Setup determined that the patch applies and also scheduled the MSI to be upgraded, which occured first. By the time the MSP was to be installed, its target product was no longer installed (different ProductCode and ProductVersion) and erred.
Further more, The error code "0x80070002" often means the file or folder cannot found, since you didn't mention the way you installed VS (Web installer or ISO), so we need to repair your VS corrupted packages.
Here are my suggestions:
1.Try with the Visual Studio Uninstaller to uninstall visual studio completely (please run it a couple times)
2. Download a VS 2015 With Update 3 ISO from https://www.visualstudio.com/downloads/
3. Use the FCIV.exe tool to check the SHA1 value of the ISO,
compare with official hash value from:
https://www.visualstudio.com/en-us/productinfo/vs2015-sha-vs
4. After making sure the ISO is ok, use it to re-install VS.
Before and during the installation, please remember to disable AV-software and firewall, clean %Temp% folder, install all the Windows update.
If any problem persists, please feel free to tell me.
Best Regards,
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Monday, February 13, 2017 1:14 AM | 1 vote
Turns out my issues were due to an application called AppSense that our IT department uses to manage desktop environments. Disabling AppSense allowed the VS2015 installation to work as per normal.
Monday, February 13, 2017 2:03 AM
Hi Scott,
Thank you for your update.
It's really kind of you for sharing your result and solution here.
You could reply as answer. It would be easier for other members who encounter similar question as yours, and find your solution.
Have a nice day :)
Best Regards,
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Tuesday, July 11, 2017 11:38 PM
Stopping the AppSense services on our machines fixed this too.
Very frustrating - this answer saved us!