Help and Support
 

powered byLive Search

The Systems Management Server 2003 SMS_Executive service continuously stops and restarts

View products that this article applies to.
Article ID:889432
Last Review:October 27, 2006
Revision:1.3

SYMPTOMS

The Microsoft Systems Management Server (SMS) 2003 SMS_Executive service (Smsexec.exe) stops continuously, and a Crash.log file is created in the SMS\Logs folder. The Crash.log file contains an error message that is similar to the following:
EXCEPTION INFORMATION
Time = 02/22/2003 11:52:26.992
Service name = SMS_EXECUTIVE
Thread name = SMS_SCHEDULER
Executable = E:\SMS\bin\i386\smsexec.exe
Process ID = 2108 (0x83c)
Thread ID = 780 (0x30c)
Instruction address = 6c374060
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 00000016 for which it does not have the appropriate access." Raised inside CService mutex = No CService mutex description = ""


Additionally, the Sched.log file may contain the following message:
<JOB 000D6F08> $$<SMS_SCHEDULER><Sat Feb 22 11:52:26.976 2003 Central Standard Time><thread=780 (0x30C)> Updating status of minijob "PackageName, Package ID = PackageID". $$<SMS_SCHEDULER><Sat Feb 22 11:52:26.976 2003 Central Standard Time><thread=780 (0x30C)> Checking status of send request SendRequestFile. $$<SMS_SCHEDULER><Sat Feb 22 11:52:26.976 2003 Central Standard Time><thread=780 (0x30C)>
SendRequestFile is the name of the send request file, and PackageID is the ID of the advertised package. The Sched.log file is located in the SMS\Logs folder.

Note This message may appear in the Sched.log file every time the SMS_Executive service restarts.

Back to the top

CAUSE

This problem typically occurs when the send request file is corrupted. When this problem occurs, the SMS_Executive service cannot read the send request file. The SMS_Executive service may cause an access violation. When the SMS_Executive service restarts, it tries to re-read the send request file, and the access violation occurs again.

Back to the top

RESOLUTION

To resolve this problem, stop the SMS_Executive service, and then delete the corrupted send request file. To do this, follow these steps.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
1.Use an account that has administrative permissions to log on to the SMS site server computer that is experiencing the problem.
2.Click Start, point to Programs, point to Administrative Tools, and then click Services.
3.In the Services snap-in, right-click SMS_EXECUTIVE, and then click Stop.
4.Use Windows Explorer to locate the SMS\inboxes\schedule.box\requests folder.
5.Right-click the send request file that cannot be read by the SMS_Executive service, and then click Delete. The send request file is referenced in the Sched.log file every time the SMS_Executive service restarts.
6.In Windows Explorer, right-click the SMS\inboxes\schedule.box folder, and then click Search.
7.In Search Results, type *.* in the Search for files and folders named box, type the name of the send request file in the Containing text box, and then click Search Now.
8.Right-click any files that contain a reference to the corrupted send request file, and then click Delete.
9.Click Start, point to Programs, point to Administrative Tools, and then click Services.
10.In the Services snap-in, right-click SMS_EXECUTIVE, and then click Start.

Back to the top

APPLIES TO
•Microsoft Systems Management Server 2003

Back to the top

Keywords: 
kbtshoot kbprb KB889432

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.