RMA : Cannot Read Data (HM.5.7, RMA.3.15)

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
Svend
Posts: 38
Joined: Fri Sep 23, 2005 5:00 pm

RMA : Cannot Read Data (HM.5.7, RMA.3.15)

Post by Svend »

Using HM 3.70 on Server2003, RMA 3.15 on Win2000 Server.
When trying to test CPU Utilization I get RMA:Cannot Read Data

Other tests (Disk space free, TCP connections, URL tests ) are working with this agent
Timeout on agent is set to 120 (seconds I assume).

I am trying the test on two systems - one is the Win2K server with the agent, another is on the same site but is an NT4.0 Server that is refferenced by the agent.

If I log into the server and then stop and restart the RMA service then it responds, but after I've logged out and the screensaver has locked the console it stops responding to this specific test until the service is restarted.

The NT4.0 server needs me to be logged in and throws up a "cannot find js32.dll" message when I refresh it's CPU test. This system does not have an agent on it.
Yoorix
Posts: 177
Joined: Wed Dec 14, 2005 8:28 am

Post by Yoorix »

RMA is started as service?
Probably account that is used to start agent does not have enough rights?

Coud you try to give RMA Agent service an administrator logon account?
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

When trying to test CPU Utilization I get RMA:Cannot Read Data
Other tests (Disk space free, TCP connections, URL tests ) are working with this agent
Such behavior means RMA cannot retrieve information from target system within specified timeout.
Timeout on agent is set to 120 (seconds I assume).
Are you sure? There is timeout specified by rma_cfg utility (on system where agent is running). This timeout specifies the maximum amount of time (in seconds) that agent will keep waiting for the complete request packet from HostMonitor (after initial TCP connection established) before dropping the connection.
But you should check another timeout, timeout that is specified on HostMonitor's side in "Agent Connection Parameters" dialog.
I am trying the test on two systems - one is the Win2K server with the agent, another is on the same site but is an NT4.0 Server that is refferenced by the agent.
Have you installed and started Remote Registry Service? Its not installed by default on NT 4.0. RPC service started? RMA is running under admin account?

Regards
Alex
Post Reply