The information in this article applies to:
SYMPTOMSA 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. CAUSEDespooler 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. WORKAROUNDTo 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.
NOTE: Start the scheduler service on the site server as an administrator
user.
STATUSMicrosoft 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 : kbtool kbusage smsdespooler kbbug1.20 kbfix1.20.sp2 |
Last Reviewed: September 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |