Unable to install Gen 8.6 on a VM Server
search cancel

Unable to install Gen 8.6 on a VM Server

book

Article ID: 239019

calendar_today

Updated On:

Products

Gen Gen - Workstation Toolset

Issue/Introduction

Unable to install Gen 8.6 on a server.

The install shield window has the following.

Install wizard for CA Gen 8.6 Completed
The wizard was interrupted before CA Gen 8.6 could be completely installed.
Your system has not been modified. To complete installation at another time, please run the setup again.

 

Environment

Release : 8.6

Component : Gen INSTALL

Resolution

1. Gen installations use Microsoft MSI installer which has the capability to create a log.  Below are 2 possible ways to create the MSI log.

1a. https://docs.microsoft.com/en-AU/troubleshoot/windows-client/application-management/enable-windows-installer-logging

Under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows, create a new subkey "Installer" if it does not exist.
Then under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer, create a new String Value (REG_SZ) with "Value name" = "Logging" and "Value Data" =  "voicewarmupx".

The log file will be written to %Temp%.  For example, TEMP=C:\Users\<YourID>\AppData\Local\Temp

1b. msiexec /i <msipath>\Gen\CA Gen 8.6.msi /l*v c:\temp\msi.log

 

2. Review the end of the MSI*.log file.  In this case the following line was located.

MSI (c) (1C:18) [14:19:29:985]: Windows Installer installed the product. Product Name: CA Gen 8.6. Product Version: 08.6.00. Product Language: 1033. Manufacturer: CA, Inc.. Installation success or error status: 1603.

Now search the entire log for the error 1603 or whatever error number is displayed.  The search found the following section of entries.

MSI (s) (4C:60) [14:19:21:111]: Doing action: getJREDir
Action 14:19:21: getJREDir. 
Action start 14:19:21: getJREDir.
MSI (s) (4C:60) [14:19:21:126]: Creating MSIHANDLE (12) of type 790542 for thread 6496
MSI (s) (4C:F4) [14:19:21:126]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI2F0.tmp, Entrypoint: getJREDir
MSI (s) (4C!54) [14:19:21:173]: Creating MSIHANDLE (13) of type 790531 for thread 3668
Opening the root registry key for JRE.  SOFTWARE\JavaSoft\Java Runtime Environment
MSI (s) (4C!54) [14:19:21:173]: Closing MSIHANDLE (13) of type 790531 for thread 3668
MSI (s) (4C!54) [14:19:21:173]: Creating MSIHANDLE (14) of type 790531 for thread 3668
Query information for SOFTWARE\JavaSoft\Java Runtime Environment
MSI (s) (4C!54) [14:19:21:173]: Closing MSIHANDLE (14) of type 790531 for thread 3668
MSI (s) (4C!54) [14:19:21:173]: Creating MSIHANDLE (15) of type 790531 for thread 3668
JRE key contains 2 subkeys
MSI (s) (4C!54) [14:19:21:173]: Closing MSIHANDLE (15) of type 790531 for thread 3668
MSI (s) (4C!54) [14:19:21:173]: Creating MSIHANDLE (16) of type 790531 for thread 3668
Found subkey 1.8 at 0
MSI (s) (4C!54) [14:19:21:173]: Closing MSIHANDLE (16) of type 790531 for thread 3668
MSI (s) (4C!54) [14:19:21:173]: Creating MSIHANDLE (17) of type 790531 for thread 3668
Found subkey 8.0.322.6 at 1
MSI (s) (4C!54) [14:19:21:173]: Closing MSIHANDLE (17) of type 790531 for thread 3668
CustomAction getJREDir returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (4C:F4) [14:19:22:001]: Closing MSIHANDLE (12) of type 790542 for thread 6496
Action ended 14:19:22: getJREDir. Return value 3.

The 1603 error occurs when the SOFTWARE\JavaSoft\Java Runtime Environment is being queried.

3. Run regedit and drill down to the SOFTWARE\JavaSoft\Java Runtime Environment and review the keys and values.  The location as been found in one of the following. Computer\HKEY_CURRENT_USER\SOFTWARE\JavaSoft
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft 

4. Reviewing the keys in this location has identified the following products to have created them.

IBM Semeru Runtime Open Edition ... (x64)
IBM Semeru Runtime Open Edition ... (x86)
AdoptOpenJDK

5. Open the Add/Remove Programs and locate any of these products.  If they exist, uninstall them.  Installing Gen will proceed normally to a successful installation.  Re-install any of the products that are needed.