Release Notes - ELM Enterprise Manager 6.5

Contents

• Updates
• Known Issues
• Contact Us

Updates

The following fixes are included in release 6.5.148.1:

• Fixed: The ELM Server will fail to start if there is an error loading its configuration. (1231)
• Fixed: Setting 'maxNumBackups' to 0 in DatabaseSettings.xml is respected. (1228)
• Fixed: Event Alarms are more accurate. (1226)
• Fixed: Notifications are independent of Event View updates. (1210)
• Fixed: Event Collection is more accurate when a single resouce replicates event ids. (1209)
• Fixed: ELM Advisor shuts down correctly. (1208)
• Fixed: Memory leak in the ELM Server was plugged. (1196)
• Fixed: Attempt to create an ELM Editor Report with a quote in the name strips the quote instead of failing. (81)

The following fixes are included in release 6.5.136.1:

• Fixed: Editor reports are no longer limited to 2000 rows. (1202)
• Fixed: Editor reports have better performance. (1198)
• Fixed: Memory leak in the ELM Server was resolved. (1196)
• Fixed: Drag and drop of Event Views to Editor Reports is functional. (1195)
• Fixed: Event View columns shown in the ELM Console are preserved when saved. (1193)
• Fixed: Notification Rules transition to Event Views exactly once on upgrade. (1189)
• Fixed: Added Agent_Description environment variable to Notification Method messages. (1188)
• Fixed: Creating new database preserves ELM Editor Reports. (1186)
• Fixed: Favorites are preserved on upgrade. (1183, 1184)
• Fixed: Event Views with no Include Event Filters should not include any events. (684)

The following fixes are included in release 6.5.128:

• Initial release.

Known Issues

IIS Monitor Does Not Support IIS 7.0
The ELM IIS Monitor currently does not support IIS version 7.0 or newer.

EVT File Collector
Microsoft has changed how the event sub-system is organized on Windows Vista and newer operating systems. EVTX files collected from Vista and newer operating systems cannot be viewed on older operating systems.

Event based monitors not fully supported on virtual agents
If the ELM Server is installed on a Windows operating system prior to Windows Vista and Windows Server 2008, the Event Collector, Event Alarm, and Event File Collector monitors are not supported via Virtual Agents monitoring Windows Vista and Windows Server 2008 or newer Windows operating systems. Due to the same limitation, the ELM Server command line operation /ImportEvt is also not supported in the same system configuration.

Recommended workaround: Deploy Service Agents to the machines to be monitored or install the ELM Server on a newer operating system.

Windows Firewall
Windows XP Service Pack 2 introduced Windows Firewall. Changes may need to be made to allow ELM Enterprise Manager 6.5 to operate when Windows Firewall is enabled.

Installer Error 1303, the installation has insufficient privileges to access this directory
This error can occur when starting the install package after uninstalling the package. The IIS server keeps the directory in use.

Recommended workaround: Run the command "IISReset" then rerun the installation.

Installing a Service Agent on a Server in a DMZ
If attempting to upgrade a Service Agent on a Server in a DMZ or otherwise protected by a firewall, the Agent Deployment Wizard can fail due to the Windows Firewall blocking the port used by RPC.

Recommended workaround: Use the ELM setup package to upgrade the Service Agent. Step-by-step directions 'To install a Service Agent using Setup' are in the ELM online help contents under Administrator Guide | Installation Guide | Installing Service Agents.

Clustered ELM Server may not correctly report its status to Cluster Administrator
If failover takes a long time, Cluster Administrator may report the ELM Server resource as being offline, when the resource is actually online. The cause for this is currently under investigation.

Recommended workaround: Connect to the ELM Server using the ELM Console. Then, in Cluster Administrator, you should be able to right-click the ELM Server resource and bring it online.

Do not use Terminal Services to configure an Exchange Monitor or MAPI Email Notification Method
You should not use Terminal Services to configure an Exchange Monitor or MAPI Email Notification Method. As documented in Microsoft Knowledge Base article 303221, MAPI is not Terminal Services-compliant. As a result, when you configure a MAPI-based item using Terminal Services, the MAPI profile created by ELM is deleted in the background, and that breaks the item. When this happens, you will see the following error message with the Exchange Monitor: Send Exchange Monitor Message returned: 0x80040203, DoMonitor failed with return code, 0x80040203.

Recommended workaround: To correct the problem, you must delete any existing Exchange Monitor(s), and recreate them without using Terminal Services. You can use a remote ELM Console, an ELM Console local to the ELM Server, or remote control software such as VNC or pcAnywhere to configure the Exchange Monitor or MAPI Email Notification Method.

Events may be lost if the database failover occurs
A small number of events (e.g., < 5) may be lost if database failover occurs when using SQL authentication. The problem does not appear when using Windows authentication for SQL Server.

Recommended workaround: Instead of SQL authentication, use Windows authentication for SQL Server (Microsoft recommends doing this for general security reasons, as well).

Invalid Username or Password Error Installing on a Read-only or Backup Domain Controller
When installing an ELM Server or Service Agent (running under a user account) on a Read-only Domain Controller (RODC) or Backup Domain Controller (BDC), setup will try to programmatically grant Logon as a Service rights to the ELM Server service account or TNT Agent service account using the LSA APIs. This will fail because the RODC or BDC has a read-only replica of the SAM, thereby preventing the granting of this right on RODCs and BDCs.

Recommended workaround: Manually grant the service account Logon as a Service rights prior to installation.

ELM Database Maintenance Plan Remains After Upgrade
Upgrading to ELM 6.5 requires new ELM Primary and Failover databases. If the ELM 5.5 or 6.0 database was running the ELM database maintenance plan, then this plan will still be active after the upgrade. Also keep in mind the ELM database maintenance plan runs once per week on Sunday. Therefore recent data, to the point of upgrade, may not be backed up, and should be considered in any action taken.

Recommended workaround: Refer to the ELM 6.5 on-line help for steps to manually remove the ELM 5.5 database maintenance plan.

Cannot Install If System Drive Low On Space
The MSI installer requires an approximate minimum 70MB free space on the %systemdrive% before it will proceed, even if other logical drives have over 70MB free space.

Recommended workaround: Free up disk space on the %systemdrive% and restart install. See the TNT Software web site (www.tntsoftware.com) for recommended system requirements.

Upgrading from ELM 5.5 or 6.0
Prior to upgrading to an ELM Version 6.5 product, you must first update to the latest release of ELM 5.5 or ELM 6.0, depending on which version you have installed. Please check your installation and verify that you are running the latest release available. These are listed below:

• ELM 5.5.141 (direct upgrade to 6.5 is supported)
• ELM 6.0.245

If you are not running one of these releases, please contact your Account Manager at TNT Software.

Contact Us
TNT Software, Inc.
2001 Main Street
Vancouver, WA 98660

Telephone: 360-546-0878
FAX: 360-546-5017
Technical Support: Support@TNTSoftware.com
Sales: Sales@TNTSoftware.com
General: Info@TNTSoftware.com