System Center Data Access service or the System Center Management Configuration service fail to start with a time-out error

This issue occurs because the system cannot retrieve trusted and untrusted certificate trust lists (CTLs). If the system does not have access to Windows Update, either because the system is not connected to the Internet or because Windows Update is blocked by firewall rules, the network retrieval times out before the service can continue its startup procedure. In some cases, this network retrieval time-out may exceed the service startup time-out of 30 seconds. If a service cannot report that startup completed after 30 seconds, the service control manager (SCM) stops the service. 

To work around this problem, configure the computer so that the network does not retrieve trusted and untrusted CTLs.

Unblock the updated URLs in the firewall or proxy, or disable CRL checking for the Data Access service and the Management Configuration service. 

Open one of the following files in a text editor:

• For the Data Access service: Microsoft.Mom.Sdk.ServiceHost.exe.config
• For the Management Configuration service: Microsoft.Mom.ConfigServiceHost.exe.config (in Systems Mangaer) or cshost.exe.config (in Operations Manager)

To disable CRL checking, add the following line in the <runtime> section:

<generatePublisherEvidence enabled="false"/>

The following example shows this tag being added for System Center 2012 Operations Manager in the Cshost.exe.config file.

<runtime>

<generatePublisherEvidence enabled="false"/>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<dependentAssembly>

<assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService" publicKeyToken="31bf3856ad364e35" />

<publisherPolicy apply="no" />

<bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />

</dependentAssembly>

<publisherPolicy apply="no" />

<probing privatePath="" />

</assemblyBinding>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<dependentAssembly>

<assemblyIdentity name="Microsoft.Mom.Common" publicKeyToken="31bf3856ad364e35" />

<publisherPolicy apply="no" />

<bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />

</dependentAssembly>

<publisherPolicy apply="no" />

<probing privatePath="" />

</assemblyBinding>

<gcServer enabled="true"/> 

</runtime>

The following example shows the same added tag in the configuration file for System Center Operations Manager 2007 R2 (Microsoft.Mom.Sdk.ServiceHost.exe.config):

<?xml version="1.0" encoding="utf-8"?>

<configuration>

<runtime>

<generatePublisherEvidence enabled="false"/>

<gcServer enabled="true"/> 

</runtime>

The two *.config files can be found in the following directories: 

• System Center Operations Manager 2007 R2: %ProgramFiles%\System Center Operations Manager 2007
• System Center Service Manager 2010: %ProgramFiles%\System Center Service Manager 2010
• SystemCenter 2012 Operations Manager: %ProgramFiles%\System Center 2012\Operations Manager\Server
• System Center 2012 Service Manager: %ProgramFiles%\System Center 2012\Service Manager