SMS: Access Violation Occurs with Pollinv.exe

Last reviewed: March 3, 1997
Article ID: Q159610
1.00 1.20 WINDOWS kbenv kbbug1.20

The information in this article applies to:

  • Microsoft Systems Management Server version 1.2
  • Microsoft Systems Management Server 1.2 Resource Kit
  • Microsoft Backoffice Resource Kit version 1.0

SYMPTOMS

If a computer listed in the Invcolcl.txt file cannot be located on the network by the Systems Management Server Windows NT Inventory File Collector Service, Pollinv.exe, the following will occur:

  • The service will appear to stop responding when trying to locate that computer. It will not log anything further in the Invcolcl.log log file.
  • If the service is then restarted manually, or comes to the beginning of its next watchdog cycle (the default is 24 hours), then an access violation (AV) error will occur.

WORKAROUND

To work around this problem, remove the nonexistent computer from the list of computers to poll in the Invcolcl.txt file.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 1.2, the Systems Management Server Resource Kit 1.2, and the Backoffice Resource Kit version 1.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


KBCategory: kbenv kbbug1.20
KBSubcategory: smsutil
Additional reference words: prodsms reskit 1.20 1.00 bork
SMS_NT_INVENTORY_FILE_COLLECTOR inv32cli invwin32 climonnt
Keywords : smsutil kbbug1.20 kbenv
Version : 1.00 1.20
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 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.