Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Workarounds for some .NET Framework 3.5 beta 2 install issues we have seen so far

Workarounds for some .NET Framework 3.5 beta 2 install issues we have seen so far

  • Comments 5

Since the release of the .NET Framework 3.5 beta 2 a couple of weeks ago, we have run into a few installation issues that I wanted to let folks know about.  The good news is that all of these issues will be fixed in time for the final release of the .NET Framework 3.5, but the bad news is that they can cause beta 2 to fail to install and you may need to apply one of the workarounds listed below.

Issue 1: The IIS Admin Service is disabled

The .NET Framework 3.5 beta 2 will fail to install if setup is being run on a system that has IIS installed, but the IIS Admin service is set to the disabled state.

This issue will cause the following information to be written to the verbose MSI log file for the .NET Framework 3.5 component (named %temp%\dd_net_framework35_MSI*.txt):

DDSet_Error: CFxInstaller::SetupComponents SetupScriptMaps failed. Error code: 0x80070422

You can use the following steps to work around this issue:

  1. Click on the Start menu, choose Run, type services.msc and click OK
  2. In the Services snap-in that appears, locate the service named IIS Admin Service, right-click on it and choose Properties
  3. In the Startup type drop-down, change the value from Disabled to Automatic and click OK to save the changes
  4. Re-run .NET Framework 3.5 beta 2 setup
  5. (optionally) Change the Startup type back to Disabled after .NET Framework 3.5 beta 2 setup completes

Issue 2: The IIS Admin Service is not installed

The .NET Framework 3.5 beta 2 will fail to install if setup is being run on a system that has parts of IIS installed, but does not have the IIS Admin Service installed.

This issue will cause the following information to be written to the verbose MSI log file for the .NET Framework 3.5 component (named %temp%\dd_net_framework35_MSI*.txt):

DDSet_Error: CFxInstaller::SetupComponents SetupScriptMaps failed. Error code: 0x80070424

You can use the following steps to work around this issue:

  1. Click on the Start menu, choose Run, type appwiz.cpl and click OK
  2. In the Add/Remove Programs control panel (or the Programs and Features control panel in Windows Vista), choose the item on the left side that is named Add/Remove Windows Features (or Turn Windows Features on or off in Windows Vista)
  3. Locate the Internet Information Services (IIS) feature and choose to either fully uninstall IIS, or choose to install the World Wide Web Service feature of IIS
  4. Re-run .NET Framework 3.5 beta 2 setup
  5. (optionally) Go back to the Add/Remove Windows Features control panel and change the install state of IIS features back to what they were before step 3 above after .NET Framework 3.5 beta 2 setup completes

Issue 3: Insufficient privileges to modify application host config file

In some cases, the .NET Framework 3.5 beta 2 will fail to install if the user account that setup is running under does not have permission to modify IIS configuration files located at %windir%\system32\inetsrv\config.

This issue can cause one of the following entries to be written to the verbose MSI log file for the .NET Framework 3.5 component (named %temp%\dd_net_framework35_MSI*.txt):

DDSet_Error: CWebServerHandlers::Install m_spAppHostAdminManager->CommitChanges failed. Error code: 0x80070002

DDSet_Error: CWebServerHandlers::Install m_spAppHostAdminManager->CommitChanges failed. Error code: 0x80070005

We know of an issue with the NoImpersonate attribute not being set for this custom action that could cause this type of error, but have had trouble reproducing this issue in our test labs.  In most cases, you can use the following steps to work around this issue:

  1. Click on the Start menu, choose All Programs, then Accessories, then right-click on the Command Prompt item and choose Run as administrator
  2. Run .NET Framework 3.5 beta 2 setup from the administrator cmd prompt that appears

If the above work around does not help, you can use the following steps as an alternative:

  1. Click on the Start menu, choose Run, type appwiz.cpl and click OK
  2. In the Add/Remove Programs control panel (or the Programs and Features control panel in Windows Vista), choose the item on the left side that is named Add/Remove Windows Features (or Turn Windows Features on or off in Windows Vista)
  3. Locate the Internet Information Services (IIS) feature and choose to fully uninstall IIS
  4. Re-run .NET Framework 3.5 beta 2 setup
  5. (optionally) Go back to the Add/Remove Windows Features control panel and re-install IIS after .NET Framework 3.5 beta 2 setup completes
Page 1 of 1 (5 items)
Leave a Comment
  • Please add 8 and 7 and type the answer here:
  • Post