Current History Registry Key Is Not Updated Properly

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

SYMPTOMS

Although jobs in Systems Management Server have been successfully canceled and removed, the following registry key continues to grow with package ID information:

   HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\SMS\COMPONENTS
      \SMS_Despooler\Current History

CAUSE

Systems Management Server does not purge the registry information.

RESOLUTION

If you cancel or remove a job, do the following:

WARNING: Using the Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Start Registry Editor (REGEDT32.EXE) and locate the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:

    \SOFTWARE\MICROSOFT\SMS\COMPONENTS\SMS_Despooler\Current History

  2. Manually remove canceled or non-existing package ID entries.

  3. Quit Registry Editor.

  4. Shut down and restart Windows NT.

STATUS

Microsoft has confirmed this to be a problem in System 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
Keywords : kbnetwork smsdespooler
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.