Collect Timeout
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
HKLM\SYSTEM\CurrentControlSet\Services\service-name\Performance
| Data type | Range | Default value |
|---|---|---|
REG_DWORD |
0x0–0xEE6B2800 milliseconds |
(The value of OpenProcedureWaitTime.) |
Description
Defines a slow Collect procedure call for these counters.
This entry tells the Performance Library (Perflib) how long the Collect procedure call for these counters is expected to run. If the time specified in the value of this entry expires before the call completes, then Perfib considers the call to be abnormally slow, and it records an error in the Application Log in Event Viewer. Also, if the value of the Configuration Flags entry requires it, then Perflib disables the counters and does not display them again until you manually re-enable them.
Perflib times the procedure calls of non-trusted counters to identify counters that can delay or lock performance tools during initialization. While the Collect procedure call proceeds, you cannot use the performance tools, and remote users cannot log on to the local computer.
Activation Method
To make changes to this entry effective, restart the Remote Registry Service or restart Windows.
Notes
Timing procedure calls is one of several tests Perflib performs to maintain the integrity of the counters. To configure the Perflib test feature, use the Configuration Flags entry.
Perflib does not time the procedure calls of trusted performance counter dynamic-link libraries (DLLs). This entry applies only to non-trusted DLLs.
Perflib disables counters because of slow procedure calls only when the 0x8 (1000) bit is set and the 0x2 (10) bit is not set in the Configuration Flags entry.
Perflib does not time procedure calls when the 0x4 (100) bit is set in the Configuration Flags entry.
Perflib disables counters by setting the value of the Disable Performance Counters entry for that service to 1. After you have repaired or replaced the counter DLLs, you must re-enable them manually by changing the value of Disable Performance Counters to 0.
Some performance counters DLLs add this entry to the registry. If this entry does not appear, you can add it to the registry to override the default value.
Tip
- If you suspect problems with procedure calls, check the Application Log in Event Viewer. Perflib records an error in the log whenever a procedure call exceeds its limit.