RMA error 301 ?
-
- Posts: 25
- Joined: Fri Oct 03, 2003 5:29 am
RMA error 301 ?
Dear,
We have setup HM 4.10 to monitor a few Win2k-servers through an agent.
Tests like Drivespace etc work correctly. However with one server (not the server with the agent) HM is unable to check the Eventlog. It shows the following reply:
"RMA: 301 - Win32 Error. Code:38."
It occures with System, Application and Security eventlog. Sometimes this happens on another server too and it never occures on the third server.
The agent is installed as a service with the Administrator-password as logon. What can this be ?
We have setup HM 4.10 to monitor a few Win2k-servers through an agent.
Tests like Drivespace etc work correctly. However with one server (not the server with the agent) HM is unable to check the Eventlog. It shows the following reply:
"RMA: 301 - Win32 Error. Code:38."
It occures with System, Application and Security eventlog. Sometimes this happens on another server too and it never occures on the third server.
The agent is installed as a service with the Administrator-password as logon. What can this be ?
I not sure I understand everything correctly.
Strange error code, it means "Reached the end of the file.". What version of RMA do you have installed? 1.07?
Regards
Alex
However with one server (not the server with the agent) HM is unable to check EventLog ...
I do not understand test performed by agent or by HostMonitor? Probably you want to say that HostMonitor installed on system A checks system C using agent installed on system B? HM(A)<->RMA(B)<->Target(C)?The agent is installed as a service ...
Strange error code, it means "Reached the end of the file.". What version of RMA do you have installed? 1.07?
Regards
Alex
-
- Posts: 25
- Joined: Fri Oct 03, 2003 5:29 am
Yes, the sketch is correct.
The error is shown as reply when target(c) is being tested.
There are two other targets, like target(c). One of them shows this error once in while, but the last target works correctly all of the time...
Hostmonitor v4.10
RMA Manager v1.02, Agent v1.07 (I didn't know the agent and the manager could be different versions?)
The error is shown as reply when target(c) is being tested.
There are two other targets, like target(c). One of them shows this error once in while, but the last target works correctly all of the time...
Hostmonitor v4.10
RMA Manager v1.02, Agent v1.07 (I didn't know the agent and the manager could be different versions?)
I don't know am I right but I have just one idea. Error appears if system (or user) clears Event Log at the same time when RMA performs the test.
On the other hand system does not clear Event Log automatically, it just overwrites old records...
May be you have some software that checks log and removes unnecessary records? It can be reason for error.
Could you check Event Log settings on system where error never appears and settings on system where error appears?
Regards
Alex
On the other hand system does not clear Event Log automatically, it just overwrites old records...
May be you have some software that checks log and removes unnecessary records? It can be reason for error.
Could you check Event Log settings on system where error never appears and settings on system where error appears?
Regards
Alex
-
- Posts: 25
- Joined: Fri Oct 03, 2003 5:29 am
Dear sir,
Ok, the RMA connection problem is now narrowed down to 1 machine. (The target with continuous errors had the wrong host-name
Maybe something for the ToDo-list: show a plain error message?)
Now, on one machine, I check the application-log, security-log, and the system-log. Only the system-log gives the error: RMA: 301 - Win32 Error. Code: 38. I created a new test, I copied the test from another server, but all with the same result. I have asked my collegue to quit clearing the Eventlog everytime Hostmonitor tries to check it
and there are no tools installed to clean the Evenlog automatically.
Any suggestions?
Ok, the RMA connection problem is now narrowed down to 1 machine. (The target with continuous errors had the wrong host-name



Now, on one machine, I check the application-log, security-log, and the system-log. Only the system-log gives the error: RMA: 301 - Win32 Error. Code: 38. I created a new test, I copied the test from another server, but all with the same result. I have asked my collegue to quit clearing the Eventlog everytime Hostmonitor tries to check it

Any suggestions?
Most of tests display error message, I will check why Event Log displayed error code. Probably it could not retrieve error description for some reason...Maybe something for the ToDo-list: show a plain error message?
Could you try to setup HostMonitor to perform this test? Will error appear as well?
Regards
Alex
-
- Posts: 25
- Joined: Fri Oct 03, 2003 5:29 am
Sorry for not making myself clear. It is hostmonitor who checks the eventlogs, not I. The errors are not shown in the eventlogs, but in the Hostmonitor-panel as reply-value.Metallator wrote: check the application-log, security-....
In other words: Hostmonitor checks the eventlogs. The application-logs are being checked ok, but when he tries to check the system-log it shows the RMA-error.
Yes, I understand. But in your situation HostMonitor does not check the log directly, it sends request to RMA and RMA perform the test.
Could you setup HostMonitor to perform this test directly (without using RMA)? If HostMonitor will work properly, we can assume there some mistake in RMA. If HostMonitor will display the same error...
Regards
Alex
Could you setup HostMonitor to perform this test directly (without using RMA)? If HostMonitor will work properly, we can assume there some mistake in RMA. If HostMonitor will display the same error...
Regards
Alex
-
- Posts: 25
- Joined: Fri Oct 03, 2003 5:29 am
Glad its solved. But we still don't know the reason...
I think you know this joke but may be not
Alex
I think you know this joke but may be not
RegardsThere were an engineer, a manager and a programmer driving down a steep mountain road.
The brakes failed and the car careened down the road out of control until it came to a halt by running against a cliff.
They all got out, shaken by their narrow escape from death, but otherwise unharmed.
The manager said, "to fix this problem we need to organize a committee, have meetings, and develop a solution along with a mission statement."
The engineer said, "no, that would take too long, and besides that method never worked before. I have my pen knife here and will take apart the brake system, isolate the problem, and correct it."
The programmer said, "no, I think we should push the car back up the road and see if it happens again."
Alex
-
- Posts: 25
- Joined: Fri Oct 03, 2003 5:29 am