During an attempt to execute the SAFEX command, the following error occurs:
safex.exe -h <EEMSERVER> -u EiamAdmin -p <password> -f EEM_CASCM_APP_CREATION.xml
result:
Please check at least one of the following conditions are met.
*) Install CAPKI using CAPKI installer.
*) Set CAPKIHOME environment variable.
*) Pass valid second parameter to etpki_lib_init function. Ex: if the second parameter is /a/b/c/[lib]cryptocme2.[dll][so][sl], it is assumed that /a/b/c has all the required CAPKI shared libraries
Please check at least one of the following conditions are met.
*) Install CAPKI using CAPKI installer.
*) Set CAPKIHOME environment variable.
*) Pass valid second parameter to etpki_lib_init function. Ex: if the second parameter is /a/b/c/[lib]cryptocme2.[dll][so][sl], it is assumed that /a/b/c has all the required CAPKI shared libraries
Please check at least one of the following conditions are met.
*) Install CAPKI using CAPKI installer.
*) Set CAPKIHOME environment variable.
*) Pass valid second parameter to etpki_lib_init function. Ex: if the second parameter is /a/b/c/[lib]cryptocme2.[dll][so][sl], it is assumed that /a/b/c has all the required CAPKI shared libraries
SafeConfiguratorImpl::init_itech_lib: unable to initialize itech SDK with default configuration
ConfiguratorImpl::init_internal: unable to initialize itech sdk with XML []
ConfiguratorImpl::init_internal: unable to initialize itech sdk with file [(null)]
In some cases, Windows OS may show an error saying "safex.exe has stopped working" and display a dialog box prompt indicating so.
CA Service Management 14.1 and higher
All Supported Windows Operating Systems
The SAFEX command should be executed natively from the directory it was installed in EEM and not from a copy off the install media directory.
Before running any SAFEX command, launch an Administrative Command Prompt and navigate to the direct location where the SAFEX is contained within the EEM install location.
Do not copy the safex.exe file to a local drive. Several instructions and documents may ask a copy be obtained from the install media - please use the directory where safex.exe is originally placed in the initial EEM installation.
By extension, please run safex.exe from the EEM Server as well, and not from any other servers.
The SAFEX command would be located natively in the C:\Program Files\CA\SC\EmbeddedEntitlementsManager\bin directory (assuming a default EEM install setup)