imageHi everyone, Tyler Franke here once again with another troubleshooting tip for you.  Consider the following scenario:

In an otherwise healthy and functional site you find one or more of the following.

1) SMS Site Control Manager Site status message:

SMS Site Control Manager
Message ID: 2816
Message: The actual site control file %1 does not exist.
Solution: The SMS server components cannot function without this file. SMS Site Control Manager will shut down SMS Executive immediately. Contact Microsoft for help in restoring the actual site control file.

2) The following error in the sitectrl.log:

The delta site control file "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\incoming\.<site> via the SMS SDK on Mon Feb 27 17:32:41 GMT. The record was assigned the serial number 788 at site <site>. SMS_SITE_CONTROL_MANAGER 2/27/2012 11:33:06 AM 16676 (0x4124)
STATMSG: ID=2807 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_CONTROL_MANAGER" SYS= SITE= PID=34520 TID=16676 GMTDATE=Mon Feb 27 17:33:06.925 2012 ISTR0="D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\incoming\" ISTR1="Microsoft.ConfigurationManagement.dll" ISTR2="AD\E143665" ISTR3="%computername%" ISTR4="" ISTR5="2012 02 1 27 17 32 41 000" ISTR6="788" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_CONTROL_MANAGER 2/27/2012 11:33:06 AM 16676 (0x4124)
Wrote temporary file "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\temp\000003D2.ct0". SMS_SITE_CONTROL_MANAGER 2/27/2012 11:33:06 AM 16676 (0x4124)
Copied file "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\sitectrl.ct0" to "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\history\000003D1.ct0". SMS_SITE_CONTROL_MANAGER 2/27/2012 11:33:06 AM 16676 (0x4124)
WARNING: Could not move file "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\temp\000003D2.ct0" to "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\sitectrl.ct0". The operating system reported error 32: The process cannot access the file because it is being used by another process. SMS_SITE_CONTROL_MANAGER 2/27/2012 11:33:06 AM 16676 (0x4124)
Sleeping for five seconds... SMS_SITE_CONTROL_MANAGER 2/27/2012 11:33:06 AM 16676 (0x4124)

WARNING: Failed to complete processing of delta site control file "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\incoming\g0hrz08y.CT1". SMS_SITE_CONTROL_MANAGER will try to process the file again later. SMS_SITE_CONTROL_MANAGER 2/27/2012 11:34:07 AM 16676 (0x4124)
ERROR: The master site control file "D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\sitectrl.ct0" does not exist. SMS_SITE_CONTROL_MANAGER will shut down SMS_EXECUTIVE immediately. SMS_SITE_CONTROL_MANAGER 2/27/2012 11:34:07 AM 16676 (0x4124)
STATMSG: ID=2816 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_CONTROL_MANAGER" SYS= SITE= PID=34520 TID=16676 GMTDATE=Mon Feb 27 17:34:07.132 2012 ISTR0="D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box\sitectrl.ct0" ISTR1="D:\Program Files\Microsoft Configuration Manager\inboxes\sitectrl.box" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_CONTROL_MANAGER 2/27/2012 11:34:07 AM 16676 (0x4124)
SMS_EXECUTIVE is stopping... SMS_SITE_CONTROL_MANAGER 2/27/2012 11:34:07 AM 16676 (0x4124)

3) The following error in the MPControl.log:

SMS_MP_CONTROL_MANAGER 2/27/2012 12:05:33 PM 36352 (0x8E00)
SMS_MP_CONTROL_MANAGER received START notification. SMS_MP_CONTROL_MANAGER 2/27/2012 12:05:33 PM 36352 (0x8E00)
MPStart(): RegOpenKeyEx(MPNotify) returned 2. SMS_MP_CONTROL_MANAGER 2/27/2012 12:05:33 PM 36352 (0x8E00)
SMS_MP_CONTROL_MANAGER failed to start with 0x80070002 SMS_MP_CONTROL_MANAGER 2/27/2012 12:05:33 PM 36352 (0x8E00)
SMS_EXECUTIVE started SMS_MP_CONTROL_MANAGER as thread ID 37408 (0x9220). SMS_MP_CONTROL_MANAGER 2/27/2012 1:05:52 PM 39744 (0x9B40)

4) Service control manager events reporting that SMS_EXECUTIVE is terminating unexpectedly:

Log Name: System
Source: Service Control Manager
Date: 2/27/2012 10:12:55 PM
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: %computername%
Description: The SMS_EXECUTIVE service terminated unexpectedly. It has done this 3 time(s).

Cause

This can potentially be caused by one of more of the following:

1) File system corruption.
2) No Anti-virus scanning exclusion for %programfiles%\Microsoft Configuration Manager\Inboxes.
3) Someone manually or improperly editing the sitectrl.ct0 file on the site.

Resolution

To resolve this issue, execute and complete a site reset on the affected site server to create a new sitectrl.ct0 file.

More Information

About Performing a Site Reset: http://technet.microsoft.com/en-us/library/bb633159.aspx

How to Perform a Site Reset: http://technet.microsoft.com/en-us/library/bb694286.aspx

Tyler Franke | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/