Process monitor
-
- Posts: 2
- Joined: Mon Aug 25, 2008 10:19 am
Process monitor
Unable to create a process monitor for a server. When I attempt to monitor a proc. on this server and browes for process host monitor locks up and I have to end the task. Any ideas why this might be happening?
Are you sure it complettely locks up? Probably HostMonitor just waits for reply from remote system. Can you want a minute or two?Unable to create a process monitor for a server. When I attempt to monitor a proc. on this server and browes for process host monitor locks up and I have to end the task
Please check the following:Any ideas why this might be happening?
1) HostMonitor (if test is performed by HostMonitor) or RMA (if test is performed by RMA) is started under admins account
2) RPC service is started on the systems
3) Remote Registry service should be started on target system as well
4) perfProc.DLL should be enabled on target system
Microsoft provides "Extensible Counter List" utility: http://www.microsoft.com/downloads/deta ... laylang=en
This utility displays list of DLLs that are used to support Performance Counters, using the utility you may disable/enable specific DLLs.
5) Check if "admin" account has KEY_READ access to the following registry key on target system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows_NT\CurrentVersion\Perflib.
To view/change permissions to the registry key you can use the registry editor utility (Regedt32.exe).
6) no firewall between 2 system blocks TCP ports above 1023
Regards
Alex
-
- Posts: 2
- Joined: Mon Aug 25, 2008 10:19 am
Checked all
I checked and double checked everything in your post. When I turn of the firewall all works. I added the port TCP 1023 and it did not resolve the issue. I added host monitor and it did not resolve the issue. Is there other ports that need to be added?
Nope take that back, even after disabling the firewall it didn't fix the problem.
Nope take that back, even after disabling the firewall it didn't fix the problem.
Actually I said "no firewall between 2 system blocks TCP ports above 1023". This means you should open ports 1023 and higher (e.g. 1023 - 2048) because Windows RPC uses dynamic port mapping.I added the port TCP 1023
If you need to monitor some systems behind firewall, we recommend to use Remote Monitoring Agent (RMA)
http://www.ks-soft.net/hostmon.eng/rma-win/index.htm
Regards
Alex
Hi, I am having similar issues. I have confirmed the six steps above except #4 because the microsoft article says it relates to server 2000 and I am running server 2003.
I can obtain CPU info but I cannot connect to the performance counters. Previously I could get performance counter info when I was running 6.x but I just upgraded to 7.52 and now I cannot.
From the machine I am running hostmon on I can remotely connect to the registry using the same user account that hostmon uses. I can also connect to the remote machine using the performance monitor.
The error I see in the Reply column is "unable to connect to specified machine or machine is offline." When I attempt to create a new performance counter test to the remote machine it instantly replies "unable to connect to machine", so quickly that I don't think the request is even leaving the testing machine (I am attempting to connect through a vpn tunnel with no packet filters).
Thoughts?
I can obtain CPU info but I cannot connect to the performance counters. Previously I could get performance counter info when I was running 6.x but I just upgraded to 7.52 and now I cannot.
From the machine I am running hostmon on I can remotely connect to the registry using the same user account that hostmon uses. I can also connect to the remote machine using the performance monitor.
The error I see in the Reply column is "unable to connect to specified machine or machine is offline." When I attempt to create a new performance counter test to the remote machine it instantly replies "unable to connect to machine", so quickly that I don't think the request is even leaving the testing machine (I am attempting to connect through a vpn tunnel with no packet filters).
Thoughts?
Step #4 applies to Windows XP and 2003 as wellI have confirmed the six steps above except #4 because the microsoft article says it relates to server 2000 and I am running server 2003
"Extensible Counter List" utility for Windows 2003 is included into Windows 2003 Support Tools package
http://www.microsoft.com/downloads/deta ... laylang=en
If CPU Usage test works, then problem should not be related to permissions, network, firewall, RPC service or Remote Registry Service.I can obtain CPU info but I cannot connect to the performance counters
May be there is some problem with PDH.DLL installed on system where HostMonitor is running (CPU Usage test does not use this DLL)...
Can you try to setup Process test method for the same target system?
May be you have specified account using Connection Manager (menu Profiles) and marked "CPU Usage" option while did not mark "Performance Counter" option in the list?
I don't think this problem relates to update... you may easily verify that by installing old version of HostMonitor into different folder.Previously I could get performance counter info when I was running 6.x but I just upgraded to 7.52 and now I cannot
Regards
Alex