KB13916: How to enable additional logging to troubleshoot issues with the MicroStrategy Universal Installer 9.x

The Strategy Installer in Strategy 9.x will create an install.log file by default with the details of the installation and log any errors to this file. However, if there are problems with the Installer prior to the file creation, additional logging is needed to track down the issue.
Follow the steps below to enable detailed logging of the actions performed by the Installer for Strategy Universal 9.x products. The example commands shown below use the bash or ksh console: 

1. Set the environment variables JNILOG=1, ISJELOG=255 and ismpVV=1
   

   
   $ export JNILOG=1
   $ export ISJELOG=255
   $ export ismpVV=1
   

   
   
2. Create a file called setup<InstallerOS>.sp for example "setupLinux.sp" in a Linux environment, "setupsol.sp" on Sun Solaris etc, with the line is.debug=1 and put it in the same folder as the setup ".bin" file.
   

   
   $ echo is.debug=1>setupLinux.sp
   

   
    
   Note: To troubleshoot issues with the uninstaller, place the setup.sp file in the Strategy install directory.
    
   
3. Launch the application using the command is:log to create a log for the installation launcher. Capture the standard and error outputs to log files:
   

   
   $ setupLinux.bin -is:log launcher.log > output.log 2>&1
   

   
   

The launcher.log and output.log files should capture any errors or issues that the Installer faces, and may be provided to Strategy Technical Support for further analysis if required.