Installer fails: generate detailed logging to investigate the cause

Problem

When you use the installer to install Blueriq, it ends prematurely or it returns an error message. When it is unclear why this happens, you can generate detailed logging of the installation process to further investigate the cause.

This will not solve your problem directly, but it can be required to determine the root cause in order to solve the problem you are experiencing.

Solution

First, check these things:

You are installing Blueriq on a supported OS and have the required software installed
You are running the installer as administrator (right-click the Blueriq-<version>.exe and select Run as administrator

If this does not resolve your problem, you can do the following to generate the detailed installation log:

Extract the installer (Blueriq-<version>.exe) to a folder Blueriq-<version>.
Some background information: the installer is simply an archive that you can execute. It contains multiple executables that are executed in a sequence. The first step in the installation is that the archive is extracted. To be able to generate logging, we need to pass extra parameters to one of the executables in the archive, therefore we need to extract it first.
To extract an .exe archive, preferably use 7-Zip.
Open a command prompt as Administrator and navigate to the Blueriq-<version> folder. There you find the following:
- product.msi (this is the actual Blueriq installer)
- other .msi files containing additional components that need to be installed
- installer.bat (the script that is executed to install everything)
- a folder WixOutput containing installation files
Run the following command:
```
installer.bat /l*v install.log
```
The installation will now start normally, with all the logging output written to the file install.log. You can inspect this file for further analysis or provide it to support.