Event 1010 in Application Log

[Ron_54]

I am getting this error on one server and I can not find a resolution to it.

Event Type: Error
Event Source: Perflib
Event Category: None
Event ID: 1010
Date: 1/28/2003
Time: 9:45:30 AM
User: N/A
Computer: COMPUTERNAME
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

Microsoft says it is with CIM 3.5 and earlier but I am running 7 SP1 and 6.1 agents.

Thanks in advance,
Ron

[Jorge Rivera_2]

I'm also having this issue and can not find how to stop this error from popping up. It's only happening on my 2000 servers.

[Martijn Stuart · Accepted solution]

Ron,

I've had the same problem.
When I checked the performance subkey in the registry for the TCP service, the "disable performance counters" key was set to 1. I'v set the value to 0 and rebooted the machine. Problem solved !! It seems that processes trying to read the performance data failed to do so because of the fact that the perfcounters for this object were disabled.

The following is the .reg file you cab use to add the correct value in the registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Performance]
"Disable Performance Counters"=dword:00000000

Let me know if it worked out for you !

[Ron_54]

It worked! Thanks!

[Chun Siew]

I'm having the same issue, but with the collect procedure for "Spooler". I looked at the registry based on Martijn Stuart's reply. However, I do not have the "Disable Performance counters" key under Spooler\Performance. Can I safely add that key?

Any thoughts on that Martijn?

Thanks in advance:
Chun

[Jeff Wilson_3]

We have had this error on all servers installed with Smartstart 6.0 and above.

The error used to occur on versions below 3.5

Hp have escalated the problem to Microsoft but I have no information how this is progressing.

Initially we thought the registry fix mentioned in the previous messages had fixed the problem but after a few hours it returned.

[Jon Finley]

The key will work under ANY of the performance areas.

So placing it within the spooler areas should resolve your problem.

Jon

[Darrin Rawls]

This issue is currently being worked by Microsoft. Turns out it must be a bug introduced in Win2k SP3.

[Jeff Mathews]

Just a note that after setting the registry as described above and rebooting, the setting has reverted back to 1. Is this a feature of W2K SP3?

[Hagay Levin]

We Had this error repeatedli (every 5 seconds)on a new proliant, after we installed the softpaq.

disabeling the netowrk interface monitoring (from the hp monitoring tools) fixed the problem.

Sorry I cant give exact details (server model and instractions) - because I'm not near the srver.