How to Debug Elliott Installation with a Log File When It Fails
A - In a situation like this, we suggest that you run the Elliott installation package with the log file option. For example, if you run the Elliott V7.5 update, the installation package name is ELI75UP.EXE. You will use the following command:
eli75up.exe /v"/l*v \"path_to_long_file\""
e.g.:eli75up.exe /v"/l*v \"c:\temp\inst.log\""
As a result, a log file will be generated at the specified path. In addition, you will have a chance to open the log file at the end of the installation. See sample screen below.
View the log files to determine what files are opened and would cause the installation problem.
Just as an FYI, if you have any files open locally on the server, even if those files are opened through the network share, Windows may retain the open files even if you close those locally opened files through the share folders open files interface.
To find out which users are running Elliott directly on the PSQL server, you can bring up the "Task Manager" on the server console and try to locate the Elliott-related processes.
For Elliott 7.x, look for these processes:
- EL700.EXE - Elliott main process
- EL700DP.EXE - Elliott defer process
- EL700RP.EXE - Elliott report process launch from defer processing
- EL700US.EXE - Elliott license user process
- EL800.EXE - Elliott V8 control center process
- EL800P.EXE - Elliott V8 individual task process
- EL800DP.EXE - Elliott V8 defer process
- EL800RP.EXE - Elliott V8 report process launch from defer processing
- EL800RV.EXE - Elliott report viewer process
- EL800US.EXE - Elliott V8 license user process
You also have the option to reboot the server to force the closing of all open files.