ELM 5.0 Products

Contents

• Updates
• Known Issues
• Contact Us

---

Updates

The following fixes are included in this release:

5.0.236.1

• Fixed 'Keep no more than N rollover databases' is more reliable.
• Fixed The Scheduler now respects Standard (non day light savings) times.
• Fixed ELM Agents using the ELM Agent user interface to register back to an ELM Server now respect a non-default ELM Agent port.
• Fixed Databases created by ELM will now respect the default location for both the database file and the log file.
• Fixed The ELM Advisor popup notification is more reliable.
• Fixed The Database pruning criteria are more visible.
• Fixed The SNMP MIB file translator is more reliable.
• Fixed ELM Server only installation completes successfully.
• Fixed ELM Event Generator now handles Event Sources with large numbers of Event Identifiers.
• Fixed Importing XML configuration is more reliable.
• Fixed ELM Publisher output can now be viewed correctly.
• Fixed Adding Performance Counter Definitions now allows adding any Performance Object.
• Fixed ELM Event Log Monitor no longer includes a default Command Script Notification Method.
• Fixed Staged ELM Service Agents can now be deployed to another domain.
• Fixed Default database pruning is more aggressive.
• Added ELM Service Agents can now read Vista Security Event logs.
• Added SMTP Mail Notification Method now allows authentication.
• Added The EVT File Collector now uses an MD5 hash to validate its files.

5.0.207.1

• Fixed Exporting an SNMP Collector Monitor Item now results in importable text.
• Fixed Data is saved more reliably during database failover.
• Fixed The Agent Deployment Wizard now defaults to 'update' rather than 'connect' when reinstalling ELM Agents. The wording on this option was made more explicit.
• Fixed The Event File Collector did not respect the ELM Agents cache path and minimum free space properties.
• Fixed The Event File Collector could fill up the ELM Agents c: drive.
• Fixed The Event File Collector could cause the Event Collector to miss events.

5.0.203.1

• Fixed Viewing ELM Publisher Reports and the ELM Web Viewer no longer gives a 'Thread Aborted' message.
• Fixed Viewing Alert and Event data in an archive database created with ELM 4.0 will now use the correct date range.
  
• Fixed The correct ELM Publisher Reports are now included when installing the ELM Event Log Monitor.
  
• Fixed ELM Editor Reports scheduled to output to a file now default to a location with a viewable link in the ELM Web Viewer.
  
• Fixed Dragging and dropping Event Views and Performance Data views into the ELM Editor is more reliable.
  
• Fixed Registering an ELM Server from the ELM Agent user interface is more reliable.
  
• Fixed ELM Server at a glance view in the ELM Console displays more reliably.
  
• Fixed Outages for reinstalled applications are reported correctly.
  
• Fixed The 'Do not show this dialog again' check box for the new Agent Wizard Welcome dialog box is now functional.
  
• Added Scanning for ELM Agent Category assignment is now optional when creating ELM Agents.
  
• Added Users can now email any ELM Editor Report directly, without scheduling the ELM Editor Report.
  
• Added Users can now set the ScheduledReportRenderTimeoutInSeconds for scheduled ELM Editor Reports in appSettings.xml.

---

Known Issues

Upgrading from ELM Version 3.1 and Version 4.0
Prior to installation of an ELM Version 5.0 product upgrade, you must first update to the latest release of ELM 3.1 or ELM 4.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 3.1.308 (upgrading to 4.0, then 5.0 is not required)
• ELM 4.0.243

 

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

VMWare Server
Installing an ELM Service Agent or an ELM Server on a computer running VMWare Server can hang the Operating System, or possibly Blue Screen the underlying Operating System.

Recommended workaround: install the ELM Server or ELM Service Agent (and start up the ELM Server or ELM Service Agent) before the VMWare Server service and instances of virtual machines start.

Windows XP SP2
Changes will have to be made to allow ELM Enterprise Manager 5.0 operations if Windows XP Service Pack 2 is applied. See instructions at our Web Site (http://www.tntsoftware.com/support/windowsxpsp2/default.aspx).

Upgrade from "Only for me" Installation Corrupts ELM
If ELM 3.1 was installed using the "Only for me" application setting instead of the "Anyone who uses this computer" setting, then upgrading to ELM 4.0 will result in a corrupt installation of ELM. To see which setting was selected during setup of ELM 3.1, look for an ELM shortcut in the All Users Programs menu. Typically this is under 'C:\Documents and Settings\All Users\Start Menu\Programs'. If a shortcut appears, then "Anyone..." was selected during install. If the shortcut does not appear, then "Only... me" was selected and the Recommended workaround should be used.

Recommended workaround: Backup the ELM configuration, uninstall ELM 3.1, install ELM 4.0, and restore the saved configuration. For more details, please see 'Backup and Restore the ELM Configuration' in the ELM 3.1 on-line help.

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.

Service Agent Install to NT4
When installing a Service Agent to a Windows NT4 system, if the Agent has a large configuration file, it can cause the NT4 system to crash with a blue screen.

Recommended workaround: Avoid using Performance Alarms and Performance Collectors with Service Agents on NT4 systems. If either of these Monitor Items are required, delete all un-used counters from the appropriate Counters containers. There is one Counters container below each performance object, under Results | Performance Data.

Updating a Service Agent
When updating a Service Agent from the ELM Console, the update may hang and the progress indicator will show the message 'Stopping Agent Service.' This can occur when the TNTAgent.exe process hangs with the TNT Agent service in a 'Stopping' state. The cause of this behavior is currently under investigation.

Recommended workaround: End the TNTAgent.exe process on the computer being updated, and the update will proceed properly.

Upgrading 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, run the ELM Database Wizard on the Actions menu from the ELM Server node in the Management Console and create a new database.

ResrcMon.exe Memory Leak
The Agent Service (TNTAgent.exe) causes ResrcMon.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 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.

When upgrading ELM 3.1 to ELM 4.0, data is not imported from Oracle into SQL
Recommended workaround: Use the Microsoft SQL Server Migration Assistant (SSMA) to migrate the data from Oracle to SQL. The SSMA can be downloaded from Microsoft. A link can be found at http://www.tntsoftware.com/Support/SoftwareReslinks.aspx

After ELM 4.0 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 4.0, it will overwrite portions of the ELM 4.0 installation.

Recommended workaround: If ELM 4.0 has been installed, do not run the ELM 3.1 setup package.

---

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