ELM 5.5 Products
Release Notes
Copyright 1997 - 2008 TNT Software, Inc.
All rights reserved
Contents
Updates
The following fixes are included in release 5.5.88.1:
- Fixed ELM Editor Scheduled Report results are correctly displayed in the ELM Console.
- Fixed Upgrade from 5.0 can corrupt databaseSettings.xml.
- Fixed Event Views using Event Filters with both Log and Message criteria display correctly.
- Fixed Publisher Reports can have blank pages when printed using IE 7.
- Fixed 'View All' Alerts menu command from At A Glance views now works correctly.
- Fixed Scan meter on the Agent Deployment Wizard did not always show completed status.
- Fixed Configuring a Publisher Report can cause SEH exceptions.
- Fixed Exporting an Editor Report now works correctly.
The following fixes are included in release 5.5.83.1:
- Initial release.
Known Issues
ELM Console requires 16-bit color on Windows Vista
Icons in the ELM Console will display as black boxes on Vista operating systems when viewed in color depths other than 16 bit while Windows Aero user interface is enabled.
No ELM Pre-Configured Items Customized for Windows Vista or Windows 2008
Windows Vista and Windows 2008 have renumbered and expanded the security events generated by these operating systems. This release does not include pre-configured ELM Monitor Items, Filters, Views, or Reports for these updated security events. ELM can be configured for them, including the new Critical and Verbose event levels (types), however this will need to be done by the ELM administrator.
Not Supported on SQL 2008
Testing with SQL 2008 is on-going.
IIS Monitor Does Not Support IIS 7.0
The ELM IIS Monitor currently does not support IIS 7.0 on Windows Vista and Windows 2008.
EVT File Collector
Microsoft has changed how the event sub-system is organized on Windows Vista and Windows 2008. Because of this, the ELM Event File Collector does not collect all .evt files. Only the event files listed under the 'Windows Logs' container in the Windows Event Viewer (eventvwr). Evtx files collected from Vista and Windows 2008 operating systems cannot be viewed on other operating systems.
Windows XP SP2
Changes will have to be made to allow ELM Enterprise Manager 5.5 operations if Windows XP Service Pack 2 is applied. See instructions at http://www.tntsoftware.com/support/windowsxpsp2/default.aspx.
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.
Unsupported on Windows NT 4.0
Unlike ELM 5.0, ELM 5.5 does not monitor Windows NT 4.0. Starting with ELM 5.5, support for Windows NT 4.0 is discontinued.
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 MMC presents a 'Logon' dialog and an error message following a timeout. This may also happen on Windows XP with SP2, which blocks RPC communications.
Recommended workaround: Use the ELM setup package to upgrade the Service Agent. Step-by-step directions are in the ELM on-line help contents under Administrator Guide | Installation Guide | Installing Service Agents.
MSDE Database
If the MSDE database becomes corrupt or reaches its 2 Gb size limit, the ELM Server process may become unusable. The symptom is visible when selecting a view and the MMC becomes unresponsive. If ELM is in database failover and currently using the 'failover' database, then the view will appear to be missing events.
Recommended workaround: Stop the ELM Server Service or end the ELM Server process, and then shrink or backup the ELM database to bring the size below 2 Gb. If the database cannot be reduced in size, have ELM create a new database. To create a new database, open properties of the ELM Server service, select the 'Database' tab, and click the 'Database Wizard' button and follow the steps to create a new database.
RescrMon.exe Memory Leak
The Agent Service (TNTAgent.exe) causes RescrMon.exe to leak memory when Microsoft SQL 2000 SP3 is clustered on a Windows 2000 cluster, if the Agent is monitoring a virtual server. Recommended workaround: Upgrade the cluster operating system to Windows 2003 or apply the hot fix from Knowledge Base Article 883654
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; however, you cannot use Terminal Services.
Setup can accept an incorrect password for the ELM Server's service account
When installing on a Windows 2000 member server of an NT domain, setup can accept an incorrect password for the ELM Server's service account. This causes the following error at the end of setup: 'Error 0x80080005, Server execution failed.'
Recommended workaround: Manually change the service account password to the correct value, and then start the ELM Server service.
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 Server as the ELM Server database and SQL authentication. The problem does not appear when using Windows authentication for SQL Server.
Recommended workaround: Use Windows Authentication for SQL Server (Microsoft recommends doing this for general security reasons, as well).
Invalid Username or Password Error Installing on a Backup Domain Controller
When installing an ELM Server or Service Agent (running under a user account) on a 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 BDC has a read-only replica of the SAM, thereby preventing the granting of this right on BDCs.
Recommended workaround: Manually grant the service account Logon as a Service rights prior to installation.
Multi-selection in Taskpad views may not work
When running the ELM Console on Windows 2000 with MMC 1.2, multi-selection in Taskpad views may not expose all right-click context menu items.
Recommended workaround: Use MMC 2.0, or a Windows XP or Windows Server 2003 system for the ELM Console with MMC 2.0, or switch to the Standard views instead of using the Taskpad views.
Upgrading from ELM Version 4.0 and Version 5.0
Prior to installation of an ELM Version 5.5 product upgrade, you must first update to the latest release of ELM 4.0 or ELM 5.0 depending on which version you have installed. Please check your installation and verify that you are running the latest release available which are listed below.
- ELM 4.0.243 (upgrading to 5.0 first, and then to 5.5 is not required)
- ELM 5.0.236
If you are not running one of these releases, please contact your Account Manager at TNT Software.
After ELM 5.5 installed, ELM 3.1 Can Overwrite Installation
ELM 3.1 does not check for the presence of later versions of ELM. If it is installed after ELM 5.5, it will overwrite portions of the ELM 5.5 installation. Recommended workaround: If ELM 5.5 has been installed, do not run the ELM 3.1 setup package.
Older Product Versions: ELM Version 5.0 Release Notes
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
Sitemap • Privacy
• Terms of Use
© 1996-2008 TNT Software, Inc. All Rights Reserved
This site monitored by
