Server Management - Systems Insight Manager
1819504 Members
3208 Online
109603 Solutions
New Discussion юеВ

Perflib 1010 Application Event Log Error

 
Tim McGue
Regular Advisor

Perflib 1010 Application Event Log Error

All,

I've been trying to track down a Perflib 1010 error that appears in the application event log for my servers. The description of the error is:

The Collect Procedure for the "PerfOS" service in DLL "C:\WINNT\system32\perfos.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.

This problem is sporadic in nature. It does appear to be connected to the HP agents (up to 7.0 on the servers).

I did have another Perflib 1010 error that was corrected with this hotfix:

http://support.microsoft.com/?id=831877
see also:
http://support.microsoft.com/?id=819716

Anyone else seeing this problem?

Tim
2 REPLIES 2
Pat Wilson
Valued Contributor

Re: Perflib 1010 Application Event Log Error

Yes. I get similar errors on one of my Win2K backup servers that I had updated to version 7.0 agents. We started having some difficulties with SCSI bus time-outs, so I downgraded the agents to version 6.4. We are still having these eventID 1010 errors though.

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.

I had also come to the conclusion that the NIC agent is causing this, but I am also reluctant to turn it off.

This has been an issue for some time. Check out this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=213943
Tim McGue
Regular Advisor

Re: Perflib 1010 Application Event Log Error

Thanks for the thread. In regards to the Tcpip error the hotfix on 831877 fixed that error for my servers.

I'm getting close to wanting to call in a case for this one too. Anyone else want to jump in?

Tim