Problem with SCCM components

Hi all,

I have strange problem with few of SCCM components. We have configured SCOM alerts for SCCM. From two months, I'm getting thousands alerts from SCOM which report about problem (CRITICAL) with SMS_INBOX_MONITOR, SMS_OUTBOX_MONITOR, SMS_OFFER_STATUS_SUMMARIZER and others. After few minutes I'm getting another SCOM mail with info about closed alerts. And again and again.

On Monitoring->Component status all components looks fine and has "OK" status. But when I check details there is something like this:

"Message ID 4630: Component status summarizer detected that avability of component SMS_INBOX_MONITOR has changed to failed. 

Possible cause: This component has failed to generate a heartbeat within its heartbeat interval or has reported with its heartbeat that it is in a failure state.  Solution: Verify that the condition persists by examining compmon.log and then check the component's log file."

SCCM enviroment looks fine and stable. I'm loosing mind to checking what can be wrong. I will be glad and happy for any advices and suggestions. Thank you.

February 9th, 2014 12:41pm

Solution: Verify that the condition persists by examining compmon.log and then check the component's log file.

Hi,

Any useful information in the logs?

Best Regards,

Joyce Li

Free Windows Admin Tool Kit Click here and download it now
February 10th, 2014 8:57am

Hi

Thank you for answer.

In Compmon.log there is:

Checking components ...
Failed to read the required Operations Management component registry key values on local computer; error = 6 (0x6).
Failed to read in current property values and initialize COpsMgmtComponent object; error = 6 (0x6).
Can not get the current execution state for component Windows_Intune_Service since it is not installed or completed installing.
Waiting until the next polling cycle in 300 seconds from now.

In mpcontrol.log, inboxmon.log is clear. No errors or warrnings.

In inboxmgr.log there is (I don't know it is normal:

Waiting for changes in inbox definition and inbox rules, max wait = 3600 seconds
Waiting for changes in inbox definition and inbox rules, max wait = 3600 seconds
Waiting for changes in inbox definition and inbox rules, max wait = 3600 seconds
************ SERVICE THREAD IS STOPPING ************
SMS_EXECUTIVE started SMS_INBOX_MANAGER as thread ID 4828 (0x12DC).
************ SERVICE THREAD IS STARTING ************
Waiting for changes in inbox definition and inbox rules, max wait = 60 seconds
Waiting for changes in inbox definition and inbox rules, max wait = 3600 seconds
February 10th, 2014 12:58pm

Hi,

From the logs you provided, the error(Failed to read the required Operations Management component registry key values on local computer; error = 6 (0x6).) might be caused by missing files or missing registry settings, and/or permissions to those file and registry settings, which is causing the services to not be able to start or function as expected.

Could you please check the component status messages to see whether there are any other errors before Message ID 4630?

Best Regards,

Joyce Li

Free Windows Admin Tool Kit Click here and download it now
February 11th, 2014 10:47am

Hi,

Joyce--> Thank you for answer. Befroe 4630 is this:

SMS_INBOX_MONITOR 500 This component started.
SMS_INBOX_MONITOR 502 This component stopped.
SMS_INBOX_MONITOR 501 This component was signalled to stop by an administrator or the operating system. The component will complete any processing it is doing and stop at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to stop.

February 19th, 2014 7:24am

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Free Windows Admin Tool Kit Click here and download it now
March 7th, 2015 12:18pm

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

August 23rd, 2015 5:11pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics