Solution: Set application ID and classpath properly. Possible Cause: Application ID or Classpath is not properly set. Failed to get credential for id 2_1_CMS - Failed quering attribute from CyberArk Password. Failed to get credential for id 52_1_CMS - Failed quering CyberArk Password, Application ID is empty. Symptom: Checking credential failed with an error message similar to the following: Failed to get credential XYZ, please check the related error logs in probe side.įound the following error messages in the WrapperProbeGw.log: For detailed instructions, see Create and configure an application ID. Solution: Add the applicaition ID to the Safe in CyberArk. Possible Cause: The application ID is not added to the Safe in CyberArk. Symptom: Received an error message " User is not defined" when running the checkCyberArkConn.bat script to test connection. Operation > Data Flow Management > Integrations > Integrating UCMDB with CyberArk Enterprise Password Vault > CyberArk Integration Troubleshooting and Limitations CyberArk Integration Troubleshooting and Limitations