Information: Forum is in read-only mode
For details and other support options see https://www.adiscon.com/news/support-forum-set-to-read-only-mode/

Event ID 512 never delivered

Support, Questions and Discussions on MonitorWare Agent

Moderator: alorbach

Google Ads


Event ID 512 never delivered

Postby miket » Thu Dec 06, 2007 4:16 pm

I'm running MWAgent 4.1 on a Windows 2000 server and have the windows event log being sent to my syslog server (Kiwi) via TCP. Recently the server was restarted but my syslog server never saw an Event 512 come in from the server. I did receive numerous events in the syslog server from the restarted server about various services starting up, but no 512 message. I checked the restarted server's event log and there was a 512 event in the log. Any ideas why this event message would not be sent? FYI - This same server has sent me 512 events in the past when it restarted but not this time. I thought using TCP would ensure delivery of the message. We create compliance reports using this data and the 512 event is a critical one that we need to report on. Thanks for your help.
miket
New
 
Posts: 3
Joined: Fri May 20, 2005 9:51 pm

Postby alorbach » Fri Dec 14, 2007 12:23 pm

Hi miket,

this sounds very strange. Have you reviewed the application eventlog for error messages from EventReporter?

If there was a failure, you should see an error message there.
However even if the action to send syslog over tcp failed, the last record is not incremented which means the event will be retried next time.

Maybe examining the EventLog will find some more hints.

best regards,
Andre Lorbach
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Google Ads



Return to MonitorWare Agent

Who is online

Users browsing this forum: No registered users and 0 guests

cron