This article has been archived. It is offered "as is" and will no longer be updated.
When you use System Monitor to monitor the Processor object on a multiprocessor computer that is running a 64-bit version of Microsoft Windows Server 2003, System Monitor shows only one active processor. The processor that appears to be active is processor 0.
This problem occurs because a program calls the timeSetEvent() function and sets the uResolution parameter to a value that is less than 10 milliseconds.
To resolve this problem, obtain the latest service pack for Microsoft Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
To work around this problem, set the uResolution parameter in the timeSetEvent() function to a value of 10 milliseconds or more.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 1.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates