Current History Registry Key Is Not Updated Properly
Article ID: 147616
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Systems Management Server 1.0 Standard Edition
- Microsoft Systems Management Server 1.1 Standard Edition
- Microsoft Systems Management Server 1.2 Standard Edition
This article was previously published under Q147616
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.
- 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
- Manually remove canceled or non-existing package ID entries.
- Quit Registry Editor.
- 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: kbdespooler kbnetwork KB147616