Resolve upgrade failures when log files are not created

During an upgrade, installer log files are typically used to diagnose failures. However, certain conditions may prevent these logs from being created, making it difficult to identify error details. This article explains how to capture error information when logs are missing.

The Commander installer normally creates two log files:
- C:\installer.log regardless of the installation location.
- <Install Directory>\Program Files\Embotics\install_failure.log with details from Commander.
If these logs are not created, the installer may have crashed early. One observed cause is using an unsupported underscore character in a DNS name for a new SQL server, which prevents log creation.
To capture error details without logs, enable console logging:
- Hold down the left CTRL key on your keyboard while launching the installer.
- A console window opens, and messages scroll as the installation proceeds.
If the installer crashes and the error message disappears quickly, take a screen recording during the process. Then review the recording frame-by-frame to locate the error message.