If you encounter a problem while running setup.exe to install the CA SCM server, client, or agent on a Windows platform, you may be asked by Support to collect an MSI installer log. This is easily accomplished by adding two registry keys and knowing where to look for the resulting output log.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to create back up of the registry and ensure that you understand how to restore the registry if a problem may occur. For more information about how to back up, restore, and edit the registry, please review the relevant Microsoft Knowledge Base articles on support.microsoft.com.
Steps to collect an MSI installer log to help you get more information about an error like this:
<Please see attached file for image>
CA SCM setup.exe is a wrapper which calls the Microsoft MSI installer to install the CA SCM Server, Client, and Agent. You can add two registry keys to Windows to enable verbose logging of all actions taken by the MSI installer. This information will help CA Support diagnose an installation problem.
Microsoft MSI installer logs are written to %TEMP%\MSI*.log.
How To configure Windows to generate a verbose MSI installer log file in %TEMP% that will be named msi*.log.
How to analyze the msi*.log file:
Release: SCMNCR99000-12.1-Harvest-Software Change Manager-Named User-Competitive Replacem