This documentation supports the 19.02 version of Service Request Management.

To view the latest version, select the version from the Product version menu.

Troubleshooting CTSA Adapter errors for Identity Request Management

Identity Request Management no longer supported

The Identity Request Management (IRM) module is no longer supported in versions 9.0 and later of BMC Service Request Management. However, IRM continues to be shipped for reference in version 9.1.00 of BMC Service Request Management.

For more information about the end of life of IRM, see Product announcements.

This section describes the problems that might occur while implementing, building, configuring, and installing the CTSA Adapter.

1 - IRM000017E Error in adapter while login; Could not connect to the IDM Suite. The host name provided was suiteHostName and the port number was suitePortNumber

This message appears for the following scenarios:

  • The BMC Identity Management Suite server is not started.
  • The BMC Identity Management Suite host name provided in the OS_HOST parameter of the Adapter Configuration is incorrect.
  • The BMC Identity Management Suite port number provided in the OS_PORT of the Adapter Configuration is incorrect.

Resolution: Start the BMC Identity Management Suite server.

2 - IRM000017E Error in adapter while login; Key must not be null

This message appears when the alias name provided for the KEY_NAME of the Adapter Configuration form is incorrect.

Resolution: Provide a valid alias name for the KEY_NAME in the Adapter Configuration form.

3 - IRM000017E Error in adapter while login; Keystore was tampered with, or password was incorrect

This message appears for the following scenarios:

  • The Keystore password provided in the password file is invalid.
  • The value of the KEYSTORE_LOCATION adapter parameter is invalid.

Resolution: Provide a valid Keystore with a valid Keystore password.

4 - IRM000012E Internal Error: The specified PERSON_MAPPING_METHOD is invalid personMappingMethod

The personMappingMethod value is other than LOGIN_ID or GUID.

Resolution: The personMappingMethod should be either LOGIN_ID or GUID.

5 - IRM000017E Error in adapter while login; com.bmc.idm.ctsa.security.exception.SecurityException: No Unattended Administrator Defined for profile essProfileValue

The value of the ESS_PROFILE specified in the Adapter Configuration is invalid.

Resolution: Provide the correct value of the ESS_PROFILE in the Adapter Configuration.

6 - IRM000012E Internal Error: Person ID does not exist in ESS for LOGIN ID: <ITSM_LOGIN_ID>

This happens when the PERSON_MAPPING_METHOD is LOGIN_ID, and in the ITSM Person does not exist in the BMC Identity Enterprise SecurityStation backend.

Resolution: Create a BMC Identity Enterprise SecurityStation person corresponding to the ITSM person.

7 - IRM000012E Internal Error: Person ID does not exist in ESS for GUID: itsmPersonGuidValue

This happens when the PERSON_MAPPING_METHOD is GUID, and the Person GUID does not match with the GUID in the BMC Identity Enterprise SecurityStation backend.

Resolution: The GUID for the person should be the same in BMC Remedy Action Request System and the BMC Identity Enterprise SecurityStation backend.

8 - IRM000012E Internal Error: Bad version number in .class file

This happens when the Java version used by the Identity Request Management is different from the Java version of the BMC Identity Management Suite that it connects to.

Resolution: Verify the Java version that the Identity Request Management plug-in uses is compatible with the version that BMC Identity Management Suite uses in the armonitor.cfg file.

Was this page helpful? Yes No Submitting... Thank you

Comments