Error 1638: EEM installation fails due to Visual C++ conflict

Products

• Automation Analytics & Intelligence

Issue/Introduction

he CA Embedded Entitlements Manager (EEM) installation fails during the installation of Microsoft Visual C++ Runtime Libraries with return code 1638․​​​​​​​‌‍

ERROR MESSAGE: "VC redist installation returned 1638" "FATAL InstallVCRedistAction VCRedist installation failed with 1638" "Another version of this product is already installed"

SYMPTOMS:

• The installation process stops at the "Install VC Runtime Libraries" step․

• The eiam-install․log shows error code 1638․

CONTEXT: This occurs during a new installation or reinstallation of EEM on a Windows Server where newer versions of Visual C++ redistributables are already present․

Environment

EEM

Cause

ROOT CAUSE: The EEM installer attempts to install a specific version of Microsoft Visual C++ redistributables․ Windows blocks this action with error 1638 because a newer or identical version of the package already exists on the server, causing the entire EEM installation to fail․

• KB Article 227597: Similar Visual C++ conflicts in Broadcom software․

Resolution

1. IDENTIFY CONFLICTING PACKAGES:

   Open Control Panel > Programs and Features (or Add or Remove Programs)․

   Look for the following entries:

   • Microsoft Visual C++ 2015-2022 Redistributable (x64)

   • Microsoft Visual C++ 2015-2022 Redistributable (x86)

   EXPECTED: These packages are typically the cause of the 1638 conflict․

2. UNINSTALL CONFLICTING REDISTRIBUTABLES:

   Right-click and uninstall both the x64 and x86 versions of the Microsoft Visual C++ 2015-2022 Redistributable packages․

   NOTE: If you are unsure which specific version causes the conflict, you may need to temporarily remove other 2015-2019 versions as well․

3. RETRY EEM INSTALLATION:

   Run the EEM installer again․

   EXPECTED: The installer will now place its required version of the C++ libraries without being blocked by Windows Installer error 1638․

4. VERIFY SERVICES:

   Open Windows Services (services․msc) and ensure the following are running:

   • CA Directory - itechpoz

   • CA iTechnology iGateway 4․7

   EXPECTED: Both services should show a status of "Running" and "Automatic"․

VERIFY SUCCESS:

• Access the EEM Web UI via: https://[hostname]:5250/spin/eiam/eiam․csp

• Log in using the EiamAdmin credentials set during installation․

• The login screen should display the "CA Embedded Entitlements Manager" header․

 

 

Additional Information