If the installer successfully creates the product installation directory, the installer writes a set of log files in the product installation directory. Each log file is an installation record for a different component of the product. Examine these log files for a record of any problems that may have occurred during the installation. The installation log files use the following naming formats:
For the log for components specific to a driver:
driver_name_Install_timestamp.log
For the log for components common to all drivers:
odbc_common_platform_Install_timestamp.log
For the log for documentation components:
odbc_doc_Install_timestamp.log
For the log for user interactions with the installer program:
is an abbreviated name of your driver. For example, Mongodb is used for the MongoDB driver.
timestamp
is the date and time the product was installed.
platform
is the platform and version of your product. For example, this value would be solarisx32 for a 32-bit Solaris installation.
nn
is the product version number. For example, this value is 8.0 for the 8.0 version of the product.
If the installation fails completely, the installer does not create the installation directory and writes file named Progress_DataDirect_for_ODBC_nn_InstallFailed.txt in the machine’s default temporary directory (%TEMP%).
If you need help interpreting the contents of these files, contact Progress DataDirect Technical Support.
Installer Console Log
The installer records standard errors and standard output generated during installation to dd_odbc_console_install.log, which is created in the user profile directory. Progress DataDirect Technical Support might ask for this log file to troubleshoot some installer problems.
