For information about Globalscape, visit www.globalscape.com. |
|
|
For information about Globalscape, visit www.globalscape.com. |
|
The installation log file is intended for debugging purposes and contains messages that may help resolve issues that arise during installation.
During installation and maintenance, the installer creates an Installer.log file in the %TEMP%\<Product Name> directory. For example:
C:\Users\Administrator\AppData\Local\Temp\EFT Server\Installer.log
C:\Users\Administrator\AppData\Local\Temp\EFT Server Enterprise\Installer.log
At the completion of the installation, either due to success or failure, the installer copies the final log to the <InstallDir>\logs directory, if it exists. If the installer fails during an initial clean installation, the <InstallDir>\logs directory may not exist. In this case, the final log file remains in the %TEMP%\<Product Name> directory.
The installer attempts to append to the existing log file on subsequent runs of the installer (e.g., if the user performs a Reinstall). It does this by copying any existing Installer.log file from the installation directory into the Temp directory, writing to it during installation, and then copying it back to the <InstallDir>\logs directory when the installation is finished.
You can write out the same log messages to another log file of your choosing using the /logfile=<Log file> command line switch to the installer. (Refer to Command Line Parameters.)
The installer is capable of writing the same messages that go to the Main Installer Log using the Windows debug logging infrastructure. These messages may be viewed using a utility such as SysInternal’s DebugView application. To enable this logging, the installer must be run from the command line with the /debug switch. (Refer to Command Line Parameters.)
