Known Installation Issues

ELM is distributed electronically from TNT Software's Web site (http://www.tntsoftware.com). It is packaged into a self-extracting executable that will launch the setup process when executed. It is packaged into a self-extracting executable that will launch the setup process when executed:

• Windows 2003, Windows 2000 and Windows XP, as well as Windows NT computers with the Windows Installer service installed can use the Microsoft Installer package (MSI package).
  
• Windows NT computers without the Windows Installer service require the EXE package. You can download the Windows Installer service for both NT 4.0 and Windows 2000 from Microsoft's Web site.

There are several phases to the installation process:

• Installer initialization
• Package extraction
• Installation Wizard
• Installation of ELM Server service account (including grant of Logon As Service rights)
• Copy file process
• Registration of COM classes
• Instantiation (startup) of ELM Server service
• Database Connection Wizard
• Backup File Removal

Installing an ELM Server, ELM Console and/or ELM Agent using the setup package is a relatively straightforward process that generally takes less than 5 minutes to complete. If you encounter any problems during setup, or if you are unable to complete installation, the first thing to do is ensure that the system you are using meets the minimum requirements for installation of the component.

To diagnose problems with setup, you must use the Windows Installer package (.MSI file). This file supports a command-line option that can generate a trace file of setup activity. If you are running on Windows NT, you will need to first install the Windows Installer service (see link above) before you can use the MSI file.

» To run setup with tracing enabled:

1. Launch the MSI file fro a command prompt using the following command line switch:
   
   EEM50_XXX.MSI /L*V C:\Temp\MSITrace.txt TRACEFILE= c:\temp\ELMTrace.txt
   
   
2. When setup halts or encounters a problem, cancel or clear out of any dialog or other error messages.
   
3. Then, open the trace files and attempt to determine the failure point and the cause of failure. The traces file may not be readily decipherable, so we encourage you to contact TNT Software's Product Support Group for assistance.