If Data Loader Loses Its Link to SQL, Good MIFs May Be Rejected

Last reviewed: March 11, 1997
Article ID: Q153573

The information in this article applies to:

  • Microsoft Systems Management Server versions 1.0 and 1.1

SYMPTOMS

If the Inventory Data Loader process loses its connection to SQL, it is possible that the MIF that the Inventory Data Loader was processing might be treated as a BADMIF and consequently not be processed; the MIF will instead be placed in the BADMIF subdirectory. Once the SQL connection is re- established, the affected MIF can be moved back to the Deltamif.col directory and subsequently be processed.

The following is a sample from the Inventory Data Loader log file:

   Waiting for a MIF...
   finished processing current machine.
   Cannot process MIF 00000000.MIF, moving it to BADMIFS
   finished processing current machine.
   SQL problem detected, terminating the thread.
   SQL problem detected, terminating UMF processing thread.
   Processing a machine...

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 1.1. It has been fixed in Systems Management Server version 1.2.


KBCategory: kbbug
KBSubcategory: smsgeneral
Additional reference words: prodsms 1.00 1.10 1.20 mif inventory data
loader
Keywords : smsgeneral kbbug
Platform : WINDOWS


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