SCCM Server SMS EXECUTIVE Service Stopped!!!

Question

SCCM Server SMS EXECUTIVE Service Stopped!!! The sitecomp.log file recorded below prior to the service stops,

Waiting for changes to the "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box" or "D:\Program Files\Microsoft Configuration Manager\inboxes\sitecomp.box" directories, servers will be polled in 59 minutes, 59 seconds...

Detected a change to the "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box" directory.

A new site control file was not available.

Waiting for changes to the "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box" or "D:\Program Files\Microsoft Configuration Manager\inboxes\sitecomp.box" directories, servers will be polled in 59 minutes, 59 seconds...

Detected a change to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing registry key.

Waiting for changes to the "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box" or "D:\Program Files\Microsoft Configuration Manager\inboxes\sitecomp.box" directories, servers will be polled in 59 minutes, 58 seconds...

SMS_SITE_COMPONENT_MANAGER service is stopping...

STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=XXXXXXXXXX PID=6772 TID=7468 GMTDATE=Sat Sep 23 22:53:09.435 2023 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0

Updating all Operations Management component registry key values.

Updating all Operations Management component registry key values.

STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=XXXXXXXXXX PID=6772 TID=5288 GMTDATE=Sat Sep 23 22:53:09.469 2023 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0

Awaiting your expert answers!!!

Answer 1

The issue has been resolved with the help of MS Engineers. Here are the steps we took to fix it:

• We reset the SMS Provider of the SCCM Server
• We applied the SCCM Server license

This is for everyone's information and reference. Thank you.

Answer 2

Hi,

The log snippet you've provided doesn't explicitly indicate the root cause of the service stopping, but it does show some activity related to the SCCM site component manager. To diagnose and resolve the issue, you can follow these steps:

1. First, check the status of your SCCM site components. Ensure that all site components are healthy and running. You can do this through the SCCM console by navigating to "Administration" > "Site Configuration" > "Servers and Site System Roles."
2. Look for any errors or warnings in the SCCM console under "Monitoring" > "System Status" > "Component Status." This will give you more information about any specific issues with site components.
3. Ensure that the SCCM database is healthy. Check the SQL Server logs for any database-related issues. Database problems can sometimes lead to service failures.
4. You can try restarting the SMS_EXECUTIVE service manually to see if it starts without errors. If it doesn't start, note any error messages that appear.