Information: Forum is in read-only mode
For details and other support options see

EventReporter 12.0 Build 342 RB - Updated 2011-04-11

Support, Questions and Discussions on EventReporter

Moderator: alorbach

Google Ads

EventReporter 12.0 Build 342 RB - Updated 2011-04-11

Postby alorbach » Mon Apr 11, 2011 4:07 pm


The Rolling Beta program is again open, features and bugfixes will be added continuously. The changelog below helps you to keep track on the changes.
Feel free to test this new rolling beta version, if you are experiencing any problems, kindly let us know via support email ( or this forum.

A note on Win32 and x64 Edition
EventReporter is available for both platforms. Since Build 287, bot Editions are unified in one Setup file, this includes the win32 platform and the x64 platform. If you had win32 installed before, your installation will be upgraded to x64 automatically without loss of any configurations.

:arrow: Download of the rolling beta
:arrow: EventReporter 12.0 Rolling Beta Manual

Below the change since version 11.3:

:!: 2011-04-11 / build 342
:arrow: Features
- Added support for polling EventLog Records in EventLog Monitor V2. This works almost like the old EventLog Monitor, the Eventlog channel is polled frequently and new EventLog records are processed only. By default, the "Subscription Model" is used which processed events in realtime.
- Added support to read and process EVTX files. This requires the new "Eventlog Polling" method in EventLog Monitor V2. It is also possible to update the the EVTX files while MonitorWare Agent is running.
- MonitorWare SETP Protocol extended to V3. If both Sender and Server have V3 or higher, we use UTF8 encoded messages. This maintains the correct character encoding after the messages is received and rebuild internally.
- Added initial support for IPv6 in almost all network relared Services and Actions. This is a major step forward in the evolution of the EventReporter product. All client related network actions will automatically detect IPv6 and IPv4 target addresses. You can also use dns resolution to resolve valid IPv6 addresses. For network related listener services, you can configure IPv4 or IPv6 as protocol. A service can either run as IPv4 or IPv6 based service. In order to support both protocols, you will need to create two services. Currently, RELP and SNMP related services and actions do not support IPv6 yet. This will happen in near future.

:arrow: Bugfixes
- Corrected SSL Error logging in on connection shutdown.
- Added option to add ProcID into SyslogTag for RFC 5424 Header parsing. This was previously default. The Option is disabled by default now making it easier to filter for the SyslogTag.
- Added Performance fix for UTF conversion for empty strings.
Site Admin
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Google Ads

Return to EventReporter

Who is online

Users browsing this forum: No registered users and 1 guest