SMS: DBG Entries in Sched.log File Recorded by Scheduler

 Last reviewed: February 16, 1998
Article ID: Q181042
The information in this article applies to:
  • Microsoft Systems Management Server, versions 1.0, 1.1, and 1.2

SYMPTOMS

The Scheduler records some "DBG" entries, as in the following example: 

   DBG>> Send request about to write bad data. Component SMS_SCHEDULER
If you use Dumpsend.exe to check the involved send request, you can see that the send request has been corrupted. The destination site ID and the job ID are blank.

CAUSE

A desynchronization between the SENDER and the SCHEDULER causes the SENDER to update a deleted instruction file. An incomplete (corrupted) instruction file is created.

WORKAROUND

To resolve this problem, obtain the hotfix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1 and 1.2. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Additional query words: prodsms
Keywords : kbbug1.00 kbbug1.10 kbbug1.20 smsscheduler
Version : winnt: 1.0, 1.1, 1.2
Platform : winnt
Issue type : kbbug
Solution Type : kbpatch

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: February 16, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.