Select the product you need help with

Error message when you install Microsoft Dynamics CRM 4.0: "The type initializer for 'Microsoft.CRM.LocatorService' threw an exception" or "Action Microsoft.crm.setup.common.registerasyncserviceAction failed"

Article ID: 949092 - View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

When you install Microsoft Dynamics CRM 4.0, you receive one of the following error messages:

The type initializer for 'Microsoft.CRM.LocatorService' threw an exception. The type initializer for 'Microsoft.CRM.ServerLocatorService' threw an exception. Input string was not in a correct format.
Note If you receive this error message, you also receive the following error message in Microsoft Application Error Reporting:
System.TypeInitializationException: The type initializer for 'Microsoft.Crm.LocatorService' threw an exception. --->
System.TypeInitializationException: The type initializer for 'Microsoft.Crm.ServerLocatorService' threw an exception. --->
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Int32.Parse(String s, IFormatProvider provider)
at System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)
at System.Diagnostics.PerformanceCounterLib.get_NameTable()
at System.Diagnostics.PerformanceCounterLib.get_CategoryTable()
at System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category)
at System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName)
at System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName)
at Microsoft.Crm.LocatorCache.CreatePerformanceCounters()
at Microsoft.Crm.LocatorCache..ctor()
at Microsoft.Crm.ServerLocatorService..cctor()
--- End of inner exception stack trace ---
at Microsoft.Crm.LocatorService..ctor()
at Microsoft.Crm.CrmTraceSettings.LoadScaleGroupSettings()
at Microsoft.Crm.LocatorService..ctor()
at Microsoft.Crm.LocatorService..cctor()
--- End of inner exception stack trace ---
at Microsoft.Crm.Utility.RetrieveScaleGroupId()
at Microsoft.Crm.CrmKeySetting.Initialize(Boolean loadSettingsFromConfigDB, Guid scaleGroupId, ConfigSku configSku)
at Microsoft.Crm.CrmKeySetting..ctor(CrmKeyType crmKeyType, Boolean loadSettingsFromConfigDB, Boolean useCachedValues, Guid scaleGroupId, ConfigSku configSku)
at Microsoft.Crm.CrmKeySetting.CreateKeySetting(CrmKeyType keyType, ConfigSku configSku)
at Microsoft.Crm.Setup.Server.ServerSetup.Initialize()
at Microsoft.Crm.Setup.Server.ServerSetup.InternalMain(String[] args)
“Action Microsoft.Crm.Setup.Common.RegisterAsyncServiceAction failed. An exception occurred during the Commit phase of the installation. This exception will be ignored and installation will continue. However, the application might not function correctly after installation is complete. Time out has expired and the operation has not been completed.”
In addition to the error above you will see the following in the crm40svrSetup.log
12:31:07| Info| Executing Install action: Microsoft.Crm.Setup.Common.RegisterAsyncServiceAction 12:32:38| Error| System.Exception: Action Microsoft.Crm.Setup.Common.RegisterAsyncServiceAction failed. ---> System.Configuration.Install.InstallException: An exception occurred during the Commit phase of the installation. This exception will be ignored and installation will continue. However, the application might not function correctly after installation is complete. ---> System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at Microsoft.Crm.ExtendedServiceInstaller.StartService(Object sender, InstallEventArgs e) at System.Configuration.Install.InstallEventHandler.Invoke(Object sender, InstallEventArgs e) at System.Configuration.Install.Installer.OnCommitted(IDictionary savedState) at System.Configuration.Install.Installer.Commit(IDictionary savedState) --- End of inner exception stack trace --- at System.Configuration.Install.Installer.Commit(IDictionary savedState) at System.Configuration.Install.AssemblyInstaller.Commit(IDictionary savedState) at Microsoft.Crm.Setup.Common.RegisterAsyncServiceAction.Do(IDictionary parameters) at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo) --- End of inner exception stack trace ---, Error, RetryCancel, Option1
Note If you receive this error message, the following events are logged in the Application log on the Microsoft Dynamics CRM 4.0 server:
Event 1
Event ID 3012 of the LoadPerf source
Event 2
Event ID 3011 of the LoadPerf source

Back to the top | Give Feedback

CAUSE

This problem occurs because of one of the following causes.

A problem with the performance counters on the server. Therefore, the installation is unable to add performance counters to the performance counter libraries.
The installation of .Net Framework 3.0 is corrupt.
Missing or Duplicate Service Principle Name (SPN).

Back to the top | Give Feedback

RESOLUTION

To resolve this problem complete one of the following methods.

Rebuild the performance counter libraries.
Configure the appropriate HTTP SPNs for NETBIOS, FQDN or Host Headers. Configure the appropriate MSSQLSvc SPNs for NETBIOS and FQDN. Remove duplicate HTTP or MSSQLSvc SPNs.

For more information about how to rebuild the performance counter libraries, click the following article number to view the article in the Microsoft Knowledge Base:

300956

(http://support.microsoft.com/kb/300956/ )

How to manually rebuild performance counter library values