1. UNIFYBroker Forum
  2. Bugs
0
Fixed

Log writer for Windows Event Log for non-error events incorrect message

Mark Southwell 14 years ago • updated by anonymous 9 years ago • 3

A small issue I noticed with IdB is that when logging to the Windows event log and logging is set for severity of Information, the text in the event is not correct for the event type, the event text for non-error events is prefix with "an error occurred in module" as below. Small thing.

Log Name: Application
Source: Changes register item processing completed.
Date: 11/04/2011 11:59:22 AM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EDTIDM001VS.test.act.gov.au
Description:
*Error occurred in module: *Change detection engine

Changes register item processing on connector MAZE HUGHES PRIMARY Class connector completed. Duration: 00:00:00.3906200

Tony Sheehy 13 years ago

Reassigned for confirmation of completion.

Adam van Vliet 13 years ago

Can still see the following in WinEventLogWriterBase:

private const string EventLogTemplate = "Error occurred in module: {0}{1}{1}{2}";
Tony Sheehy 13 years ago

Message for the WinEventLogWriterBase updated to reflect the type of entry being logged.

Customer support service by UserEcho