For most users, installing the application is a breeze. The process goes through without a hiccup. For some, however, an issue is experienced at the time of install. In case the installer does not complete and provides no real error message, there is a process you can do to still generate a log of the install. This document discusses the process of generating this logfile.
You will most likely see this issue:
When your downloaded installer file had some form of corruption caused during download.
If you have an incompitiblity present that is causing conflict with the installer.
Regardless of the reason for the failed install, the best feedback to get is an installer log. The below process goes over how to generate an install log file using our provided installer .msi file.
If you used the Telerik Control Panel to install Test Studio, the log was automatically generated for you. Simply open the folder %ProgramData%\Telerik\Installer\Logs and locate the appropriate log file. It will be named something like:
Place this file into a .zip or .rar file and attach it as a file attachment to a support ticket. Once we receive the logfile, we can more easily assist with determining the root cause of the install not completing.
If you're installing using a .MSI file you will need to follow these steps to generate a MSI logfile:
1. Bring up a command prompt window.
a. Click Start > Run.
b. In the prompt, input cmd.
c. Click OK.
You should have a new command prompt console window open. When it opens:
2. Navigate to the folder that the downloaded installer file is saved within.
In the example below, the installer is contained in D:\TestStudio\ but your location on your drive may be different so make sure you are in the right folder before running the below command.
3. Input the following command: msiexec /i installer.msi /limev D:\TestStudio\installer.log
In the above example, replace installer.msi with the exact name for the installer you downloaded from telerik.
In the above example, replace D:\TestStudio\installer.log with the directory path and filename you want the log saved to/as.
4. Once you have the above personalized as we do in the example, press the 'enter' key on your keyboard to begin the install and generate a log.
5. After you generate the file, please compress it to either .zip or .rar format and attach it to your new or existing support ticket.
Once we receive the logfile, we can more easily assist with determining the root cause of the install not completing.