Perfmon "Unable to connect to Machine"

[Motley]

I have a win 2003 web server that was recently upgraded from 2000. After the
upgrade was completed we lost the ability to remotely monitor perfmon
counters. Everything was working when the system was Win2k. I'm not sure
what the 2003 upgrade may have changed but I have gone over the microsoft
suggestions in their 300702 article and everything is ok. I can ping to and
from the machine that I want to monitor. It's in the same domain as the
machine I want to use to monitor it. I can browse folders and files on this
machine also. Anyone have any ideas?

 

[Paul Bergson]

Two thoughts:

Any event log messages?
Are you usig the perfmon from a 2003 machine or a 2000 machine?

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Motley]

I am using perfmon from a 2003 machine. When I look in the event log for the
machine that is trying to do the monitoring I get the following 2 error
messages.

Event 2003 Perflib

The configuration information for the performance library
"c:\winnt\system32\inetsrv\w3ctrs.dll" for the "w3svc" service does not
match the trusted performance library information stored in the registry.
The functions in this library will not be treated as trusted.

I also get the same exact message except the following changes.
"c:\winnt\system32\aspperf.dll" for the "ASP" service

 

[Motley]

I just wanted to add that I can monitor counters from the machine I want to
monitor to the machine that is supposed to be doing the monitoring.

For example Server A is the monitoring computer
Server B is the machine that is supposed to be monitored

I can run perfmon on server A to any machine except Server B.
I can run perfmon on server B and monitor counters on Server A.

Basically I can monitor one-way. I don't know if this is useful but I
thought I would add that. I also cannot monitor Server B from any other
computer.

 

[Paul Bergson]

Does this help?

http://support.microsoft.com/kb/267831

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Motley]

I did this http://support.microsoft.com/kb/300956/ which is essentially the
same thing except a much more invloved process. This corrected the error I
was seeing on the server I am using to monitor but I still can not connect.

 

[Paul Bergson]

I have nothing else to offer, sorry.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[jineshv]

This worked for me:

1) Grant 'Local Service' full control permissions on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Perflib
2) Start Remote Registry service

 

[forbsy]

This worked for me:

1) Grant 'Local Service' full control permissions on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Perflib
2) Start Remote Registry service

Thanks!! I had the exact same problem and every single troubleshooting step did not help at all. Your solution did the trick!