Support Tip: Config Service DeltaSynchronization process fails with timeout exception

Here’s an issue we’ve run across a time or two here in support so I thought it would be worth documenting just in case you happen to see it. What happens is that the System Center 2012 Operations Manager Config Service DeltaSynchronization process fails and you see an Event ID 29181 that mentions a timeout exception in the Operations Manager event log on one of the management servers. Here’s an example:

Log Name:      Operations Manager
Source:        OpsMgr Management Configuration
Event ID:      29181
Level:         Error
User:          N/A
Computer:      server.domain.com
Description:
OpsMgr Management Configuration Service failed to execute 'DeltaSynchronization' engine work item due to the following exception
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperationTimeoutException: Exception of type 'Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperationTimeoutException' was thrown.
  at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle)
  at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation operation, String operationName)
  at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.WriteConfigurationDelta(IConfigurationDeltaDataSet dataSet)
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.TransferData(String watermark)
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.ExecuteSharedWorkItem()
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.SharedWorkItem.ExecuteWorkItem()
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigServiceEngineWorkItem.Execute()

This error can occur when the Delta Synchronization process is not able to build configuration within its configured timeout of 30 seconds which could be due to a large instance space.

If this is the case, we can increase the timeout using the following method on all management servers:

1. Make a backup of "x:\Program Files\System Center 2012\Operations Manager\Server\ConfigService.Config"
2. Increase the timeout values in ConfigService.config for the following:
   • <OperationTimeout DefaultTimeoutSeconds="30"> to 300 seconds
   • <Operation Name="GetEntityChangeDeltaList" TimeoutSeconds="180" /> to 300 seconds.
3. Restart the configuration service

In most cases this should allow enough time for the synchronization process to complete.

Chris Wallen| Senior Support Escalation Engineer | Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/