SMS_EXECUTIVE ERROR 578

Question

_{Monday, December 1, 2014 9:56 PM}

Hey guys,

I keep on getting this error 

"Could not read registry key "HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_EXECUTIVE\Yield Configuration" on computer xxxxxx. The operating system reported error 2: The system cannot find the file specified. " Message ID 578.

Not sure where to start or what log could help me identify the issue.

Thanks

All replies (9)

_{Wednesday, December 3, 2014 3:13 PM ✅Answered}

Right click them and select "show messages" ...

Torsten Meringer | http://www.mssccmfaq.de

_{Wednesday, December 3, 2014 5:14 PM ✅Answered}

Each and every component has its own log file: http://technet.microsoft.com/en-us/library/hh427342.aspx

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Tuesday, December 2, 2014 1:51 AM}

Where are you seeing this are why are you are you troubleshooting it?

Just because there's a random message in a log doesn't mean that there's anything wrong. Some errors are expected and thus nothing to pursue.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Tuesday, December 2, 2014 1:20 PM}

Here are 2 threads on your exact question.  (It sounds like a component restart should fix it):

https://social.technet.microsoft.com/Forums/en-US/73d9fb90-e90a-4ec3-991f-dee18baf82c1/sccm-2012-warning-in-sms-executive-component-after-recovery?forum=configmanagergeneral

https://social.technet.microsoft.com/Forums/systemcenter/en-US/0fba78bd-02a5-43b6-abf2-6cacf9e101fc/srange-registry-key-error-with-smsofferstatussummarizer-component?forum=configmgrsetup

Best, Jacob I'm a PC.

_{Tuesday, December 2, 2014 4:50 PM}

Its showing in Site Status as critical!! I agree I didn't notice any disrupted functions but it is still annoying to have critical status and an X sign instead of green. Its pointing to the sql server box and the 2 site system role showing this message are: Reporting Services point and component server.

_{Tuesday, December 2, 2014 7:27 PM}

I doubt that message is causing your site status to be critical. Have you reviewed *all* status messages for the site?

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Tuesday, December 2, 2014 10:10 PM}



_{Wednesday, December 3, 2014 1:42 AM}

But the message you posted above is not causing these components to go critical. You need to review *all* of the status messages associated with each component. You should also review the log files associated with each component to troubleshoot why they are showing as critical.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, December 3, 2014 3:09 PM}

This the only 2 errors that I see when I review all for those 2 components. What logs are you referencing ?