Mark Gabarra's Blog : WCF Setup Issues

Stale machine.config entries referencing ‘2.0.0.0’ versions of .NET Framework 3.0 assemblies blocks installation of the .NET Framework 3.0 package

Mark Gabarra — Wed, 20 Sep 2006 21:12:00 GMT

Craig McLuckie just compiled documentation that details work around instructions for common .NET Framework 3.0 setup issues. You can find the full document on the WCF Forums titled Common WCF RC1 Installation Issues. The following is a WCF specific issue captured as a separate blog post here for ease of search.

Problem: Stale machine.config entries referencing ‘2.0.0.0’ versions of .NET Framework 3.0 assemblies blocks installation of the .NET Framework 3.0 package

Source of Issue:

Some preview (CTP and Beta) versions of the .NET Framework 3.0 did not remove all machine.config entries on uninstall. These entries that reference the 2.0.0.0 version of ‘System.ServiceModel.dll’ in the machine.config file blocks the correct installation of the .NET Framework 3.0.

Symptoms:

1. .NET Framework 3.0 installation fails with this error:

“ERROR_INSTALL_FAILURE 1603 Fatal error during installation”

2. An error event appears in the application event log that references problems running ServiceModelReg.exe.

3. The setup log file titled ‘dd_wcf_retCA*’ in the users %temp% directory location contains an entry indicating problems running ServiceModelReg.exe.

Either the event log entry, or the setup log entry may contain an exception that looks like the following (timestamp 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)

Resolution:

Remove the stale machine.config entries by hand

a. From a command window run “notepad %windir%\microsoft.net\framework\v2.0.50727\config\machine.config”

b. Remove any xml nodes and child nodes that reference System.ServiceModel.dll

c. If you are running a 64 bit machine, you will also need to edit “%windir%\Microsoft.NET\Framework64\v2.0.50727\config\machine.config” if it exists and perform the same action.

Note: This issue only occurs if you have installed an early preview version of the .NET Framework 3.0 on your system before installing the RC1 version.

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

IIS Metabase Corruption Blocks Installation of the .NET Framework 3.0 package

Mark Gabarra — Wed, 20 Sep 2006 21:11:00 GMT

Problem: IIS Metabase Corruption Blocks Installation of the .NET Framework 3.0 package

Source of Issue:

IIS metabase corruption on a system with IIS installed blocks the installation of the .NET Framework 3.0.

Symptoms:

1. .NET Framework 3.0 installation fails with this error:

“ERROR_INSTALL_FAILURE 1603 Fatal error during installation”

2. An error event appears in the application event log that reference failure to register WCF scriptmaps (source of the event would be listed as System.ServiceModel.Install.dll 3.0.0.0).

3. The setup logs in user’s %temp% directory contain references to failure to register WCF scriptmaps

Either the event log, or the setup log may contain an exception stack trace with the following details:

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 funtionality, disable the IISAdmin service and reregister ServiceModel.

Resolution:

1. Uninstall IIS.

2. Re-install IIS.

3. Re-run .NET Framework 3.0 setup

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Some WCF Registry Keys are not deleted on uninstall of some preview .NET Framework 3.0 (‘WinFX’) releases

Mark Gabarra — Wed, 20 Sep 2006 21:03:00 GMT

Problem: Some WCF Registry Keys are not deleted on uninstall of some preview .NET Framework 3.0 (‘WinFX’) releases.

Source of Issue:

Some preview (CTP and Beta) versions of the .NET Framework 3.0 ("WinFX") did not remove all registry keys on uninstall. The presence of these keys on a system blocks the correct installation of the .NET Framework 3.0.

Symptoms:

1. .NET Framework 3.0 installation fails with this error:

“ERROR_INSTALL_FAILURE 1603 Fatal error during installation”

2. The following registry keys exit in the registry after uninstall:

i. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC Bridge 3.0.0.0\Performance

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

iii. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelOperation 3.0.0.0\Performance

iv. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelService 3.0.0.0\Performance

v. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMSvcHost 3.0.0.0\Performance

Resolution:

Run the uninstall tool (recommended), or follow the following instructions:

1. First try rebooting. There is more than one issue that can destabilize performance counters on a machine and rebooting can fix some of those issues, and is the safest way to fix those issues rather than manual registry intervention.

2. If that does not work, try the following:

b. Check the following registry keys:

i. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC Bridge 3.0.0.0\Performance

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

iii. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelOperation 3.0.0.0\Performance

iv. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelService 3.0.0.0\Performance

v. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMSvcHost 3.0.0.0\Performance

c. If those registry keys are empty or only include values named “Wbem*”, then you are in a partially removed state.

d. To fix, simply delete the parent registry keys of any of the above empty keys. For example, if the key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelEndpoint 3.0.0.0\Performance” is empty, you should delete “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceModelEndpoint 3.0.0.0”.

Note: This issue only occurs if you have installed an early preview version of the .NET Framework 3.0 on your system before installing the RC1 version. The uninstall bug that results in this behavior has been addressed in current .NET Framework 3.0 preview editions.

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

ServiceModelReg and FileLoadException

Mark Gabarra — Tue, 08 Aug 2006 04:43:00 GMT

When ServiceModelReg runs and checks if a given section [group] handler is installed, if that handler points to a type in an assembly that cannot be found, ServiceModelReg may fail with a FileLoadFoundException. This has happened in the past when customers have not completely removed a previous version of WCF before installing a new drop (i.e. removed the files but not the machine.config settings). The new version's ServiceModelReg.exe cannot clean up the prior version entries nor can it register the new version's entries. The only workaround is to hand edit machine.config.

You can be certain that you have run into this issue if you run ServiceModelReg by hand with verbose output and get an error message similar to the following:

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)

File name: 'System.ServiceModel, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

The important thing to note from the error message surrounds the version of the System.ServiceModel assembly; 2.0.0.0. The version of the System.ServiceModel assembly released should read 3.0.0.0. The version 2.0.0.0 assembly was released as early CTP (Customer Technology Preview) releases. Thus, you would encounter this issue on a machine where an early CTP release of WCF was installed, but not completely uninstalled, prior to installing the official release of WCF.

To fix this issue you will need to hand edit your machine.config file. You will find this file at: %windir%\Microsoft.NET\Framework\v2.0.50727\config\machine.config (or if you are running on a 64-bit machine you will also have to edit %windir%\Microsoft.NET\Framework64\v2.0.50727\config\machine.config if it exists). Find any XML nodes in this file that refer to “System.ServiceModel, Version=2.0.0.0”, delete them and any child nodes. Save the file and retry running ServiceModelReg.exe. That should fix the issue.

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

ServiceModelReg, WCF Setup, and Exceptions...Oh my!

Mark Gabarra — Tue, 08 Aug 2006 04:33:00 GMT

During WCF install, or while troubleshooting a WCF configuration related issue, you may have run into our WCF registration tool ServiceModelReg. This tool provides a command line mechanism for you to manage the WCF configuration of a machine. Most often you will use this tool to bring your box back to a default install state, or explicitly manage the .svc WebHost registration on IIS 5.1 and IIS 6.0.

As the WCF product heads to release, as the owner of ServiceModelReg, I have started to receive interesting failure reports. It seems that the WCF team could not reproduce the myriad of ways a machine could become unstable, or even corrupt, during our validation of ServiceModelReg. In some cases, we could not reproduce a certain corruption even after receiving a detailed report of the issue.

To help ease the pain as I learn of these issue, I will add a small description and workaround (when available) here. In some cases, we will learn of an issue too late to address it before we release, and it may not make the servicing bar (that whole tradeoff argument) to warrant a hotfix release. Hopefully, I can provide enough information to clearly identify a particular issue and outline steps to either work around or address the underlying problem.

If you run into an issue that you do not see described here, feel free to let me know.

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

WCF July CTP Missing Config Intellisense

Mark Gabarra — Wed, 02 Aug 2006 02:21:00 GMT

Recently, I received a question about the WCF configuration intellisense in our July CTP release from Nilesh Pagare. After installing the July WCF CTP Nilesh no longer had our configuration intellisense when modifying either app.config or web.config files in Visual Studio. The dotnetconfig.xsd file did not include the System.ServiceModel configuration schema.

After tracking down the correct contact regarding the installation of WCF configuration intellisense, it appears that you have run into an unfortunate known issue. Here are the details that have been provided to me, which include a work around:

VS extension should be installed for Intellisense to work correctly.

However, we did not ship such an extension package with July CTP. This is the major problem.

To workaround, one can install the VS extension for Jun CTP on the July CTP with the following command line (direct install will fail):

msiexec /i vsextwfx.msi WRC_INSTALLED_OVERRIDE=1

The VS extension package for June CTP can be found at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=1a994549-94cb-4f61-903d-a8c8e453eef4&DisplayLang=en

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm