Troubleshooting the Denodo Platform Installer¶
During the installation of the Denodo Platform, errors may occur that prevent the installation from completing correctly. For example, the user that launches the installer does not have enough privileges to install a Windows service or an antivirus is blocking some files.
This page explains how to troubleshoot issues during the installation process.
If you are going to install the Denodo Platform on Windows Server, you double-clicked
install.exe and the installer did not start, do the following:
install.exeand click Properties
In the tab General, select the check box Unblock.
Click Ok and launch the installer again.
The option Unblock is not available in all versions of Windows server. If this option is not available on your system, keep reading.
Follow these steps to start the installer in debug mode:
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-8.0 .\jre\bin\java.exe -DDENODO_INSTALL_DEBUG=ENABLED -jar denodo-install-8.0.dat > output-install.log 2>&1
cd denodo-install-8.0 ./jre/bin/java -DDENODO_INSTALL_DEBUG=ENABLED -jar denodo-install-8.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-8.0 installer_cli.bat install --debug
cd denodo-install-8.0 ./installer_cli.sh install --debug