.NET 3.0 Installation Known Issues

Mahesh Chand
17y
27k
0
0

Blog

1. Download failure when downloading and installing .NET Framework 3.0.

The download and installation of a .NET Framework 3.0 intermittently fails.

To resolve this issue

Rerun dotnetfx3setup.exe from the Web site and try the download again. Click here for more troubleshooting information about download errors.

– or –

Install the full redistributable package dotnetfx3.exe (x86) or dotnetfx3_x64.exe (x64). You can find these redistributable packages on the .NET Framework 3.0 download location.

2. Antivirus applications that are configured to clean the Temp folder will cause setup to fail if setup needs to reboot.

If setup needs to reboot, and the antivirus application is set to clean the Temp directory on launch, necessary setup files will be deleted and setup will fail with a program-not-found error.

To resolve this issue

Change your antivirus applications configuration to not clean the Temp folder on launch or reboot before running .NET Framework 3.0 setup. Consult your antivirus documentation for the steps to accomplish this.

3. Launching Maintenance Mode from Add or Remove Programs can take several minutes and might give the appearance that setup has failed.

If you have other processes running when you launch Maintenance Mode, such as virus-scanning software, these processes can slow setup considerably and give the appearance that setup has failed.

To resolve this issue

Be patient. There is no workaround. Setup has not failed.

4. No Add Remove Programs entry to uninstall Windows Workflow Foundation.

You may get the "Please uninstall Windows Workflow Foundation" error when installing .NET Framework 3.0 , but there is no ARP entry for Windows Workflow Foundation to uninstall the product.

To resolve this issue

Run the uninstall tool for pre-release version at: http://www.microsoft.com/downloads/details.aspx?FamilyId=AAE7FC63-D405-4E13-909F-E85AA9E66146

5. .NET Framework 3.0 installation may overwrite the localized version of MSXML6

On Windows XP SP2 and Windows 2003 SP1, if you have a localized version of MSXML6 previously installed, .NET Framework 3.0 installation will overwrite the localized MXSML6 with the English version.

To resolve this issue

Reinstall the localized version of MSXML6 after installing .NET Framework 3.0 .

6. Installation error when installing .NET Framework 3.0 packages on Vista

Windows Vista comes with .NET Framework 3.0. There is no separate installation package required. The standalone .NET Framework 3.0 packages are not supported on Vista.

7. Possible issues when upgrading from a pre-release version of the .NET Framework 3.0 (previously WinFX 3.0)

This section describes issues you may encounter if you previously installed a pre-release (CTP and Beta) version of the .NET Framework 3.0 and want to remove it to upgrade to the RTM version.

To uninstall .NET Framework 3.0, please uninstall through Add and Remove Program (ARP) in the Control Panel. If uninstalling from ARP does not solve the issue, you can review the following:

Run the Uninstall Tool
The .NET Framework 3.0 Uninstall Tool available is available at http://www.microsoft.com/downloads/details.aspx?FamilyId=AAE7FC63-D405-4E13-909F-E85AA9E66146. This tool resolves many uninstall problems and is the best first step in attempting to resolve uninstall/reinstall problems. Details on the correct use of the tool are listed on the download page.

If you cannot run the tool or if it does not resolve your issue, review the Known Issues and Workarounds section below for potential solutions.

Note: These install issues occur only if you have installed an early pre-release version of the .NET Framework 3.0 on your system before installing the RTM version. The issues that cause these behaviors have been addressed in recent .NET Framework 3.0 pre-release editions.

Known Issues and Workarounds

7.1“Microsoft Digital Identity Service” (idsvc) is not deleted on uninstall

On uninstall, some pre-release versions of the .NET Framework 3.0 did not correctly delete all services they created. The presence of one of these services on a system blocks the installation of the .NET Framework 3.0. The installation will fail with this error:
ERROR_INSTALL_FAILURE 1603 Fatal error during installation
Also, one of the %temp%\dd_wcf_retCA*.txt log files will show the following:

ServiceModelReg [15:48:08:041]: Installing: Microsoft Digital Identity Service (idsvc)
ServiceModelReg [15:48:08:073]: Error: System.ComponentModel.Win32Exception: The name is already in use as either a service name or a service display name

To resolve this issue

Run the uninstall tool at: http://www.microsoft.com/downloads/details.aspx?FamilyId=AAE7FC63-D405-4E13-909F-E85AA9E66146

If the issue persists:
Open a command prompt.

Click Start.
Click All Programs.
Click Accessories.
Click Command Prompt.
In the command prompt, type:
sc delete “InfoCard Service”
Reboot the machine.
Restart the .NET Framework 3.0 installation.

7.2 Some WCF perf counter registry keys are not deleted on uninstall of some pre-release versions of the .NET Framework 3.0

Some pre-release versions of the .NET Framework 3.0 did not remove all perf counter registry keys on uninstall. The presence of these keys blocks the installation of the .NET Framework 3.0. The installation fails with this error:
“ERROR_INSTALL_FAILURE 1603 Fatal error during installation”
The following keys may still exist in the registry after uninstall:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC Bridge 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelEndpoint 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelOperation 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelService 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMSvcHost 3.0.0.0\Performance

To resolve this issue

Run the uninstall tool at: http://www.microsoft.com/downloads/details.aspx?FamilyId=AAE7FC63-D405-4E13-909F-E85AA9E66146

If the issue persists, try rebooting. Many issues can destabilize the performance counters. Rebooting can fix some of those issues and is safer than manually editing the registry. If that does not solve the problem, check the following registry keys. Delete the parent registry keys of any of the following that are empty or whose values contain “Wbem*”:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC Bridge 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelEndpoint 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelOperation 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelService 3.0.0.0\Performance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMSvcHost 3.0.0.0\Performance

For example, if this key is empty:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelEndpoint 3.0.0.0\Performance

you should delete:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelEndpoint 3.0.0.0”

7.3 Stale machine.config entries that reference “2.0.0.0” versions of .NET Framework 3.0 assemblies block installation

Some pre-release versions of the .NET Framework 3.0 did not remove all machine.config entries on uninstall. Any entries that reference the 2.0.0.0 version of “System.ServiceModel.dll” in the machine.config file will block the installation of the .NET Framework 3.0. The installation fails with this error:
“ERROR_INSTALL_FAILURE 1603 Fatal error during installation”
In addition:

An error event appears in the application event log that references problems running ServiceModelReg.exe.
The setup log file titled “dd_wcf_retCA*” in the user’s %temp% directory location contains an entry that indicates problems running ServiceModelReg.exe.
Either the event log entry or the setup log entry may have an exception similar to the following (time stamp will vary):
ServiceModelReg [16:21:10:656]: Error: System.IO.FileLoadException: Could not load file or assembly 'System.ServiceModel, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

To resolve this issue

Remove the stale machine.config entries by hand:

From a command window, run “notepad %windir%\microsoft.net\framework\v2.0.50727\config\machine.config”
Remove any XML nodes and child nodes that reference System.ServiceModel.dll.
If you are running on a 64-bit machine and the following config file exists:
“%windir%\Microsoft.NET\Framework64\v2.0.50727\config\machine.config”
edit the file to remove any xml nodes and child nodes that reference System.ServiceModel.dll.

7.4 May not be able to web host WCF services if a pre-RC1 version of WCF was previously installed

If you installed a previous version of the .NET Framework 3.0 while IIS was installed, when you upgrade to the RTM version of the .NET Framework 3.0 you may have difficulty accessing WCF services that are IIS hosted using .svc files. On computers running Windows Server 2003, accessing an .svc extension from the browser may return a “404: Page Not Found” error. On computers running Windows XP, the .svc content may be displayed as plain text.

This is due to an issue with WCF script map registrations in a previous release.

To resolve this issue

There are three ways to work around this issue:

Download the unsupported tool, CleanIISScriptMaps.exe from http://wcf.netfx3.com/files/folders/product_team/entry5648.aspx. Run the tool from a command console without any arguments.
Uninstall and reinstall IIS or re-create your Web sites:
1. Uninstall IIS and reinstall it so that the IIS Metabase is refreshed. Then run the WCF install tool manually to re-register the WCF scriptmaps:
  “%windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe” /r /y
2. If you are running Windows 2003 Server, you may be able to resolve the problem by deleting the “Default Web Site” and re-creating it.
Install .svc manually as a temporary workaround:
You can run the following command to install .svc mapping manually. However, this refreshes the IIS Metabase for existing sites. "%windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" /s:W3SVC

7.5 IIS metabase corruption blocks installation of the .NET Framework 3.0

If you installed a previous version of the .NET Framework 3.0 while IIS was installed, it’s possible that the IIS metabase was corrupted. This may block the installation of the .NET Framework 3.0.
You can identify this issue in the following ways:

The installation fails with this error:
“ERROR_INSTALL_FAILURE 1603 Fatal error during installation”
An error event appears in the application event log that references a failure to register WCF scriptmaps. The source of the event is System.ServiceModel.Install.dll 3.0.0.0.
The setup logs in your %temp% directory will also contain references to a failure to register WCF scriptmaps.
Either the event log or the setup log may contain the following exception stack trace:
System.ApplicationException: ServiceModelReg.exe has detected a possible corruption in the IIS metabase that prevents the registration of the ServiceModel IIS scriptmaps. Please either fix the IIS metabase corruption, or, if you do not desire ServiceModel WebHost functionality, disable the IISAdmin service and reregister ServiceModel.

To resolve this issue