SMS: Despooler Service Processes SNI Files Slowly

Last reviewed: December 1, 1997
Article ID: Q168130
The information in this article applies to:
  • Microsoft Systems Management Server version 1.2

SYMPTOMS

After Systems Management Server jobs are canceled, it may appear that subsequent jobs remain in a pending state. The Systems Management Server Despoolr.log file may display the following:

   Despooler failed to execute the instruction, error code = 38a

CAUSE

Canceling a Systems Management Server job may corrupt the *.sni file. This causes the Despooler Service to process very slowly through each corrupt file, and display the message listed in the Symptoms section. SNI files are job status MIFS returning from the client, and are processed before INS files. It appears that Despooler is not getting to the Pending jobs.

Also, deleting an active job, or deleting a job before it is completely canceled can also cause the error to occur.

WORKAROUND

Examine the SMS\Site.srv\Despoolr.box\Receive directory and move all *.sni files that are unrelated to current active jobs to a temporary subdirectory.

Some good practices to implement include the following:

  • If you cancel your jobs, do not delete them until they have been canceled for 48 hours.
  • If you are canceling jobs, do not cancel more than one at a time.
  • Do not delete Active jobs.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 1.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodsms slow hang delete
Keywords : kbbug1.20 smsdespooler
Version : winnt:1.2
Platform : winnt
Issue type : kbbug
Solution Type : kbpending


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.