Invalid Audit and History Records

 Last reviewed: April 24, 1997
Article ID: Q148263
The information in this article applies to:
  • Microsoft Systems Management Server version 1.0, 1.1 and 1.2

SYMPTOMS

History records maintained by Systems Management Server (SMS) begin to get cluttered and often contradictory as successive audits are run on files which may have been moved, or even deleted. At this time, the only way to be sure you have accurate records is to run DBCLEAN, and delete all audit files, then re-run the audit jobs.

CAUSE

The problem is that every part of an Audited Software row is a key field. Even though the package number and file names may always be the same, the "Time Collected" is always different. Thus, the Data Loader does not correctly identify and map the previous instances to the new ones, and assumes all the data is new.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1 and 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
Keywords : kbbug1.10 kbnetwork smsaudit
Version : 1.0 1.1 1.2
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: April 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.