Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Mar 12, 2011 02:14 AM by wil2
Mar 10, 2011 12:53 AM|LINK
I am getting really fed up trying to install MVC 3, I have bloged about the problem here - http://blog.williamhilsum.com/2011/03/error-0x80070643-installing-aspnet-mvc.html
To sum it up, after ages of digging around, I finally managed to track it down to the
I am not sure what to do
next as I have tried to repair, remove, force delete as well as a few other things, but I am just getting no where.
I have a normal system - I upgraded to Windows 7 SP1 yesterday, VS 2010 SP1 today and have never had any Betas installed apart from Web Matrix which I uninstalled today (after the VS SP1).
I can not see anything that sticks out and was just wondering if anyone can help.
The exact details of the error is:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action WebConfigCA_Remove, location: C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET
Web Pages\v1.0\WebConfig\WebConfigCA.exe, command: -u
=== Logging stopped: 10/03/2011 01:22:31 ===
Mar 11, 2011 05:37 AM|LINK
I think you also posted this on microsoft connect. I added a workaround there, but here it is for good measure:
We experienced the same issue - I was unable to install because an old version of "Microsoft ASP.NET Web Pages" was still installed. However, the uninstaller was failing for the old version.
It seems VS 2010 SP 1 modifies the framework paths in the registry to contain a trailing backslash, which causes the uninstaller for the old version of "Microsoft ASP.NET Web Pages" to fail.
Steps to workaround are:
1. Remove the trailing backslash from the following registry keys:
2. Uninstalled the old version of "Microsoft ASP.NET Web Pages".
3. Add the trailing backslash back to those keys.
4. Install MVC 3.
Hope that helps!
Mar 11, 2011 06:50 AM|LINK
@Matt.... I think I love you!!!!!
I have been trying to do this on and off for 2 days and I was a few hours away from reinstalling windows.
This teaches me for playing with a beta!
Thank you so much!
How on earth did you find this out? Also, should I put the slashes back in after reinstalling?
Mar 11, 2011 07:40 AM|LINK
Glad to have helped!
I put the registry keys back to their original values after I uninstalled the old version of "ASP.NET Web Pages", so yes I'd recommend you add the slashes back.
We found this out when we noticed the part of the uninstall that was failing was a call to "WebConfigCA.exe" (using the msiexec command line to enable logging). We looked up the stack trace of the failure in Event Viewer, and then used Reflector to see the
code that was failing. The code was concatenating the value of the framework path in the registry with "\config", which was leading to a path with two backslashes, which failed a validity check in the code. We checked a machine without VS 2010 SP1 installed
and there wasn't a backslash on the registry key - this seemed to explain why the uninstall would have worked before SP1 was installed but not after.
From there we came up with the workaround of temporarily removing the slashes while uninstalling the old version of "ASP.NET Web Pages".
Mar 11, 2011 08:06 AM|LINK
Thanks - I have put the slashes back in now.
I saw the basic log in the temp folder, saw the event log error with the unhandled exception and even did reflector, however I never got as far as to seeing what variable was actually going in to it other than just calling it with `-u`
But thanks again - I have updated the blog and given you credit - http://blog.williamhilsum.com/2011/03/error-0x80070643-installing-aspnet-mvc.html (If you have
a blog/want your name linked to any page, please let me know.)
Mar 11, 2011 08:48 PM|LINK
I managed to re-install using this post first and then this http://blog.mjjames.co.uk/2010/12/mvc-3-rc2-install-error-0x80070643.html
Mar 12, 2011 02:09 AM|LINK
It truly surprises me that you had many problems installing MVC 3. The installation should be pretty straight forward and easy.
Did you manage to have the issue resolved?
Mar 12, 2011 02:14 AM|LINK
Yes - Please see Matts first reply - marked as answer.
It was down to the SP1 install changing registry paths. It is all installed and working now!