We are using HM 5.88 and we monitor a few x64 2003 SP1 Windows servers.
The problem is the event log events on these 64 bit servers. The RMA picks up new events, but the %Reply% strings for these events are always empty. I have tried various RMA versions and are currently at version 3.35.
Windows Event log missing %Reply% details on 64 bit servers
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Do you get blank Reply field for every EventId you want to monitor or for particular ones only? What exact EventId do you monitor? Does RMA checks EventLog on system where it is running (Windows 2003 x64) or on remote system?spud wrote:Yes, RMA is running on 3 servers that are x64 2003 SP1 Windows.
Regards,
Max
The test is set to monitor Event ID "Any" and Event Type "Error". All of the error events so far have come back with a blank reply. I checked the event log and found error events like this in the recent list of events: 1111, 1215, 7024, 12, 15.
The RMA is loaded on each of the x64 2003 servers and monitors just the Event Log on that local box.
The RMA is loaded on each of the x64 2003 servers and monitors just the Event Log on that local box.
I checked the code and I assume Windows LoadLibraryEx function fails when RMA tries to get message from the DLL. Checked Microsoft manuals, I have not find any information about possible incompatibility. However I assume LoadLibraryEx may fail when 32bit application needs to use some new DLLs that were developed for 64bit system.
What exactly event source(s) do you monitor?
Solution? Unfortunately we cannot offer 64bit RMA right now. We need new version of the compiler that is not available yet.
BTW: Do you see event description using Windows Event Viewer? If description is missed there, then I think its registry problem.
Regards
Alex
What exactly event source(s) do you monitor?
Solution? Unfortunately we cannot offer 64bit RMA right now. We need new version of the compiler that is not available yet.
BTW: Do you see event description using Windows Event Viewer? If description is missed there, then I think its registry problem.
Regards
Alex