OpenProcedureWaitTime

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

Data type Range Default value
REG_DWORD 0x0 - 0xEE6B2800 milliseconds 0x2710 (10 seconds)

Description

Defines a slow Open procedure call for the performance counters DLLs on this system.

When an Open procedure call takes longer to complete than the time specified in this entry then, by default, Perflib records an error in the Application Log. However, if the value of Configuration flags is0x0, Perflib disables the counter DLL and does not load the counters again until you have manually reenabled them.

Perflib times the procedure calls of non-trusted counters to identify counters that can delay or lock performance tools during initialization. While the Open 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 2000.

Note Image Note

Perflib disables counter by setting the value of Disable Performance Counters for that service to 1. After you have repaired or replaced the counters, you must re-enable them manually by changing the value of Disable Performance Counters to 1.

Perflib does not time the procedure calls of trusted performance counter DLLs This entry applies only to non-trusted DLLs.

This entry applies to all counter DLLs on this system. To adjust the Open procedure time for the counters of a particular service, use the Open Timeout entry.

The value of this entry is also the default value of the Collect Timeout entry.

This entry has a different effect on Windows 2000 than it has on Windows NT 4.0 and earlier. In Windows NT 4.0 and earlier, it determines the Open procedure wait time only for extensible counters. For more information, see Regentry.hlp in the Windows NT Resource Kit 4.0.

Windows 2000 does not add this entry to the registry. You can add it by editing the registry or by using a program that edits the registry.

Tip Image 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.

Related Entries

Page Image

Page Image

Page Image