When you run the Flush Health Service State and Cache task in Microsoft System Center 2012 Operations Manager, the task may not complete and time out. What happens is that after you run the task, the agent health service is restarted in a clean state in which the record of the task is removed. Therefore, the agent does not realize that a flush task is already running and flushes the health service state and cache again. This behavior can result in an infinite loop that eventually causes a time-out.
This issue is fixed in System Center 2012 R2 but for all the details see the following:
KB2889317 - The Flush Health Service State and Cache task times out in System Center 2012 Operations Manager (http://support.microsoft.com/kb/2889317)
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
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/