Packages that are sent from a parent site are not received on child sites and the SMS_EXECUTIVE service stops repeatedly in Systems Management Server 2.0 (883987)



The information in this article applies to:

  • Microsoft Systems Management Server 2.0

SYMPTOMS

Microsoft Systems Management Server (SMS) 2.0 software distribution packages that are sent from a parent site do not appear on child sites. Although you can restart the SMS_EXECUTIVE service, the service stops unexpectedly after you restart it. The contents of the Crash.log file in the drive letter:\Sms\Logs folder contains information that is similar to the following:
Time = Date and time
Service name = SMS_EXECUTIVE
Thread name = SMS_SCHEDULER
Executable = drive letter:\SMS\bin\i386\smsexec.exe
Process ID = 1660 (0x67c)
Thread ID = 1224 (0x4c8)
Instruction address = 6c374060
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 00000013 for which it does not have the appropriate access."

CAUSE

This issue occurs because of a damaged send request file (.srq). When the SMS_SCHEDULER thread processes a damaged .srq file, the SMS_EXECUTIVE service creates a Crash.log file, and then the SMS_EXECUTIVE service stops.

RESOLUTION

To resolve this issue, identify the damaged .srq file, and then delete the damaged .srq file from the parent site server.

Identify the damaged .srq file that is causing this issue

  1. Start Notepad, and then open the drive letter:\Sms\Logs\Crash.log file.
  2. Make a note of the thread ID that is assigned to the SMS_SCHEDULER thread. In the example earlier in this article, the SMS_SCHEDULER thread ID value is 1224 (0x4c8).
  3. In Notepad, open the drive letter:\Sms\Logs\Sched.log file.
  4. Search the Sched.log file for the thread ID to identify the damaged .srq file that is causing this issue. The entry in the Sched.log file may appear similar to the following:

    <JOB 0004F88C> $$<SMS_SCHEDULER><datetimetime zone><thread=1224 (0x4C8)>

    Updating status of minijob "Software Distribution for MQSeries Workflow Client, Package ID = C01002E9". $$<SMS_SCHEDULER><datetimetime zone><thread=1224 (0x4C8)>

    Checking status of send request 3_VCEC01. $$<SMS_SCHEDULER><datetimetime zone><thread=1224 (0x4C8)>

    Important In this example, you must delete the 3_vcec01.srq send request file.

Delete the damaged .srq file

  1. Stop the SMS Executive service and Site Component Manager service on the site server. To do this, follow these steps:
    1. Click Start, point to Settings, and then click Control Panel.
    2. Double-click Administrative Tools, and then double-click Services.
    3. Right-click SMS_SITE_COMPONENT_MANAGER, and then click Stop.
    4. Right-click SMS_EXECUTIVE, and then click Stop.
  2. Delete the damaged .srq file from one of the following folders:
    • Sms_root_folder\Inboxes\Schedule.box\Requests
    • Sms_root_folder\Inboxes\Schedule.box\Outboxes\Lan
  3. Start the SMS_EXECUTIVE service, and then start the SMS_SITE_COMPONENT_MANAGER service on the site server.

Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbwinservperf kbMgmtServices kbtshoot kbprb KB883987 kbAudITPRO