DOCUMENT:Q325585 10-JUL-2002 [sms] TITLE :SMS: Software Inventory May Be Discarded from Offline Clients PRODUCT :Microsoft Systems Management Server PROD/VER::2.0,2.0 SP1,2.0 SP2,2.0 SP3,2.0 SP4 OPER/SYS: KEYWORDS:kbsms200 kbsms200bug kbInventory ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Systems Management Server versions 2.0, 2.0 SP1, 2.0 SP2, 2.0 SP3, 2.0 SP4 ------------------------------------------------------------------------------- SYMPTOMS ======== If a computer that is running the Systems Management Server (SMS) 2.0 client agent with software inventory turned on cannot connect to the network to forward collected software inventory, and if that inability to connect continues for more than a single software inventory cycle, the resulting software inventory that is reported when the computer finally can connect may be inaccurate. Computers may be legitimately off the network or be unable to connect for many reasons, including Client Access Points (CAPs) that are offline for maintenance, temporary network problems, or laptop computers that may be disconnected from the network for days at time. CAUSE ===== There is no ordering in the processing of software inventory files. If a computer has two inventory files queued up and both are forwarded at the same time, the most recent inventory file may be processed before the older file. If any inventory changes such as software addition or deletion are recorded in the older file, they are discarded and the software inventory processor records the following message in the Sinvproc.log file: WARNING - This file is out-of-date and will be skipped. Because the older inventory is not processed, changes to inventory that are recorded in the older inventory file are not recorded in the database. WORKAROUND ========== Delete the Sinv.his file from the client computer on which the inventory information is possibly inaccurate. Then, either wait for the next software inventory cycle or force a new cycle. This sends a complete inventory for the client that overrides any conflicting data in the database. STATUS ====== Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. Additional query words: prodsms ====================================================================== Keywords : kbsms200 kbsms200bug kbInventory Technology : kbSMSSearch kbSMS200 kbSMS200SP1 kbSMS200SP2 kbSMS200SP3 kbSMS200SP4 Version : :2.0,2.0 SP1,2.0 SP2,2.0 SP3,2.0 SP4 Issue type : kbprb ============================================================================= 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. Copyright Microsoft Corporation 2002.