EventMaster 2.x and MessageMaster 3.x Revision History

EventMaster Revision History

2.8.2 -> 2.8.3 (Feb 14, 2006)

• Server: Changes were all in the MessageMaster back end.

2.8.1 -> 2.8.2 (Feb 2, 2006)

• Server: Changes were all in the MessageMaster back end.

2.8.0 -> 2.8.1 (Jan 31, 2006)

• Console: Fix in Client Agent Install management page to handle session expiry

2.7.9 -> 2.8.0 (Jan 27, 2006)

• Server: Added Client Agent Install push functionality from anywhere you can access the web-based console.
• Console: Better organized management page.

2.7.8 -> 2.7.9 (Jan 22, 2006)

• Server: Changes were all in the MessageMaster back end.

2.7.7 -> 2.7.8 (Jan 16, 2006)

• Client: Additional fields are available in the MessageMaster message generated by the client: event category, begin and end times for consolidated messages, event log entry type, event log audit entry type (Success or Failure).

2.7.6 -> 2.7.7 (Jan 9, 2006)

• Client: Message post time will now be the Event time (when the event happened in the event log), not the time it got to the database.
• Client: Detect and generate a specific message when a corrupt Event Log is encountered.

2.7.5 -> 2.7.6 (Dec 18, 2005)

• Server: Changes were all in the MessageMaster back end.

2.7.4 -> 2.7.5 (Dec 12, 2005)

• Server: Changes were all in the MessageMaster back end.

2.7.3 -> 2.7.4 (Nov 1, 2005)

• Server: Include client computer name in MessageMaster message generated when an error is encountered retrieving EventMaster configuration information.
• Client: Fixed problem retrieving server from which to download EventMaster configuration information via HTTP.

2.7.2 -> 2.7.3 (Oct 10, 2005)

• Client: Fixed problem with Event Log message formatting.

2.7.1 -> 2.7.2 (Jul 28, 2005)

• Client: Netlogon messages with parameters such as %%1311 now translate these cryptic codes into meaningful messages.

2.6.4 -> 2.7.1 (May 24, 2005)

• New Feature: Rate-based Subscription because it ships with MessageMaster 3.2
• Client: EventMaster now sends in new non-critical events to the server every 30 minutes rather than every 4 hours.
• Console: Better accessibility to EventMaster Configuration page from Console Management page.
• Console: Improved defaults for Event Log messages in message selection drop-downs.

2.6.3 -> 2.6.4 (Dec 5, 2004)

• Setup: Access to EventMaster COM+ components was modified to allow successful launching of the component by the anonymous web account if they had not already been launched by users accessing the EventMaster console pages.
• Console: Current version is now displayed on Main Management Page.

2.6.2 -> 2.6.3 (Nov 21, 2004)

• Configuration: Create MessageMaster messages for EventMasterData.asp; a web page that retrieves EventMaster configuration data for EventMaster client services. MessageMaster administrators are, by default, subscribed to these messages when the product is installed or upgraded.
• Setup: Instead of removing and re-installing when upgrading the product, a new EventMaster Server version can be installed on top of the old.
• Setup: Confirm that the sa and ObjectiveSoftware database username and password specified in the installer user interface can connect to the database before allowing the new page of the install dialog to be shown, instead of generating an error message during the actual installation.
• Setup: Remember previously used installation parameters (user names, directories, etc.) when performing an upgrade of the product.
• Client: An Event log message generated by the EventMaster client service was not using the EventMessages.dll to produce correctly formatted Event log text.

2.6.1 -> 2.6.2

• Begin publication of this change log.
• Revised logging of internal errors in the event log so that a link to the online knowledgebase is present.
• Setup: New versions of the installation package can be installed over top of older ones.

MessageMaster Revision History

3.3.9 -> 3.3.10 (Feb 14, 2006)

• Server: Upgraded Delivery Service to .NET

3.3.8 -> 3.3.9 (Feb 2, 2006)

• Server: Eliminate performance bottleneck in accessing database
• Server: Fix string handling issue in message delivery processing

3.3.7 -> 3.3.8 (Jan 31, 2006)

• Console: Fix for new user created incorrectly by management page
• Server: Fix for Delivery Service exception (while logging e-mail failures)

3.3.6 -> 3.3.7 (Jan 27, 2006)

• Console: Better organized management page.
• Server: Added client install service that assists with pushing out EventMaster clients.

3.3.5 -> 3.3.6 (Jan 22, 2006)

• Notification: Fixed issue with links in notification emails expiring after 21 days. Now links sent out in notification emails will continue to work until you purge the message from your database.
• Notification: More flexible delivery limit for your message definitions. They can now be fine-tuned to intervals less than one day.
• Notification: In daily notification emails, rate-based alerts are now shown in blue to be easily differentiated from other alerts.
• Server: Rate-based subscriptions can now be limited to messages that happen on the same machine, or in the same location.
• Server: New system setting for default delivery limit. Now if a machine has been offline for many months, you do not get bombarded with outdated alerts when the machine comes online. Only the last 2 days by default.
• Server: Scheduled tasks on the server now run at 4:59am rather than 11:59pm. Now your morning daily email alerts will contain problems from the entire night as well as the previous day.

3.3.4 -> 3.3.5 (Jan 16, 2006)

• Notification: Link to MessageMaster message definition from notification messages (i.e. Email or Email (text) carrier).
• Notification: Links placed in MessageMaster message definitions are now converted to anchor tags in HTML e-mails and when displayed on the web console.
• Console: Each subscription created may now use a different e-mail address.
• Console: NULL delivery limit error when copying one version's MessageMaster messages to another.
• Logging: Daily e-mail tracing and error reporting has been enhanced. The Daily e-mail MessageMaster trace message is excluded from the default administrator's subscription because it only needs to be referred to when an error message is sent.
• Setup: Added SMTP server authentication to Setup.
• Setup: Remove separate MessageMaster installations (database and web) as setup now supports the ObjSoft database being created on a remote server.

3.3.3 -> 3.3.4 (Jan 9, 2006)

• Delivery: Fix for unnecessary error "309" when the delivery service is being shut down.
• Console: Time zone is now a user preference and is remembered in the database.
• Console: Default time zone for new users is the MessageMaster Server's time zone using the 12-hour clock.
• Console: Displaying time using the 12- or 24-hour clock is also a user preference that can be changed in the database at this time.
• Archive Utility: Optionally, an asterisk can now be specified on the command line and the program will prompt for a password.
• General: Time zone is always specified when user's preferred time zone is not in effect, such as in email alerts.
• Client: Added comments to underlying XML of each message indicating that time elements and attributes are in UTC time zone.

3.3.2 -> 3.3.3 (Dec 18, 2005)

• Server: MSDE support.
• Server: Fixed problem with NTLM SMTP Authentication.
• Server: Improved licensing system.
• Setup: Simplified setup for MessageMaster Listener.

3.3.1 -> 3.3.2 (Dec 12, 2005)

• Server: Stability and performance improvements in Delivery and Router services.
• Server: Corrected error codes 219, 201, 213, and 308.
• Client: Improved queue handling for large volumes of messages.
• Listener: Change Forwarder to Listener in standalone installer for consistent naming.
• Listener: Link to Online Help from Listener Setup program.
• Console: Fixed bug when searching for a workstation name with a space after it.
• Console: Adding a user no longer fails with special characters.
• Console: Application admins can now delete message definitions as well as create them.
• Console: Application drop-down list is now sorted alphabetically.

3.3.0 -> 3.3.1 (Nov 1, 2005)

• Server: Altered permissions on Scheduled Tasks folder during setup so that NETWORK SERVICE has permissions. The lack of permissions were causing Event Log warnings to be generated by Windows Installer trying to detect the MessageMaster Server scheduled task job files.
• Client: Fixed problem causing watching for new MessageMaster message files in the local queue to stop under certain circumstances.

3.2.14 -> 3.3.0 (Oct 10, 2005)

• New Feature: Client now uses HTTP to send messages to the server rather than a file share.
• Console: Search String can now be specified during the Subscription Wizard.
• Console: Rate-based check box no longer available for Exclude filters.
• Console: Fixed error when searching with quotes in the search string.
• Bug Fix: Fixed duplicate key error when two threads were trying to process the same message.

3.2.13 -> 3.2.14 (Jul 28, 2005)

• Console: Fixed problem in Add User feature.
• Console: Corrected typographical error on XML Details page.
• Console: New filters now default to Include filters rather than Exclude.
• Stability: Fix in Delivery service for some environments.

3.1.2 -> 3.2.13 (May 24, 2005)

• New feature: Rate-based Subscription.
• Console: Improved look of Console's Management page.
• Console: Monitoring page now shows size of Delivery Queue as well as Router stats.
• Console: Subscriptions referred to as Subscriptions throughout documentation and console, and not as Agents anymore.
• Console: Better compatibility with non-IE browsers.
• Console: Bug Fix: Improved message that displays when you try to delete a Site that still has Subscriptions against it.
• Console: Online Help link now available for the Message Details (XML) console page.

3.0.4 -> 3.1.2 (Apr 28, 2005)

• New Feature: Added multi-threading in the router for significantly higher message throughput.
• Improved licensing system. New license file required.

3.0.3 -> 3.0.4 (Dec 5, 2004)

• Licensing: Inconsistent grace period in licensing system. An event log message from some MessageMaster Server components indicated that the grace period was 30 days when, in fact, it is 15 days.
• Setup: Revised creating registry entries during setup. In all cases, registry entries for MessageMaster server will be created and saved during product upgrades.
• Console: Current version is now displayed on Main Management Page.
• Console: Improved User Management on Main Management page.

3.0.2 -> 3.0.3 (Nov 24, 2004)

• Setup: Interim check in to fix install bug on Windows 2003 - must include Everyone in the CreatorOwner role in order that random users may launch the ObjSoft Message UI COM+ component.

3.0.1 -> 3.0.2 (Nov 21, 2004)

• Setup: MessageMaster administrators are, by default, subscribed to MessageMaster system messages when the product is installed or upgraded.
• Setup: Instead of removing and re-installing when upgrading the product, a new MessageMaster Server version can be installed on top of the old.
• Setup: Confirm that the sa and ObjectiveSoftware database username and password specified in the installer user interface can connect to the database before allowing the new page of the install dialog to be shown, instead of generating an error message during the actual installation.
• Setup: Remember previously used installation parameters (user names, directories, etc.) when performing an upgrade of the product.
• Setup: When upgrading, allow the user to specify the existing location of the license.bin file without generating an error during installation.
• Setup: A warning in the MessageMaster web site installation script was reported as an error in the setup logging system. It is now a warning.
• Setup: Parent paths in IIS are disabled by default in IIS6 (Windows 2003). The installation process now enables them for the MessageMaster server web site only.
• Console: Correct sample code in comments of Visual Basic module generated by MessageMaster console.
• Console: Cosmetic change adding a space between user and date for last modified date on all edit pages under Message Admin menu.
• Console: Corrected formatting error in initial=true (red text) for EventMaster management page.
• Console: Made Breadcrumb links on Subscription pages more intuitive.
• Console: On Subscription pages, eliminated use of the word Rule, and made consistent use of the word Filters instead.

3.0.0 -> 3.0.1

• Begin publication of Revision History.
• Revised default GiveUpRetry seconds (amount of time before a message is declared unroutable and deleted from the MessageMaster server's incoming message queue) to 4 hours.
• Revised logging of internal errors in the event log so that a link to the online knowledgebase is present.
• Setup: New versions of the installation package can be installed over top of older ones.
• Bug Fix: Incoming messages with characters that are not valid in XML files are handled by substituting the characters with their hex encoded equivalents.