search cancel

ETPKI Library Installation on Windows Server Fails

book

Article ID: 133850

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On SITEMINDER

Issue/Introduction

Following an installation of the r12.8.x SSO SDK on a standalone host, you attempt to install the ETPKI libraries.  The setup.exe job completes, however the directories were not created.


EXAMPLE:


setup.exe install caller=01010101 instdir=C:\ETPKI veryverbose


There is no "C:\ETPKI" directory created once the job completes.

Cause

If there is a "CAPKI5\InstallDir" registry key present in the registry, the setup.exe will use that path rather than the path defined in the "InstDir=<Path>" switch in the command itself.


EXAMPLE:


Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Shared\CAPKI5\InstallDir

Value: C:\Program Files\CA\SC\CAPKI


Command: setup.exe install caller=01010101 instdir=C:\ETPKI veryverbose


ETPKI will install in "C:\Program Files\CA\SC\CAPKI" rather than "C:\ETPKI" because that is where "InstallDir" registry setting is pointing.

Environment

Release : 12.8.x

Component : SITEMINDER -SDK

Resolution

The installation should be completing properly.  You can delete the [HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Shared\CAPKI5] registry and then re-run setup.  This will ensure the ETPKI libraries are placed in the directory of your choice.  This may impact other applications.