We're having a weird issue in our SCCM environment. Our secondary site that houses 85 - 90 % of our clients is a BDP. In the component status window, I'm seeing that the SMS_STATE_SYSTEM keeps stopping every two hours. The component message states:
MS Executive detected that this component stopped unexpectedly.
Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly.
Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
I logged onto the site serer in question, and looked into the statesys.log and noticed the following messages. line that states "Could Not Connect to registry" repeats every minute for the next two hours, and then the whole thing repeats itself every two hours.
ThreadMain (SMS_STATE_SYSTEM) ...SMS_STATE_SYSTEM3/6/2012 11:44:30 AM5288 (0x14A8)
=== SMS_SVC_STATE_SYSTEM has Started ===SMS_STATE_SYSTEM3/6/2012 11:44:30 AM5288 (0x14A8)SMS_SVC_STATE_SYSTEM - Could not get copy of registry config.SMS_STATE_SYSTEM3/6/2012 11:44:30 AM5288 (0x14A8)
SMS_SVC_STATE_SYSTEM - Could not connect to registry.SMS_STATE_SYSTEM3/6/2012 11:45:30 AM5288 (0x14A8)
SMS_SVC_STATE_SYSTEM - Could not connect to registry.SMS_STATE_SYSTEM3/6/2012 11:46:30 AM5288 (0x14A8)
SMS_SVC_STATE_SYSTEM - Could not connect to registry.SMS_STATE_SYSTEM3/6/2012 11:47:30 AM5288 (0x14A8)
SMS_SVC_STATE_SYSTEM - Could not connect to registry.SMS_STATE_SYSTEM3/6/2012 11:48:30 AM5288 (0x14A8)
I'd appreciate any feedback regarding this. Right now we are able to push updates to machines, but the compliance reports are useless as the machines state message isn't getting processed. In the compliance report we have over 80% of our clients send back"state unknown" message.