Lansweeper Alert Reporting engine Keeps sending the same error

[acb_sawyerb]

We have email notifications turned on for event log entries. We have an issue where Lansweeper keeps sending emails several times a day for several days for the same event log entry. As an example we had a server reboot unexpectedly @ 8:44AM on 5/17/2010. I have been emailed this event by Lansweeper more then 10 times since then.

I assume that this is not the intended operation of the alert engine. Seems that Lansweeper is parsing the entire event log on each scan of the server and alerting on old events. I'd imagine that it is desirable to have Lansweeper remember the most recent event seen on the last scan and start scanning from that point forward. This would also reduce load on the server as the whole log would not need to be read, only "what's new"

Bob Sawyer

[Hemoco]

We have found the cause of this problem and are currently testing the fix internally.

[jdaniel]

Is there any update on this..? We are receiving duplicate errors in the event logs on Lansweeper as well, but not on the actual server.. here is a few brief entries of what I'm talking about. Thanks.
-------------------------------------

Event 10009, DCOM Logfile: System Time: 5/27/2010 8:46:48 AM
DCOM was unable to communicate with the computer x.x.x.x using any of the configured
protocols.

Event 10009, DCOM Logfile: System Time: 5/27/2010 8:47:30 AM
DCOM was unable to communicate with the computer x.x.x.x using any of the configured
protocols.

Event 10009, DCOM Logfile: System Time: 5/27/2010 8:46:48 AM
DCOM was unable to communicate with the computer 01XXXXXX using any of the configured
protocols.

Event 10009, DCOM Logfile: System Time: 5/27/2010 8:46:48 AM
DCOM was unable to communicate with the computer 01XXXXXX using any of the configured
protocols.

Event 10009, DCOM Logfile: System Time: 5/27/2010 8:46:06 AM
DCOM was unable to communicate with the computer 01XXXXXX.domain.com using any of the configured
protocols.

Event 10009, DCOM Logfile: System Time: 5/27/2010 8:46:06 AM
DCOM was unable to communicate with the computer 01XXXXXX.domain.com using any of the configured
protocols.

[acb_sawyerb]

Just sent it.

Thanks

[Hemoco]

Could you mail this as an excel file to lansweeper@hemoco.com please.

[acb_sawyerb]

it appears so: this is not wide enough to display is nicely, but I have 2 machines that are doing this. 529 & 147.

9895 401 6008 1 System The previous system shutdown at 5:36:44 PM on 3/29/2010 was unexpected. EventLog 2010-03-29 17:38:11.000
309118 528 6008 1 System The previous system shutdown at 10:27:05 PM on 5/11/2010 was unexpected. EventLog 2010-05-12 07:46:41.000
364051 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
364553 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
367216 152 6008 1 System The previous system shutdown at 3:52:06 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:34:48.000
368825 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
369632 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
374463 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
376656 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
380571 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
382684 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
385534 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
389479 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
392646 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
397358 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
397432 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
401576 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
405017 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
407429 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
409842 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
411718 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000
413986 147 6008 1 System The previous system shutdown at 3:52:42 PM on 5/17/2010 was unexpected. EventLog 2010-05-17 16:35:27.000
418199 529 6008 1 System The previous system shutdown at 8:44:45 AM on 5/17/2010 was unexpected. EventLog 2010-05-17 08:47:08.000

[Hemoco]

Lansweeper only reads the "what's new" events.
Do you see the multiple events in table tblntlogevent?