If the Encryption Key Manager fails to start, check for a firewall.Either a software firewall or a hardware firewall may be blocking the EncryptionKey Manager from accessing the port.EKM server not started. EKM.properties config could not beloaded or found.1. This error occurs when starting the KMSAdminCmd or EKMLaunch withoutspecifying the complete path of KeyManagerConfig.properties when theproperties file is not located in the default path.Default path on Windows is C:/Program Files/IBM/KeyManagerServer/Default path on Linux platforms is /opt/ibm/KeyManagerServer/2. Re-enter the command to start the KMSAdminCmd and include the completepath of the KeyManagerConfig.properties file. See Appendix B, “EncryptionKey Manager Configuration Properties Files” for more information.EKM server is not started. File name for XML metadata file needsto be specified in the configuration file.The Audit.metadata.file.name entry is missing from the configuration file.To correct this problem, add the Audit.metadata.file.name property to theKeyManagerConfig.properties configuration file.Failed to start EKM.Mykeys. The system cannot find thespecified file.1. This error message occurs when the keystore entries inKeyManagerConfig.properties do not point to an existing file.2. To correct this problem, ensure the following entries in theKeyManagerConfig.properties file point to existing, valid keystore files:Admin.ssl.keystore.nameTransportListener.ssl.truststore.nameTransportListener.ssl.keystore.nameAdmin.ssl.truststore.nameSee Appendix B, “Encryption Key Manager Configuration Properties Files” formore information.Failed to start EKM. File does not exist = safkeyring://xxx/yyyThe error can be caused by specifying the wrong provider in the IJO variable inthe Encryption Key Manager environment shell script.For JCECCARACFKS keystores use:-Djava.protocol.handler.pkgs=com.ibm.crypto.hdwrCCA.providerand for JCERACFKS keystores use:-Djava.protocol.handler.pkgs=com.ibm.crypto.providerChapter 6. Problem Determination 6-3
