Troubleshooting the Denodo Platform Installer¶
During the installation of the Denodo Platform errors can occur that prevent the installation to complete correctly. For example, the host runs out of disk space during the installation or the user that launches the installer does not have enough privileges to install a Windows service.
To troubleshoot these issues, start the installer in debug mode. To do this, follow these steps:
Make sure that the user account that you use to launch the installer has privileges to create files on the directory where you are installing the Denodo Platform. To test this, you can create a file there and then, delete it.
If you already run the installer, delete the directory where you tried to install the Denodo Platform.
Start the installer in debug mode:
To run the graphical installer in debug mode, open a command prompt (in Windows, an “admin” command prompt) and execute this:
cd denodo-install-6.0 .\jre\bin\java.exe -DDENODO_INSTALL_DEBUG=ENABLED -jar denodo-install-6.0.dat > output-install.log 2>&1
cd denodo-install-6.0 ./jre/bin/java -DDENODO_INSTALL_DEBUG=ENABLED -jar denodo-install-6.0.dat > output-install.log 2>&1
Once the installation finishes, the file output-install.log will contain logging information and more information about what went wrong. You can remove the part
> output-install.log 2>&1from the command so the logging information is printed on the command line.
To launch the command line installer in debug mode, run this:
cd denodo-install-6.0 installer_cli.bat install --debug
cd denodo-install-6.0 ./installer_cli.sh install --debug