Log Files Created During Installation
- Last Updated: March 12, 2025
- 1 minute read
- DataDirect Connectors
- ODBC
- Aha! 8.0
- Amazon Redshift 8.0
- Apache Cassandra 8.0
- Apache Hive 8.0
- Apache Spark SQL 8.0
- Autonomous Rest Connector 8.0
- GitHub 8.0
- Google Bigquery 8.0
- + 16
Installation Log Files
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:
DataDirect_for_ODBC_nn_-_version_bit_Install_timestamp.log
where
- driver_name
- is an abbreviated name of your driver. For example,
Mongodbis used for the MongoDB driver.
- timestamp
- is the date and time the product was installed.
- version
- is the platform of your product. This value is 32 for 32-bit installations or 64 for 64-bit installations.
- nn
- is the product version number.
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.