SMS: .Tmp Files Not Converted to .Raw Files In Logon.srv

Last reviewed: July 7, 1997
Article ID: Q168340
The information in this article applies to:
  • Microsoft Systems Management Server, version 1.2

SYMPTOMS

After moving a Systems Management Server NetWare Logon Server from site A to site B, you may see some extraneous .tmp files in the Sms\Logon.srv directory of that logon server.

CAUSE

When clients log on to a NetWare server that has been moved from one site to another and run the Systems Management Server script, the inventory will not be taken for three times (or however many times InvAgtFalseLogonCount is set for). On the third logon, the clients write a .tmp file in the Sms\Logon.srv\Inventry.box directory on that NetWare logon server. The .tmp file is a small file, and does not contain all the inventory information. The .tmp file will not be converted to a .raw file, and therefore is not moved by Maintenance Manager to the site server.

WORKAROUND

To work around this problem, manually delete the .tmp files. Be sure to only delete those files that are affected by this problem, and do not delete any new .tmp files that are waiting to be converted to .raw files.

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 sms execute
Keywords : kbnetwork smsinv smsmaintman
Version : 1.2
Platform : Windows
Issue type : kbbug
Resolution Type : kbworkaround


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