| Event Id | 2002 |
| Source | Perflib |
| Description | The open procedure for service "%1!s!" in DLL "%2!s!" has taken longer than the established wait time to complete. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted. |
| Event Information | Resolution steps for Perflib Version: 5.0 Message: The open procedure for service "%1!s!" in DLL "%2!s!" has taken longer than the established wait time to complete. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted. Explanation : The performance counter provider could not return performance counter data within the specified open timeout period. Either there is a problem with this performance counter provider or the service it is collecting data from, or the system was too busy when this call was made. User Action: If the problem continues, increase the open timeout period for this service. By default, the system uses the same open timeout period of 10 seconds (measured in milliseconds) for all services. To override this for an individual service, change the Open Timeout registry entry. To change the registry entry 1) Using Regedit, navigate to the HKLM\SYSTEM\CurrentControlSet\Services\\Performance subkey. 2) Double-click Open Timeout, and then change the length of time in the Value Data box. If the Open Timeout registry entry does not exist, you can create it. To create an Open Timeout registry entry 1) Using Regedit, navigate to the HKLM\SYSTEM\CurrentControlSet\Services\\Performance subkey. 2) On the Edit menu, point to New, and then click DWORD value. 3) Type Open Timeout. 4) Double-click Open Timeout, and then enter a length of time in the Value Data box. Following newsgroup information may help: "If the error is generated by the performance counter of a particular service that are not using, then unload the specific .DLL by using the command unlodctr and remove the performance counter for that service in registry." |
| Reference Links | Event IDs 10006, 10002, 2002, and 8199 Are Logged Every Few Minutes in Exchange 2000 Conferencing Server Microsoft TechNet Document. INFO: Events for Performance Monitor Extensions OS Management Agent for Windows May Cause `Event ID: 2002, Source: Perflib` Error Message In Windows 2000 Server Application Log Perfproc.dll Logs Event 2002 Errors in the Windows 2000 Application Log |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.