Aha! The dreaded PerfLib error! Try this dude:
NT Event Log error-NwPfOpenODIPerformanceData (Last modified: 19FEB1998)
This document (2918062) is provided subject to the disclaimer at the end of
this document.
Issue
In the NT Event Viewer you may notice three STOP errors that the Novell
intraNetWare Client for Windows NT adds to the Event Log. They are:
Date Time Source Category Event User Computer
Perflib None 1005 N/A
Perflib None 1006 N/A
Perflib None 1007 N/A
If you double-click on these errors they will expand to:
Unable to locate the open procedure "NwPfOpenODIPerformanceData" in DLL
"Nwpfctrs.dll" for the "OdiLoad" service. Performance data for this service
will not be available. Error Status is data DWORD 0.
Unable to locate the collect procedure "NwPfCollectODIPerformanceData" in
DLL "Nwpfctrs.dll" for the "OdiLoad" service. Performance data for this
service will not be available. Error Status is data DWORD 0.
Unable to locate the close procedure "NwPfCloseODIPerformanceData" in DLL
"Nwpfctrs.dll" for the "OdiLoad" service. Performance data for this service
will not be available. Error Status is data DWORD 0.
Although these errors do have STOP messages in front of them, they are in
essence purely informational. When Novell's Client installs itself, it
registers the above 3 performance counters with NT. These performance
counters are only used if an ODI driver is being used. So if the machine is
running an NDIS driver, they are still registered, but cannot be loaded
because the ODILOAD service is not being used. Normally you should not see
these errors. However, when NT does a DR. Watson crash, NT will attempt to
reload all of the performance counters and these 3 errors will be
generated. They are not the cause of the DR. Watson, but a result of it. If
you are using an NDIS driver, they can be safely ignored.
A customer has supplied the following solution on how to stop the errors
Remove the following Registry Entry :
Hkey_Local_Machine\System\CurrentControlSet\Services\Odiload\Performance.
This solution has not been tested by Novell. Other customers have reported
that renaming odistats.h, lslstats.h and rdrstats.h will stop the errors.
These are the performance counters files.
Document Title: NT Event Log error-NwPfOpenODIPerformanceData Document ID:
2918062 Creation Date: 09DEC96 Modified Date: 19FEB98 Document Revision: 5
Novell Product Class: NetWare OS Novell Product and Version: intraNetWare
Client 4.0 for Windows NT
Good Luck
G!
"NT_LIST"
<nt_list@ntlwo To: "NT System Admin Issues"
rld.com> <[EMAIL PROTECTED]>
cc:
27/09/2001 Subject: Full app log
17:17
Please respond
to "NT System
Admin Issues"
Guys n Gals
I have a win2k PDC that fills its application log up daily. I get the
following every 10-15 seconds or so....
Event Type: Error
Event Source: Perflib
Event Category: None
Event ID: 1010
Date: 25/09/2001
Time: 12:19:45
User: N/A
Computer: GODZILLA
Description:
The Collect Procedure for the "Tcpip" service in DLL "C:
\WINNT\system32\Perfctrs.dll"
generated an exception or returned an invalid status. Performance data
returned by
counter DLL will be not be returned in Perf Data Block. Exception or
status code returned
is data DWORD 0.
Data:
0000: a7 00 00 00
Thanks for any input
Bryan
Want to unsub? Do that here:
http://www.w2knews.com/rd/rd.cfm?id=unsub
Need a good FAQ? Try this one first:
http://www.ultratech-llc.com/KB/
Want to unsub? Do that here:
http://www.w2knews.com/rd/rd.cfm?id=unsub
Need a good FAQ? Try this one first:
http://www.ultratech-llc.com/KB/
