XADM: The Print Spooler Service Stops Unexpectedly on an Exchange 2000 Server

This article was previously published under Q321314
This article has been archived. It is offered "as is" and will no longer be updated.
The Print Spooler service (Spoolsv.exe) may stop unexpectedly on a computer that is running Exchange 2000 Server. There may also be a larger number of threads in the Spoolsv.exe process than usual.
To allow communication with Active Directory, the Print Spooler service loads many dynamic-link library files (DLLs) when the Print Spooler service starts. When one of these DLL files, Cdoexm.dll, is loaded, that DLL file also loads an Exchange-specific module that monitors the registry for changes (Pttrace.dll). Because of a logic issue in the code, the Print Spooler service incorrectly tries to gain access to memory in an address space that is no longer resident. As a result, the process stops with an access violation.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix has the following file attributes or later:

Component: Collaboration Data Objects (CDO)

File nameVersion

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

Article ID: 321314 - Last Review: 10/24/2013 11:28:49 - Revision: 1.4

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB321314