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/

MWAgent 4.3 (Build 322) Rolling beta - Updated 2007-01-12

Support, Questions and Discussions on MonitorWare Agent

Moderator: alorbach

Google Ads


MWAgent 4.3 (Build 322) Rolling beta - Updated 2007-01-12

Postby alorbach » Thu Nov 09, 2006 5:46 pm

Hi,

The Rolling Beta program is 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 (support@adiscon.com) or this forum.

A note on Win32 and x64 Edition
MonitorWare Agent is available for 2 platforms. For the win32 platform as before and now also for the [b:cb8ee1acd8]x64[/b] platform. Note that you can not cross update from the win32 to the x64 Version yet. If you want to do so, you can manually backup your registry settings, uninstall the MonitorWare Agent, install the x64 Version and reimport the registry settings.

Download of the Win32 rolling beta
Download of the x64 rolling beta

MonitorWare Agent 4.3 Rolling Beta Manual

Below the change since version 4.2:

:!: 2007-01-12 / build 322
:arrow: Features/Enhancements
- Send SETP Action: Changed Errorreporting style. Previous for every failed connection try, an error Event was generated with Event ID 1005. Now there will only be ONE error on the first occurence of the connection problem. Once the connection is established again, a Success Event (Type Information) will be logged with ID 1012.
- OLEDB/ODBC Action: Added support for MSSQL Stored Procedures. You can now select between a INSERT and Call Statement, which is Microsoft specific for Stored Procedures. This means also this type of SQL Statement will only work if MSSQL is used as database. If you select MSSQL Call Statement, the tablename field will automatically be used as stored procedure name.


:!: 2006-12-21 / build 320
:arrow: Features/Enhancements
- Added New Service: A new Service has been added to fully support the new EventLog of Windows Vista. Currently the Service is just called EventLog Monitor V2 and can only be configured and used on Windows Vista or Windows Longhorn Server. This new Service fully supports the new EventLog structure, the new Channels and so on. Please note that this is the initial release of the new EventLog Monitor, so not all planned options and features have been added yet. The new beta manual will contain some more detailed informations about the new service.
- Forward Syslog Action: Added support for sending syslog messages in compressed form. Added support for syslog-transport-tls framing in the syslog sender when used with tcp and compression (the framing itself can not yet be forced)

:arrow: Bugfixes
- EventLog Monitor: Fixed a bug in the x64 build which could cause problems resolving sids in seldom cases
- WriteNTEventLog Action: Fixed a bug when Source replacement was enabled. Only the first Source was correctly replaced, but not the following sources.
- Setup Issues on Vista: Fixed several minor setup issues which caused problems installing MonitorWare Agent on WIndows Vista.


:!: 2006-12-04 / build 319
======================
:arrow: Features/Enhancements
- EventLog Monitor: Added better support for reading Event sources on Vista. Still some work to do, but most of the Events are correctly read now.
- SendMail Action: Added support for low/normal/high mail priorities

:arrow: Bugfixes
- EventLog Monitor: Fixed a bug in EventLog Monitor in the SID resolving facility. If an event had more than 1 SID to resolve, the resolved names became the same.


:!: 2006-11-23 / build 318
======================
:arrow: Features/Enhancements
- EventLog Monitor: Added code to support dropping control characters from the event log monitor event parameter insert strings and event categories


:!: 2006-11-09 / build 317
======================
:arrow: Features/Enhancements
- Rule Engine: Added new Option in the General (Engine specific) Options to control the Rule Exception handling when a Rule processing fails.
- SETP Server: Added new Option "Notify Sender about Rule Action Error's". Use this option to have Rule error processing control over SETP as well.
Attention! If you enable this feature, older MonitorWare Agent Versions ( 4.2.x and below ) may have trouble sending data over SETP once a Rule Exception occurs! If you intend to use this feature, make sure all MonitorWare Agent Installations are at least Version 4.3.x.
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