RMA: 301 cannot retrieve information
RMA: 301 cannot retrieve information
My environment is HOST MONITOR 4.14 on win2000 and RMA-WIN 1.11 on NT4. It worked properly before. When I check windows processes ,it will return "RMA: 301 cannot retrieve information " right now. I can still check others like "windows service" on the same environment. Could u please tell me how to check?Beside this machine (nt4.0) other test on other RMA-win works properly.
I am having exactly the same problem. I am using Host Monitor 4.14 on 2000 with 1.10 RMA (on 2000 instead of NT4). I have a CPU usage test running on all of the machines with RMA, however, I get this same RMA 301: Cannot Retrieve Information error when I attempt a process test. Is there some application or service that RMA and Host Monitor use to communicate back and forth with each other? Thanks.
When I have experienced this problem, I have usually been able to fix it by restarting the RMA via RMA manager. On occasion, I must actually log in to the RMA box and restart the agent from there (using rma_cfg).
Be aware that if you restart too quickly (using rma_cfg on the remote), it will sometimes be unable to obtain port 1055. (Even though the RMA will be in 'RUNNING' state) This can be easily verified by looking at the LOG2.txt file. Its' almost like the STOP had not yet finished releasing the port by the time you click to START. Safest practice seems to be STOP service wait 5-10 second, START service.
We have a group of 60 servers that reboot at 4am. Often I will get this error on 6-7 of these machines. Not always the same ones. I suspect that it has something to do will HM attempting a particular test before the operating system on the remote has fully and completely loaded.
Be aware that if you restart too quickly (using rma_cfg on the remote), it will sometimes be unable to obtain port 1055. (Even though the RMA will be in 'RUNNING' state) This can be easily verified by looking at the LOG2.txt file. Its' almost like the STOP had not yet finished releasing the port by the time you click to START. Safest practice seems to be STOP service wait 5-10 second, START service.
We have a group of 60 servers that reboot at 4am. Often I will get this error on 6-7 of these machines. Not always the same ones. I suspect that it has something to do will HM attempting a particular test before the operating system on the remote has fully and completely loaded.
Last edited by timn on Thu Feb 05, 2004 4:32 pm, edited 1 time in total.
No, HostMonitor and RMA need only TCP/IP protocol to communicate.Is there some application or service that RMA and Host Monitor use to communicate back and forth with each other?
Message "RMA: 301 cannot retrieve information" means that RMA receives request from HostMonitor and HostMonitor receives response from RMA. Code 301 means that RMA cannot retrieve information from target system (cannot retrieve list of processes in your case).
To perform "Process" test sofware must have access to pseudo-registry. There are some additional requirements when software checks remote system (e.g. HostMonitor installed on system A checks system B [HostMonitor (A) <-> (B)] or RMA installed on system B checks system C [HostMonitor (A) <-> RMA (B) <-> (C)]):
- Remote Registry service must be started (on remote system)
- software must be started under administrator's account.
If you are checking local system (local to RMA) and CPU test works fine but Process test does not work, most likelly problem is in perfproc.dll. May be this DLL just disabled. If you have exctrlst.exe utility (included in Microsoft Resource Kit), you may check status of the performance counter DLLs. This utility available somewhere on www.microsoft.com, unfortunatelly I do not remember where.
Regards
Alex
This problem already fixed. Advanced Host Monitor 4.30 that includes RMA 1.14 available at www.ks-soft.net/hostmon.eng/downpage.htmaware that if you restart too quickly (using rma_cfg on the remote), it will sometimes be unable to obtain port 1055.
Regards
Alex
Alex:KS-Soft wrote:"that if you restart too quickly (using rma_cfg on the remote), it will sometimes be unable to obtain port 1055.
This problem already fixed. Advanced Host Monitor 4.30 that includes RMA 1.14 available at www.ks-soft.net/hostmon.eng/downpage.htm
We are running RMA 1.14 on all machines. This seems to have fixed some boxes with the problem but not others. It may be just an issue with configuration on our end.
Regards, Tim
Alex:
Mostly NT, but...
To be fair, the problems may not be HM or the RMA. We discovered a bad switch in our network today that we think has been the source of a great many ongoing intermittent and mysterious errors here.
This switch has now been replaced and I'd like to let things run for a few days before drawing any firm conclusions.
We have been trying to track down the source of intermittent application problems for about 3 weeks. What looked like software/OS bugs was in fact a very confused (or maybe just evil) switch.
Mostly NT, but...
To be fair, the problems may not be HM or the RMA. We discovered a bad switch in our network today that we think has been the source of a great many ongoing intermittent and mysterious errors here.
This switch has now been replaced and I'd like to let things run for a few days before drawing any firm conclusions.
We have been trying to track down the source of intermittent application problems for about 3 weeks. What looked like software/OS bugs was in fact a very confused (or maybe just evil) switch.