Site components with Critical status and other compmon.log errors

I have a couple of problems but I don't know if they are related or not.

#1

In my Site Status the Application Catalog website point, Application Catalog web service point and Reporting services point are all reading critical.  If I look at the events for all three there is nothing indicating any kind of problem. All three components appear to be functioning correctly as well.  If I use a DB query to reset the statuses to 0 they all go green for a period of time but then return to critical.  This has been like this for a while and there hasn't been any changes to SCCM.

#2 and possibly related

In the compmon.log I get the following errors:

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

I have performed a site reset but that hasn't helped.  I have also compared the Operations Management registry key permissions against my test environment which is nearly identical and doesn't have this problem and they keys and permissions are identical.  I have also tried removing and reinstalling the App Catalog Website point as well just to try that angle but it didn't help.

I supposed that if the site server cannot read the status registry keys that could result in the components being marked as critical.

Anyone have any other suggestions about where I can look to resolve this?

Thanks

May 26th, 2015 9:36am

What version (and CU) of ConfigMgr are you running?

Jeff

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 10:46am

2012 R2 CU4.

Thanks.

May 26th, 2015 10:48am

I've seen something similar in environments that have ConfigMgr 2012 SP1 with no CUs.  Sounds like your environment is more up to date, which is a good thing.  You can check out this thread - https://social.technet.microsoft.com/Forums/en-US/5e0b7af6-f00c-4610-a709-f3e0e26505be/sccm-2012-monitoring-site-status-reporting-services-point-status-critical?forum=configmanagergeneral

I have not attempted the database and WMI changes yet in an environment.  Standard cautions apply - test it in a non-production environment, call Microsoft, etc.

Jeff

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 11:30am

I've tried the database query to reset the status outlined in that post.  It works temporarily but after a short time the status goes back to critical.

I have also checked through WMI and the state for the critical components is set to '2'.  I have tried removing and reinstalling the App Catalog web service and website points but that didn't resolve it.  They just came back as critical after reinstallation.

Looks like I might need to burn an incident if I get tired of looking at the red dots :)

May 26th, 2015 11:54am

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

Other recent topics Other recent topics