msgs - fields not being populated, %1 %2 %3.
list S Aiello
On Monday 16 June 2008, user-ce96540ed38f@xymon.invalid wrote:
Hello All, I normally run bbwin 0.9, but I have just notice a strange error with msgs report output. Seem some fields event log message are not getting populated. I just upgraded a test server to the 0.12 and I see the same issue there as well. An example of this problem would be: bbwin msgs output snippet: application: warning - 2008/06/16 09:20:11 - ASP.NET 2.0.50727.0 (1309) - n/a "Event code: %1 Event message: %2 Event time: %3 Event time (UTC): %4 Event ID: %5 eventlog message seen from the server's event viewer, snippet: Event code: 3005 Event message: An unhandled exception has occurred. Event time: 6/16/2008 9:20:11 AM Event time (UTC): 6/16/2008 1:20:11 PM Event ID: 9f92c98a8695411c99fa81faf5362d50 Thoughts, advice ? ~Steve
has anyone seen the above issue, just curious if i am completely crazy or not. thanks, `steve
list Etienne Grignon
Hi, 2008/6/18 user-ce96540ed38f@xymon.invalid <user-ce96540ed38f@xymon.invalid>:
▸
On Monday 16 June 2008, user-ce96540ed38f@xymon.invalid wrote:Hello All, I normally run bbwin 0.9, but I have just notice a strange error with msgs report output. Seem some fields event log message are not getting populated. I just upgraded a test server to the 0.12 and I see the same issue there as well. An example of this problem would be: bbwin msgs output snippet: application: warning - 2008/06/16 09:20:11 - ASP.NET 2.0.50727.0 (1309) - n/a "Event code: %1 Event message: %2 Event time: %3 Event time (UTC): %4 Event ID: %5 eventlog message seen from the server's event viewer, snippet: Event code: 3005 Event message: An unhandled exception has occurred. Event time: 6/16/2008 9:20:11 AM Event time (UTC): 6/16/2008 1:20:11 PM Event ID: 9f92c98a8695411c99fa81faf5362d50 Thoughts, advice ? ~Stevehas anyone seen the above issue, just curious if i am completely crazy or not.
No you are not crazy. It happens sometimes for some events which seems special. I haven't search the reason for this strange behavior and how to fix it in the msgs agent yet. Regards, -- Etienne GRIGNON