Article ID: 161043
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Systems Management Server 1.2 Standard Edition
This article was previously published under Q161043
SYMPTOMS
A single job may cause the distribution process to stop responding. The job in question will report the following error in the Despooler log file:
The status of all new jobs created after this process will remain Pending, and the original job will not complete until either Despooler or Smsexec are stopped and restarted.
CAUSE
Despooler attempts to read the INS file passed to it by Lansend before Lansend has released its file lock. Consequently, Despooler cannot access the INS file. Despooler should try to read the INS file again at the next polling cycle, but is not doing so.
WORKAROUND
To work around this problem, manually stop and restart the Sms_executive service. Use the following AT scheduling commands to stop and restart the service on a daily or weekly basis.
at \\anfield 21:00 /every:m,t,w,th,f,s,su "c:\winnt\stop.bat"
Stop.bat = net stop sms_executive
at \\anfield 21:20 /every:m,t,w,th,f,s,su "c:\winnt\start.bat"
Start.bat = net start sms_executive
NOTE: Start the scheduler service on the site server as an administrator user.
STATUS
Microsoft has confirmed this to be a problem in Systems Management Server version 1.2. This problem was corrected in the latest Microsoft Systems Management Server version 1.2 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Additional query words: Despool Error32 32 share
Keywords: kbbug kbdespooler kbusage KB161043
