How to troubleshoot windows Communication Foundation (WCF) Installation Problems

Some Windows Communication Foundation registry keys cannot be repaired by performing the MSI repair operation on. NET Framework 3.0.

If you delete any of the following registry keys:

• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ servicemodelservice 3.0.0.0

• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ servicemodeloperation 3.0.0.0
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ servicemodelendpoint 3.0.0.0
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ smsvchost 3.0.0.0
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSDTC bridge 3.0.0.0

Then"Control Panel"In"Add/delete programs"When the. NET Framework 3.0 installer started in the applet is fixed, these items are not re-created. To re-create these items correctly, you must uninstall and reinstall. NET Framework 3.0.

WMI Service Termination uption prevents installation of the Windows Communication Foundation WMI provider during the installation of the. NET Framework 3.0 package

WMI Service resume uption may prevent installation of the Windows Communication Foundation WMI provider. During the installation process, the Windows Communication Foundation installer cannot use the mofcomp.exe component to register the WCF. mof file. The following lists the symptoms:

1. . NET Framework 3.0 is successfully installed, but the wcf wmi provider is not registered.

2. An error event is displayed in the Application Event Log, which indicates that a problem occurs when the WMI provider of WCF is registered or mofcomp.exe is running.
3. The Installation Log File named dd_wcf_rechloroform * in the user's % Temp % directory contains references to the failure to register the wcf wmi provider.
4. One of the following exceptions may be listed in the event log or installation trace log file:

   Servicemodelreg [11: 09: 59: 046]: system. applicationexception: Use "E: \ windows \ Microsoft. net \ framework \ V3.0 \ Windows Communication Foundation \ servicemodel. MOF "execution E: \ windows \ system32 \ WBEM \ mofcomp.exe unexpected result 3

   Or:

   Servicemodelreg [07: 19: 33: 843]: system. typeinitializationexception: "system. Management. managementpath" type Initial Value Setting item raises an exception. ---> System. runtime. interopservices. comexception (0x80040154): failed to retrieve components whose CLSID is {CF4CC405-E2C5-4DDD-B3CE-5E7582D8C9FA} in the com class factory because of the following error: 80040154.

   Or:

   Servicemodelreg [07: 19: 32: 750]: system. Io. filenotfoundexception: the file cannot be loaded or the Assembly "C: \ windows \ system32 \ WBEM \ mofcomp.exe" or one of its dependencies. The system cannot find the specified file.

   File Name: "C: \ windows \ system32 \ WBEM \ mofcomp.exe"

To solve the problem described above, follow these steps.

1. Run WMI diagnosis utility, version 2.0 (WMI diagnostic utility version 2.0) to repair the WMI Service. For more information about using this tool, see WMI diagnosis utility (WMI
   Diagnostic utility) topic.

Use"Control Panel"In"Add/delete programs"The applet fixes. NET Framework 3.0 installation, or uninstalls/reinstalls. NET Framework 3.0.

After installing. NET Framework 3.5, the. NET Framework 3.0 will remove the configuration elements introduced by. NET Framework 3.5 in machine. config.

If you fix. NET Framework 3.5 after installing. NET Framework 3.0, the configuration elements introduced by. NET Framework 3.5 are removed from machine. config. However, Web. config remains unchanged. The solution is to use ARP to fix. NET Framework 3.5, or use the workflow service registration tool (wfservicesreg.exe)
And/CSwitch is used in combination.

The workflow service registration tool (wfservicesreg.exe) can be found in % WinDir % \ microsoft. net \ framework \ v3.5 \ or % WinDir % \ Microsoft. NET \ framework64 \ v3.5 \.

After installing. NET Framework 3.5, configure IIS correctly for WCF/WF webhost

If the. NET Framework 3.5 installation fails to configure other IIS configuration settings related to WCF, an error is recorded in the installation log and the operation continues. Any attempt to run the workflowservices application will fail because necessary configuration settings are missing. For example, loading xoml or the rule service fails.

To solve this problem, set the workflow service registration tool (wfservicesreg.exe) and/CTo correctly configure the IIS script ing on the computer. Workflow service registration tool (wfservicesreg.exe)
You can find it in % WinDir % \ microsoft. net \ framework \ v3.5 \ or % WinDir % \ Microsoft. NET \ framework64 \ v3.5 \.

The system. servicemodel. Activation. httpmodule type cannot be loaded from the assembly "system. servicemodel, version 3.0.0.0, culture = neutral, publickeytoken = b77a5c561934e089"

This error occurs if. NET Framework 4 is installed and. NET Framework 3.5 wcf http activation is enabled later. To solve this problem, run the following command line at the Visual Studio 2010 Command Prompt:

aspnet_regiis.exe -i -enable