RMA Fails on WIN2003 Servers

[MADS]

Hey,

I installed RMA on 3 server and all 3 gives the same problem:

Faulting application rma.exe, version 0.0.0.0, faulting module kernel32.dll, version 5.2.3790.0, fault address 0x000249d3.

Anybody?
Thx
Marc

[KS-Soft]

As usually 1st question is - what version of the agent do you use?
2nd question - where and when do you see such error? RMA's log? NT Event Log? When? Right after startup?

Regards
Alex

[MADS]

I'm sorry.

The version is the latest the one, comming with HM 5.66, Version 3.15.

The error I send was fount in nt event log
It seems the agent is working for a little while and then stops returning this error.

Regards,
Marc

[KS-Soft]

Fault address is outside of RMA's code, so we cannot trace the problem using this information.
What Windows do you use? Service Pack? Do you have installed some antivirus monitor or personal firewall?
What test methods, actions do you execute using agent?

Regards
Alex

[skyline]

I am trying to monitor a server at a client site behind a ISA firewall. Port 962. Windows 2003 SP1. HP running "foundations" a SNMP app I guess. I never have been able to get the RMA client, Version 3.15, to connect. I do have another server I am monitoring successfuly on the same network on port 961. Here is the errors I am getting from the client's server:


The system has detected the following event:

SNMP Trap: 11004

Date time: 02/09/2006 01:33:50 PM
Computer: JMMLAN
Source: Foundation Agents
Type: Informational
Category: (4)

Description:
An 'Application Error Trap' signifies that an application generated an operating system exception.

Details:
The HP Management Agents have detected a process exception: PID: 3836 - DESC: rma


the Application log shows the following when SNMP is turned off:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 2/9/2006
Time: 2:17:45 PM
User: N/A
Computer: JMMLAN
Description:

Faulting application rma.exe, version 0.0.0.0, faulting module kernel32.dll, version 5.2.3790.1830, fault address 0x00015dea.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[KS-Soft]

Looks like MADS found solution.
MADS, could you please tell us what was the reason of the problem?

I never have been able to get the RMA client, Version 3.15, to connect

Does it means RMA crahes every time HostMonitor sends request to the agent?
Do you have any non-standard sock software installed? Like real-time antivirus monitors, personal firewall, content monitoring software?

PS If you want to post some huge logs, screen shots, etc, please send mail to support@ks-soft.net. Do no use forum for such purpose

Regards
Alex

[skyline]

This server had microsoft proxy client intsalled on it but we removed it. It has no personal firewall. Just standard norton corporate antivirus, no content monitoring software. This is a hp server with hp's server management software.

How do I know if the RMA client is crashing? There are no logs in the RMA folder.

[KS-Soft]

How do I know if the RMA client is crashing? There are no logs in the RMA folder.

If you start application and you see window on screen, it means application is running.
If window and tray icon disappears, it means application crashed. Usually system reports some error when it terminates the application.
According to your logs (you posted before), RMA crashes. That's why I asked when exactly it crashes.

Just standard norton corporate antivirus

It often leads to various problems

Regards
Alex

[skyline]

When you say start the application do you mean rma.exe or rma_cfg.exe. When i start rma.exe it tells me somthing about starting a second instance.

I can start the rma_cfg.exe and change things in the window that it brings up, and in the lower right it says service running.

[KS-Soft]

It means you have started agent in service mode and agent is not crashed, it works.
So, what exactly the problem? Agent is running, port on firewall is opened but HostMonitor cannot connect to the agent? Could you check log1.txt, log 2.txt files in RMA's directory? Any messages? Make sure logging is enabled (using rma_cfg.exe utility)

Regards
Alex

[skyline]

We got it fixed. We had to add the default gateway address to the network card properties under windows. Now the RMA manger and Host monitor can connect to the client on this remote server.

[KS-Soft]

Glad to hear this

Regards
Alex