ConfigMgr 2012 MP – suspending SCOM agent/health service

Hi,
I use SCOM agent/health for our SLA reporting. I found a handful of servers last month with something like 99.9% uptime even though I knew they had been up all of the time. Looking in the Operations Manager event log I have found the following events related
to ConfigMgr 2012 -
The System Center 2012 - Operations Manager agent running on computer "XXXXXXXXXXXXX" is suspended for the following reason:
"ConfigMgr 5.00.7804.1000 - SMS_MaintenanceTaskRequests –
I am trying to understand what and why it is doing this. Presumably something in the ConfigMgr MP is trying to “fix” something with a task? However if I checked open/closed alerts for the servers involved I can’t see any type of alert getting created.
I have opened the ConfigMgr MP with “Management Pack Viewer” but can’t find any Diagnostics, Recoveries or Tasks listed. Just wondered if anyone had any idea what this was or perhaps it’s a task related to a SCOM internal MP itself? I can’t find any other examples
of the agent getting suspended whilst something gets “fixed”

Hi,
This event is telling you that the SCOM Agent is being paused for an SCCM Maintenance task (often a backup).
For more information, please refer to the link below:
Use of Disable Operations Manager alerts option in ConfigMgr
http://blog.tyang.org/2014/04/24/use-disable-operations-manager-alerts-option-configmgr/
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

CCMSetup.exe - Will not install the ConfigMgr 2012 R2 CU3 Client Agent. Logs Listed.

I have been diagnosing a few ConfigMgr logs and I discovered a few things that sparked my interest like "Reseting the WMI Repository", "Checking the WMI Namespace", and "CCMClean.exe Tool and Re-run CCMSetup.exe".
None of the above had any effect on the client's workstation. So, I figured that if I can't figure it out, I will find a MVP or ConfigMgr Admin who has remediated this issue.
<![LOG[Successfully created the ccmsetup service]LOG]!><time="14:23:28.293+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="1932" file="ccmsetup.cpp:3260">
<![LOG[==========[ ccmsetup started in process 7696 ]==========]LOG]!><time="14:23:28.358+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4740" file="ccmsetup.cpp:9441">
<![LOG[Running on platform X64]LOG]!><time="14:23:28.358+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4740" file="util.cpp:1892">
<![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="14:23:28.359+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4740" file="ccmsetup.cpp:9285">
<![LOG[Launch from folder C:\WINDOWS\ccmsetup\]LOG]!><time="14:23:28.359+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4740" file="ccmsetup.cpp:721">
<![LOG[CcmSetup version: 5.0.7958.1401]LOG]!><time="14:23:28.359+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4740" file="ccmsetup.cpp:727">
<![LOG[In ServiceMain]LOG]!><time="14:23:28.360+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4964" file="ccmsetup.cpp:3365">
<![LOG[Successfully started the ccmsetup service]LOG]!><time="14:23:28.360+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="1932" file="ccmsetup.cpp:3271">
<![LOG[Deleted file C:\WINDOWS\ccmsetup\ccmsetup.exe.download]LOG]!><time="14:23:28.362+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="1932" file="ccmsetup.cpp:9497">
<![LOG[Task 'Configuration Manager Client Upgrade Task' does not exist]LOG]!><time="14:23:28.363+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="1932" file="wintask.cpp:634">
<![LOG[CcmSetup is exiting with return code 0]LOG]!><time="14:23:28.363+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="1932" file="ccmsetup.cpp:10879">
<![LOG[Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18]LOG]!><time="14:23:28.396+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="util.cpp:1974">
<![LOG[Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice "/mp:sdlcorpwsccm02.suddenlink.cequel3.com" "/forceinstall" "smssitecode=P12" "FSP=sdlcorpwsccm02.suddenlink.cequel3.com"]LOG]!><time="14:23:28.396+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:3590">
<![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="14:23:28.396+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:3775">
<![LOG[Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice "/mp:sdlcorpwsccm02.suddenlink.cequel3.com" "/forceinstall" "smssitecode=P12" "FSP=sdlcorpwsccm02.suddenlink.cequel3.com"]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:3776">
<![LOG[SslState value: 224]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4964" file="ccmsetup.cpp:4425">
<![LOG[CCMHTTPPORT: 80]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:8621">
<![LOG[CCMHTTPSPORT: 443]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:8636">
<![LOG[CCMHTTPSSTATE: 224]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:8654">
<![LOG[CCMHTTPSCERTNAME: ]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:8672">
<![LOG[FSP: sdlcorpwsccm02.suddenlink.cequel3.com]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:8724">
<![LOG[CCMFIRSTCERT: 1]LOG]!><time="14:23:28.397+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:8782">
<![LOG[Config file: ]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4539">
<![LOG[Retry time: 10 minute(s)]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4540">
<![LOG[MSI log file: C:\WINDOWS\ccmsetup\Logs\client.msi.log]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4541">
<![LOG[MSI properties: SMSSITECODE="P12" FSP="sdlcorpwsccm02.suddenlink.cequel3.com" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4542">
<![LOG[Source List:]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4550">
<![LOG[MPs:]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4569">
<![LOG[ sdlcorpwsccm02.suddenlink.cequel3.com]LOG]!><time="14:23:28.399+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:4584">
<![LOG[No version of the client is currently detected.]LOG]!><time="14:23:28.400+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:2748">
<![LOG[Task 'Configuration Manager Client Retry Task' does not exist]LOG]!><time="14:23:28.401+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4964" file="wintask.cpp:634">
<![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="14:23:28.402+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4964" file="ccmsetup.cpp:9285">
<![LOG[Sending Fallback Status Point message to 'sdlcorpwsccm02.suddenlink.cequel3.com', STATEID='100'.]LOG]!><time="14:23:28.402+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:9760">
<![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="14:23:28.403+360" date="03-05-2015" component="ccmsetup" context="" type="2" thread="4964" file="ccmsetup.cpp:9842">
<![LOG[Params to send FSP message '5.0.7958.1401 Deployment ']LOG]!><time="14:23:28.403+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4964" file="ccmsetup.cpp:9891">
<![LOG[State message with TopicType 800 and TopicId {2CA81B64-EBF4-4E73-B1FB-836EC58B350F} has been sent to the FSP]LOG]!><time="14:23:28.476+360" date="03-05-2015" component="FSPStateMessage" context="" type="1" thread="4964" file="fsputillib.cpp:752">
<![LOG[Running as user "SYSTEM"]LOG]!><time="14:23:28.487+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:1995">
<![LOG [Sending Fallback Status Point message to 'sdlcorpwsccm02.suddenlink.cequel3.com', STATEID='328'.]LOG]!><time="14:23:28.488+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4964" file="ccmsetup.cpp:9760">
<![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="14:23:28.490+360" date="03-05-2015" component="ccmsetup" context="" type="2" thread="4964" file="ccmsetup.cpp:9842">
<![LOG[Params to send FSP message '5.0.7958.1401 Deployment Error 0x80004005']LOG]!><time="14:23:28.491+360" date="03-05-2015" component="ccmsetup" context="" type="0" thread="4964" file="ccmsetup.cpp:9891">
<![LOG[State message with TopicType 800 and TopicId {DBB1E065-465B-47CE-9221-E644FE138C68} has been sent to the FSP]LOG]!><time="14:23:28.566+360" date="03-05-2015" component="FSPStateMessage" context="" type="1" thread="4964" file="fsputillib.cpp:752">
<![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="14:23:28.568+360" date="03-05-2015" component="ccmsetup" context="" type="1" thread="4740" file="ccmsetup.cpp:10883">
If you can help me solve this issue, you would be much appreciated. :)

The FSP error is showing because our "ConfigMgr Engineers" said we didn't need it enabled. So we have our clients looking for a FSP that isn't even enabled on the ConfigMgr server.
Yes, that's not the point though. ccmsetup will try to send a message to the FSP after a failure and the thing that happens, as mentioned, right before it tried to send a message is to update the security on the ccmsetup folder which implies something went
wrong when it tried to do this.
Have you disabled your AV or other local products that may interfere with local security?
Jason | http://blog.configmgrftw.com | @jasonsandys

Event IDs 508,509 and 510 (Health Service ESE Store) on SCOM agents

Hi Team,
Many of my SCOM agents are getting the Event IDs 508,509 and 510 on them.
HealthService (2944) Health Service Store: A request to write to the file "C:\Program Files\System Center Operations Manager\Agent\Health Service State\Health Service Store\edb.log" at offset 1485312 (0x000000000016aa00) for 512 (0x00000200)
bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Because of these events I keep getting "Health Service Heartbeat Failure" Alerts in SCOM whenever these events occur on the agents. After a couple of minutes these alerts get auto resolved and closed.
Has anyone faced a similar issue and let me know what should be done here to solve the issue.
Thanks,
S K Agrawal

I am still not able to resolve the issue. But I came to know that the servers that had this issue were having some issue with the blade servers they all were hosted on and probably this is the issue they got these Event IDs.
I am closing this as a faulty hardware issue on the servers.
Thanks, S K Agrawal

SCCM 2012 R2 SMS Agent Host service crashing every 10 seconds on Secondary Site Client PCs running Win7

Hi Teem;
We are having the following issue with SCCM 2012 R2: The SMS Agent Host service keeps on crashing on Client PCs with in the Secondary site! the issue isn't happening at the primary site!
We have 3 SCCM 2012 R 2 servers: CAS & Pri @ the DataCenter site and the Secondary site in the office site.
Please advise.
Thank you.

The client is entering a loop, here are some lines of the ClientIDManagerStartup.log:
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
   HardwareID1=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   HardwareID2=6CBB0600010000FE   ClientIDManagerStartup   3/21/2014 11:11:30 AM   3760 (0x0EB0)
RegEndpoint: Spawning task to re-register in 5000 milliseconds.   ClientIDManagerStartup   3/21/2014 11:11:43 AM   3760 (0x0EB0)
[----- SHUTDOWN -----]   ClientIDManagerStartup   3/21/2014 11:11:52 AM   1428 (0x0594)
[----- STARTUP -----]   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
Machine: SCCM-TEST02   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
OS Version: 6.1   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
SCCM Client Version: 5.00.7958.1000   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
'RDV' Identity store does not support backup.   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
CCM Identity is in sync with Identity stores   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
Client is set to use HTTPS when available. The current state is 224.   ClientIDManagerStartup   3/21/2014 11:11:55 AM   1604 (0x0644)
[RegTask] - Executing registration task synchronously.   ClientIDManagerStartup   3/21/2014 11:11:56 AM   3928 (0x0F58)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100   ClientIDManagerStartup
3/21/2014 11:11:56 AM   3928 (0x0F58)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100
ClientIDManagerStartup   3/21/2014 11:11:56 AM   3928 (0x0F58)
No SMBIOS Changed   ClientIDManagerStartup   3/21/2014 11:11:56 AM   3928 (0x0F58)
SMBIOS unchanged   ClientIDManagerStartup   3/21/2014 11:11:56 AM   3928 (0x0F58)
SID unchanged   ClientIDManagerStartup   3/21/2014 11:11:56 AM   3928 (0x0F58)
HWID unchanged   ClientIDManagerStartup   3/21/2014 11:11:57 AM   3928 (0x0F58)
Windows To Go requires a minimum operating system of Windows 8   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
Windows To Go requires a minimum operating system of Windows 8   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
Computed HardwareID=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   Win32_SystemEnclosure.SerialNumber=<empty>
   Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
   Win32_BaseBoard.SerialNumber=None
   Win32_BIOS.SerialNumber=VMware-56 4d 44 fe 3d ad af 3f-d4 e8 3f 19 48 d8 e2 71
   Win32_NetworkAdapterConfiguration.MACAddress=00:0C:29:D8:E2:71   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
[RegTask] - Client is not registered. Sending registration request for GUID:1A54B9A0-E658-4F89-8D39-A47220CD5C48 ...   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
[RegTask] - Client is registered. Server assigned ClientID is GUID:1A54B9A0-E658-4F89-8D39-A47220CD5C48. Approval status 1   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
'RDV' Identity store does not support backup.   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
[RegTask] - Client is registered. Exiting.   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100   ClientIDManagerStartup
3/21/2014 11:11:59 AM   3928 (0x0F58)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100
ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
No SMBIOS Changed   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
SMBIOS unchanged   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
SID unchanged   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
HWID unchanged   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
Windows To Go requires a minimum operating system of Windows 8   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
Computed HardwareID=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   Win32_SystemEnclosure.SerialNumber=<empty>
   Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
   Win32_BaseBoard.SerialNumber=None
   Win32_BIOS.SerialNumber=VMware-56 4d 44 fe 3d ad af 3f-d4 e8 3f 19 48 d8 e2 71
   Win32_NetworkAdapterConfiguration.MACAddress=00:0C:29:D8:E2:71   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
   HardwareID1=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   HardwareID2=6CBB0600010000FE   ClientIDManagerStartup   3/21/2014 11:11:59 AM   3928 (0x0F58)
RegEndpoint: Spawning task to re-register in 60000 milliseconds.   ClientIDManagerStartup   3/21/2014 11:12:13 AM   3232 (0x0CA0)
[----- SHUTDOWN -----]   ClientIDManagerStartup   3/21/2014 11:13:16 AM   1604 (0x0644)
[----- STARTUP -----]   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
Machine: SCCM-TEST02   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
OS Version: 6.1   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
SCCM Client Version: 5.00.7958.1000   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
'RDV' Identity store does not support backup.   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
CCM Identity is in sync with Identity stores   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
Client is set to use HTTPS when available. The current state is 224.   ClientIDManagerStartup   3/21/2014 11:13:16 AM   3516 (0x0DBC)
[RegTask] - Executing registration task synchronously.   ClientIDManagerStartup   3/21/2014 11:13:19 AM   3792 (0x0ED0)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100   ClientIDManagerStartup
3/21/2014 11:13:19 AM   3792 (0x0ED0)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100
ClientIDManagerStartup   3/21/2014 11:13:19 AM   3792 (0x0ED0)
No SMBIOS Changed   ClientIDManagerStartup   3/21/2014 11:13:19 AM   3792 (0x0ED0)
SMBIOS unchanged   ClientIDManagerStartup   3/21/2014 11:13:19 AM   3792 (0x0ED0)
SID unchanged   ClientIDManagerStartup   3/21/2014 11:13:19 AM   3792 (0x0ED0)
HWID unchanged   ClientIDManagerStartup   3/21/2014 11:13:20 AM   3792 (0x0ED0)
Windows To Go requires a minimum operating system of Windows 8   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
Windows To Go requires a minimum operating system of Windows 8   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
Computed HardwareID=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   Win32_SystemEnclosure.SerialNumber=<empty>
   Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
   Win32_BaseBoard.SerialNumber=None
   Win32_BIOS.SerialNumber=VMware-56 4d 44 fe 3d ad af 3f-d4 e8 3f 19 48 d8 e2 71
   Win32_NetworkAdapterConfiguration.MACAddress=00:0C:29:D8:E2:71   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
[RegTask] - Client is not registered. Sending registration request for GUID:1A54B9A0-E658-4F89-8D39-A47220CD5C48 ...   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
[RegTask] - Client is registered. Server assigned ClientID is GUID:1A54B9A0-E658-4F89-8D39-A47220CD5C48. Approval status 1   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
'RDV' Identity store does not support backup.   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
[RegTask] - Client is registered. Exiting.   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100   ClientIDManagerStartup
3/21/2014 11:13:22 AM   3792 (0x0ED0)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000340034002000660065002000330064002000610064002000610066002000330066002D0064003400200065003800200033006600200031003900200034003800200064003800200065003200200037003100
ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
No SMBIOS Changed   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
SMBIOS unchanged   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
SID unchanged   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
HWID unchanged   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
Windows To Go requires a minimum operating system of Windows 8   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
Computed HardwareID=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   Win32_SystemEnclosure.SerialNumber=<empty>
   Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
   Win32_BaseBoard.SerialNumber=None
   Win32_BIOS.SerialNumber=VMware-56 4d 44 fe 3d ad af 3f-d4 e8 3f 19 48 d8 e2 71
   Win32_NetworkAdapterConfiguration.MACAddress=00:0C:29:D8:E2:71   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
   HardwareID1=2:ED42563E6365D1A53E55EE48D92A4CDF5D208373
   HardwareID2=6CBB0600010000FE   ClientIDManagerStartup   3/21/2014 11:13:22 AM   3792 (0x0ED0)
RegEndpoint: Spawning task to re-register in 5000 milliseconds.   ClientIDManagerStartup   3/21/2014 11:13:36 AM   3672 (0x0E58)

Health Service Heartbeat Failure Alert for Generated when one Management Server Down,

Hi,
I have Two Management Server, every one manage about 100 server, when one Management Server goes down unexpected, I receive 100 Alert for 100 Server Health Service Heartbeat Failure.
My Question, why when the Management Server down, it send that all Managed agent Health Service Heartbeat Failure?
Is there a way to change this?

SCOM 2012 agent will autofailover when primary server is down. You can check the failover management server by using the following powershell cmdlet:
#Verify Failover for Agents reporting to MS1
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"--Failover MS :: " + ($managementServer.ComputerName);
Write-Host "";
http://www.systemcentercentral.com/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr/

SCOM Agent Cache

Hi Guys,
we have SCOM 2012 SP1 in production.
I'm receiving complaints from the customer that SCOM has failed to alert on an event. Example: though the agent service is running and the threshold is breached, logical disk monitor, service monitor (many others) wont generate alerts.
When i check the health explorer, the status of monitor will be "critical" but the time stamp will be very old, say months. i then i manually flush the agent cache and restart the agent service. it works then on.
we are monitoring nearly 600 agents. one or the other agent will be having this issue. it's getting hard for me to identify which agent is having this cache problem. i want to find out such agents, so that i can take some proactive action on it.
i faced this problem in SCOM 2007, 2012 & now in SP1.
has anyone came across this type of problem? Is there any solutoin to this issue? what's the best practice to overcome this issue?
Thanks in advance,
Venu
Best regards, Venu.

Hi,
To examine Agent health with the built in views in OpsMgr:
Under Monitoring, Operations Manager, Agent, Agent Health State, there is a view for all agent, for critical agent, we can flush their cache and restart the agent service.
In addition, we can use powershell script to restart all agents' health service remotely also. By using restart-service command.
Hope the below link be helpful for you:
http://blogs.technet.com/b/kevinholman/archive/2009/10/01/fixing-troubled-agents.aspx
Regards, Yan Li

SCOM 2012 UR2 - Flush health service state causes infinite agent resets

Appearing on several of our 2008R2 servers from our SCOM 2012 UR2 environment, set up with several management servers:
If I select a monitored servers agent in the Operator Console and click the task
Flush health service state and cache, the selected agent will restart as intended.
However, it will restart again every 2-3 minutes forever ever after, unless you stop the agent service and delete the health service cache folder on the monitored server.
This is visible via the eventlog:
event 103, Healthservice. A task to reset the health service store has been submitted. The service store will be deleted and re-created.
This was never the case with our SCOM2007R2 setup and started appearing with 2012.
Have anyone seen this before? Any ideas?
Regards / Jon

Might save someone some time....
Stopping the agent, removing the "Health Service State" directory + restarting doesn't appear to help. I did this *and* deleted some agents from the console (then re-added them. We turned auto approve off) and it appears
it might have fixed it. I'll know more in the morning if this actually does the trick besides doing a full uninstall/reinstall of the agent.
If you don't know what agents are constantly restarting, search all management servers for *many* file transfers (Event ID 2110 in Ops manager event log) all to the same Instance/GUID. Execute this powershell on a managemnt server: "get-SCOMClassInstance
-Id <GUID>" to get the affected agent. Alternatively, make a SCOM rule to catch event 103 and look for many repeats from the same server/agent:
Event Type: Warning
Event Source: HealthService
Event Category: Health Service
Event ID: 103
Description:
A task to reset the health service store has been submitted. The service store will be deleted and re-created.

How is called the Services "OpsMgr Health Service" in the SCOM 2012 and Client machine?

Hi,
Can anybody tell me how is called the Services of OpsMgr Health Service in the SCOM 2012?
I have installed the agent of scom2012 on my client computer. But I dont find any agent called "OpsMgr Health Service" on the Client machine?
Regards

Hi
If you look in the services.msc window then it is listed as the System Center Management Service. This is the display name.
The actual service name is HealthService
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
The Ayman answer is god, It is called "Microsoft Monitoring Agent"

SCOM 2012 - Event ID 6024 (Launching Restart Health Service. Health Service exceeded Process\Handle Count or Private Bytes threshhold.)

I am getting event ID 6024 (LaunchRestartHealthService.js : Launching Restart Health Service. Health Service exceeded Process\Handle Count or Private Bytes threshhold.) within an interval ranging from 12-17 minutes.
I am using SCOM (2012 SP1 and 2012 R2) on Windows Server (2008 R2 / 2012 / 2012 R2).
This issue is occurring only on agent managed computer (acting as proxy and discover managed objects on other computers setting is enabled) which i am using for monitoring my device. All discovery scripts (powershell) and monitors are targeted on this agent
managed computer.
There are total 80 discoveries and 900 monitors. 55 discoveries and 550 monitors are enabled by default and rest all are disabled.
I am seeing event id 6024 frequently only on agent managed computer. Can anyone help me to resolve this issue.
Thanks,
Mukul

To fix issue 6024, you can follow below steps:
1. Open SCOM console. Go to Monitors -> Agent -> Entity Health -> Performance -> Health Service Performance -> Health Service State.
2. Double click Health Service Handle Count Threshold monitor and go to Overrides page.
3. Click Override -> For a specific object of Class: Agent. Select the affected SCOM agent QMXServer.
4. Check on the parameter Agent Performance Monitor Type - Threshold. Change the default value 2000 to an appropriate value, like 4000. You can check the Health service handle count alert in SCOM console to get the value when the alert is generated. You
can also launch the health explorer against QMXServer to check the value when the monitor state is changed from healthy to critical.
Also you can refer below links
http://blogs.technet.com/b/omx/archive/2013/10/17/health-service-restarts-on-service-manager-servers-with-scom-agents.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Can monitor SCCM agent health through SCOM, monitor logs like CCMeval and setup alerts

Can monitor SCCM agent health/inactive agents through SCOM, monitor logs like CCMeval and setup alerts

You can find some management packs here:
http://systemcenter.pinpoint.microsoft.com/en-US/applications/search/Operations-Manager-d11?q=
There are other sites as well but this is the MS page for hosting MP's. The default SCCM 2012 Management pack for SCOM 2012 is pretty functional, this page talks a little bit about it:
http://blogs.technet.com/b/kevinholman/archive/2012/12/11/monitoring-configmgr-2012-with-opsmgr.aspx
If I remember correctly, it does NOT include a lot of client monitoring but I could be wrong. It might take some custom monitor creation or management pack downloads to get exactly what you're wanting. If I can find something like that
I'll add it to this post.
A good rule of thumb that I live by with SCOM, in case the product is new to you, is to save all your changes and customizations to the SCCM management pack in a custom-created management pack.

Options for monitoring health of SCSM 2012 SP1 using SCOM 2012 SP1

Hi,
I've done some research on how to monitor SCSM using SCOM (version 2012 SP1 for both) and found two options:
Option 1 - Agent-based monitoring. With SCSM2012 SP1, it looks as though the agent is
already present (for upgrades and also for fresh installs). So it follows that SCOM will be able to monitor the health of SCSM.
Option 2 - Agentless monitoring. On the Technet
download page, 'System Requirements' section indicates compatibility with SCOM 2012 and above, and SCSM 2012 and above. Details tab says the following (emphasis mine):
This System Center Management Pack for System Center 2012 - Service Manager should be used to monitor
System Center 2012 - Service Manager, System Center 2012 R2 - Service Manager
and includes monitors for the management server as well as the Data Warehouse server. In this release of the management pack, the Data Access Service, Health Service, Configuration Service, and workflows are monitored.
So it looks like both options are viable, but I'd be interested in hearing other people's experiences of using one vs. the other. Is there any major difference in the information that's provided by agentless vs. agent-based monitoring, or are they just two
different ways of pulling the exact same information into SCOM?
Edit: Just occurred to me that SP1 isn't explicitly mentioned in the Technet article linked above under option 2. Has anyone successfully used agentless monitoring on SP1?

Hi,
Here is a related blog for your reference.
SCSM 2012 SP1 (Beta) – Monitoring Management Servers with SCOM 2012
http://marcelzehner.ch/2012/09/29/scsm-2012-sp1-beta-monitoring-management-servers-with-scom-2012/
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

2012 Health Service handle Count Threshold

I only have one server at present (a beefy one) for testing SCOM 2012 and with just 10 servers being monitored and only the AD, SQL, and Task Scheduler MP's installed, already the RMS is complaining that the Threshold for the
Health Service Handle Count is over the top.
Is this a case of simply adjusting the threshold from 6000 to a higher number?
If so, what is the magic number pls?
Thx very much,
John Bradshaw

Based on my knowledge the Healthservice handle count will go high when there is a huge alert flow mainly where there is lot of agents and when they throw lot of alerts.
In our Environment of SCOM 2007 R2 we monitor Exchange 2010 and that is a quiet noisy MP.
So there may be some agent which is throwing some collection / alerting data for which this count will go high.
Request you guys to run the below SQL Query on the Ops DB to check which are those noisy alerts
Most common events by event number and event publishername: (This
gives us the event publisher name to help see what is raising these events)
SELECT top 50 Number, Publishername, COUNT(*) AS TotalEvents
FROM EventAllView
GROUP BY Number, Publishername
ORDER BY TotalEvents DESC
and
Computers generating the most events: (This
shows us which computers create the most event traffic and use the most database space)
SELECT top 50 LoggingComputer, COUNT(*) AS TotalEvents
FROM EventallView
GROUP BY LoggingComputer
ORDER BY TotalEvents DESC
refer: https://social.technet.microsoft.com/Forums/systemcenter/en-US/908db57b-4ed4-4b8e-8513-fd62965332ba/health-service-handle-count-threshold
Gautam.75801

SCOM Health Service Watcher / Server Availability...

Good morning all,
I'm reasonably new to SCOM reporting and have only recently started to take a close look at how this could be performing for my company. I understand that SCOM reporting is a vast and complex beast and have also read quite a lot of questions posted in forums
that are not a million miles away from what I'm about to ask (although not quite the same).
I'm looking to produce a report that reports upon the reachability / actual uptime of each monitored server. I've selected my date range and added the health service watcher for each of my servers, indicated what I consider an outage to be (unplanned maintenance
and monitoring unavailable) and produced the report. The result is confusing me. For around 2/3's of our monitored infrastructure I'm viewing what I expected to see... around 99% uptime with the "health Service Heartbeat Failure" and "Computer
Not Reachable" monitors having detected some downtime (power cycles following application of Windows updates). However, around a 1/3 of our infrastructure isn't reporting any downtime what-so-ever, nothing detected by the "health Service Heartbeat
Failure" and "Computer Not Reachable" monitors which is inaccurate as these servers have been power cycled following Windows updates applications.
If anyone could shed any light on what is occurring here it would be greatly appreciated.
Thank you in advance for anyone taking the time to read this post.
Cheers.
M Tipler

Hi,
As far as I know, the heartbeat interval for agents is 60 secs by defalt, and the management server allow 3 times of missed heartbeat. So although some agents have been rebooted due to updates, the management server may not fire heatbeat alert for them.
It is suggested to run SQL query to get all heartbeat failure on all agents:
SELECT
TOP
[AlertName]
,[BaseManagedEntity].DisplayName
FROM [OperationsManager].[dbo].[Alert]
JOIN [OperationsManager].[dbo].[BaseManagedEntity]
ON [ALERT].BaseManagedEntityId=[BaseManagedEntity].BaseManagedEntityId
WHERE [ALERT].AlertName
= 'Microsoft.SystemCenter.HealthService.Heartbeat'
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

ConfigMgr 2012 Agent Installation permanently failed with Error 1603

We have some clients, where the agent must be reinstalled. But it fails permanently with Error 1603. I have tried the following steps allready:
Delete the CCMSETUP and CCM Folder and start from scratch
Repair WMI by deleting root\ccm
Recreated the WMI Repository
Register all *.dll and *.mof in WBEM
Cleaned up with the ccmclean Tool
We use SCCM 2012 SP1 CU3
The error happens on Vista and Windows 7
From the logs, it looks that something went wrong with the ccmexec service, but I'm not sure. In the Eventlogs are some entries from the Search Service that the Service unexpectly stopped. But not much more.
CCMSETUP.LOG
MSI: Action 11:25:16: CcmRegisterSystemTask. Registers a System Task with WMI.
MSI: Action 11:25:17: CcmRegisterHostingConfiguration. Register configuration for Configuration Manager Client service.
MSI: Action 11:25:17: CcmSetObjectSecurity. Applying security permissions
MSI: Action 11:25:18: CcmSetupLogging. Sets component logging information in WMI.
MSI: Action 11:25:19: SmsSwDistSetCacheConfig. This custom action gets the cache configuration, disables the cache options in control panel if required by the site settings and updates the registry keys accordingly. It also configures the security for the cache
directory.
MSI: Action 11:25:19: CcmRegisterPerfCountersRollback. Rolls back any changes made by CcmRegisterPerfCounters if install fails.
MSI: Action 11:25:19: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action
MSI: Action 11:25:20: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
MSI: Action 11:25:20: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit
MSI: Action 11:25:20: CcmInstallUtil. Calling InstallUtil.exe to register .net WMI provider
MSI: Action 11:25:20: SmsSetLUAAccessPermissions. >Gets permission for evelation on Vista and grants each COM object permission.
MSI: Action 11:25:20: Ngen. Calling NGEN.exe
MSI: Action 11:25:22: InstallServices. Installing new services
MSI: Action 11:25:22: WriteEnvironmentStrings. Updating environment strings
MSI: Action 11:25:22: CcmSetServiceConfig. Sets WMI ServiceRootDir and configures CCMEXEC service.
MSI: Action 11:25:22: CcmRegisterWinTaskRollback. Rolls back the changes made by CcmRegisterWinTask.
MSI: Action 11:25:22: CcmRegisterWinTask. Registers tasks with Windows Task Scheduler.
MSI: Action 11:25:22: Rollback. Rolling back action:
File C:\Windows\ccmsetup\{1AF71F68-6089-4211-ADDC-06DF40606141}\client.msi installation failed. Error text: ExitCode: 1603 Action: ErrorMessages:
Next retry in 120 minute(s)...
CLIENT.MSI.LOG
MSI (s) (CC:B4) [11:26:01:135]: Executing op: ComponentUnregister(ComponentId={F7DB5D80-2A09-4F1B-BB55-8D69AA9A94A6},ProductKey={FD794BF1-657D-43B6-B183-603277B8D6C8},BinaryType=0,)MSI
(s) (CC:B4) [11:26:01:137]: Executing op: ComponentUnregister(ComponentId={4942E0A1-7621-4D9A-93B5-AFA1A0B7FCC6},ProductKey={FD794BF1-657D-43B6-B183-603277B8D6C8},BinaryType=0,)MSI
(s) (CC:B4) [11:26:01:137]: Executing op: ActionStart(Name=CcmStopServiceRollback,Description=Calls CcmStartService. Starts the ccmexec service.,)MSI
(s) (CC:B4) [11:26:01:139]: Executing op: CustomActionRollback(Action=CcmStopServiceRollback,ActionType=3329,Source=BinaryData,Target=CcmStartService,)MSI
(s) (CC:B4) [11:26:01:159]: Creating MSIHANDLE (12483) of type 790536 for thread 6068MSI
(s) (CC:64) [11:26:01:159]: Invoking remote custom action. DLL: C:\Windows\Installer\MSICFD.tmp, Entrypoint: CcmStartServiceMSI
(s) (CC!50) [11:26:01:221]: Creating MSIHANDLE (12484) of type 790531 for thread 5712MSI
(s) (CC!50) [11:26:01:222]: Closing MSIHANDLE (12484) of type 790531 for thread 5712MSI
(s) (CC!50) [11:26:01:222]: Creating MSIHANDLE (12485) of type 790531 for thread 5712[11:26:01]
WARNING: Failed to delete setup in progress time-stamp with error 0x80070002MSI (s) (CC!50)
[11:26:01:222]: Closing MSIHANDLE (12485) of type 790531 for thread 5712MSI (s) (CC:64)
[11:26:01:223]: Closing MSIHANDLE (12483) of type 790536 for thread 6068MSI (s) (CC:B4)
[11:26:01:223]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)MSI
(s) (CC:B4) [11:26:01:223]: Error in rollback skipped. Return: 5MSI
(s) (CC:B4) [11:26:01:223]: Entering MsiProvideAssembly. AssemblyName: Microsoft.ConfigurationManager.AssetProvider.dll,Version="5.0.0.0",Culture="neutral",PublicKeyToken="31bf3856ad364e35", AppContext: , InstallMode: -4MSI
(s) (CC:B4) [11:26:01:223]: Pathbuf: 0, pcchPathBuf: 0MSI (s) (CC:B4) [11:26:01:244]:
MsiProvideAssembly is returning: 1607[11:26:01] The service 'ccmexec' is not installedMSI
(s) (CC:B4) [11:26:01:255]: No System Restore sequence number for this installation.MSI
(s) (CC:B4) [11:26:01:255]: Unlocking ServerMSI (s) (CC:B4) [11:26:01:307]: PROPERTY CHANGE:
Deleting UpdateStarted property. Its current value is '1'.Action ended 11:26:01: INSTALL.
Return value 3.Property(S): UpgradeCode = {252DA259-82CA-4177-B8D0-49C78937BA3E}Property(S):
SourceDir = C:\Windows\ccmsetup\{1AF71F68-6089-4211-ADDC-06DF40606141}\
Has anybody came around this behavior?
Kind regards Stefan Somogyi

CCMClean.exe is not supported for ConfigMgr 2012, but I guess that you know that :)
Have you tried 'ccmsetup.exe /uninstall', wait for it to complete and then install again?
Perhaps the steps taken in the last comment from this thread can help you:
http://social.technet.microsoft.com/Forums/en-US/98fadc7b-2bdd-4b46-a0cb-ba43ebd10aaf/client-reinstall-failing-on-upgraded-clients?forum=configmanagerdeployment
Regards,
Nickolaj Andersen - MCTS - www.scconfigmgr.com - @Nickolaja

SCOM not generating alerts & The request to synchronize state for OpsMgr Health Service identified by "bdb1712b-0a9a-bbe3-9630-41f2da9f64a1" failed due to the following exception "System.Data.SqlClient.SqlException: Cannot open database "OperationsManager

Hi Anyone can assisting on this. The SCOM 2007r2 i managed suddenly do not pump out alerts.
I have perform full scom service restart(data access, agent, config). it no load up related datawarehouse like(stored, write)
I also restarted my sql db services. It show me the error like this. Anyhow i can fix it
The request to synchronize state for OpsMgr Health Service identified by "bdb1712b-0a9a-bbe3-9630-41f2da9f64a1" failed due to the following exception "System.Data.SqlClient.SqlException: Cannot open database "OperationsManager" requested
by the login. The login failed.
Login failed for user 'HK\svc-scomsdk'.
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.DatabaseConnection.Open()
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)
   at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)
   at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".

Hi,
I would like to suggest you reset the SDK account password (in this case, it seems like that the account is 'scomsdk'). And change the password for the account in service configuration.
Please go through the below article for details:
How to change the credentials for the SDK Service and for the Config Service in Microsoft System Center Operations Manager
http://support.microsoft.com/kb/936220/en-us
Regards,
Yan Li
Regards, Yan Li

ConfigMgr 2012 MP – suspending SCOM agent/health service

Similar Messages

Maybe you are looking for