Visual Studio and .NET Framework Home
Installation of .NET Framework 3.5.1 Features/WCF Activation/HTTP Activation fails with error 0x80070643 when .NET 4 beta 1 is installed
5/21/2009 8:50:37 AM
User(s) can reproduce this bug
Installation of .NET Framework 3.5.1 Features/WCF Activation/HTTP Activation fails with error 0x80070643 when .NET 4 beta 1 is installed.
Uninstalling .NET 4 beta 1 and KB958488, installed as part of .NET 4 beta 1, resolves the problem.
.NET Framework 4 Beta 1
Windows Server 2008 R2
Operating System Language
Steps to Reproduce
1. Install .NET 4 beta 1 on Server 2008 R2 RC (build 7100)
2. Try to install HTTP Activation under WCF Activation in .NET Framework 3.5.1 Features
Installation fails with error 0x80070643.
After uninstalling .NET 4 beta 1 and KB958488 wich is installed as part of .NET 4 beta 1, installation of HTTP Activation works again.
Installation of .NET 3.5.1 HTTP Activation should still work even if .NET Framework 4 was installed first.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 6/22/2009 at 11:52 AM
Thank you for your feedback.
We have reviewed this issue you submitted and have fixed it for Beta 2.
As a workaround to this issue for Beta 1, you can do the following:
- Uninstalling .NET 4 Beta 1 and KB958488 which was installed as part of the Beta 1 installation.
- Enable activation services
- Reinstall .NET 4 Beta 1
on 5/29/2009 at 5:30 PM
Thank you for using .NET Framework 4.0 providing feedback on the WCF and WF products. This bug is currently going to the feature team who will directly investigate the issue you are reporting. We are very eager to receive this feedback and will take care to address your input. Feel free to provide comments on the Connect site if you have concerns on the resolution of this bug.
on 5/22/2009 at 4:06 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
to post a workaround.
Please enter a workaround.
© 2014 Microsoft