NT event log test not working consitently

adam_morris · Post by **adam_morris** » Mon Apr 23, 2007 5:41 am

I am using the NT Event log test to test for the completion of backups performed by Acronis True Image Server.
Several application event logs are produced each time a backup runs.

The event I wish to monitor is as follows:
ID: 6
Source: Acronis True Image Server
Description: The description for Event ID ( 6 ) in Source ( Acronis True Image Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Operation has succeeded.

My test has the server name specified, the ID, and "succeeded" in the string test.

The test is performed via RMA.

It works on another RMA server for the same Acronis product and event logs.

I have tried every conceivalble variation in the test - ie connection password or not, including string test or not etc.

The test did work once for this particular RMA server.

Both servers are running the same RMA ver 3.35. It also works OK on a local server test.

Have you any other ideas. I need to monitor backups on this server but can not find a reliable way.

Thanks
Adam

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Apr 23, 2007 6:06 am

Could you explain what does it mean - "test does not work". Do you see any error in Reply field? What exact error? What exact status does test return? What does it mean "The test did work once for this particular RMA server"? The test returned the "Bad" status once? Please note: HostMonitor changes test status to "Bad" only when it has found NEW event(s) that satisfies all specified requirements. If, after the next probe, the monitor does not find a new "Bad" event, it changes the test status to "Ok".

Regards,
Max

adam_morris · Post by **adam_morris** » Wed Apr 25, 2007 8:52 am

The test is reversed.

So, if it does not find a succesful event at 08:00 am it produces a bad test result. It is doing this, even though good test events are being logged.

On the occasion it did "work", the test found the event and reported a good test result including the description (test set to use reply).

I have ran test backups, created the sucessful event several times and the test does not read the event and report a good test.

KS-Soft · Post by **KS-Soft** » Wed Apr 25, 2007 12:51 pm

We are checking our source codes, do not see anything wrong yet...
Either "Ok" or "Bad" status means HostMonitor is able to connect to remote system and retrieve information from NT Event Log. If some events trigger "Ok" status while another events do not, I assume there is some difference between these events.

Regards
Alex