A transfer is not resumed immediately after the SMS_EXECUTIVE service is restarted in Systems Management Server 2003 (906318)



The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

You stop and then restart the SMS_EXECUTIVE service when a large job is being transferred to a remote Microsoft Systems Management Server (SMS) 2003 site. The transfer is not resumed immediately after the SMS_EXECUTIVE service is restarted. However, you may see other transfers being serviced toward the same remote SMS 2003 site. The transfer of the large job is eventually resumed.

CAUSE

When no bandwidth restriction is being used, the sender thread does not take notice of a stop instruction. Instead, the thread continues to send data to the remote SMS 2003 site until the thread is stopped after 10 minutes. (The Service Control Manager stops the thread.) However, the send request file is not correctly updated. The file indicates that an active transfer is still occurring when the SMS_EXECUTIVE service has stopped. Therefore, the scheduler thread does not take notice of this send request until enough time has passed to consider the send request abandoned. Depending on the SMS 2003 site configuration, the time that is required for a send request to be considered abandoned may be significant.

WORKAROUND

To work around this issue, follow these steps:
  1. Open the SMS Administrator console.
  2. Expand Site Database (Site_code - Site_name), expand Site Hierarchy, expand Site_code - Site_name, and then expand Site Settings.
  3. Click Senders, right-click the sender that is being used, and then click Properties.
  4. On the Advanced tab, decrease the values for the Delay before retrying setting and the Number of retries setting.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Modification Type:MajorLast Reviewed:11/4/2005
Keywords:kbtshoot kbprb KB906318 kbAudITPRO