Troubleshooting
If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

Error:
ERROR (0,0) : Failed to deserialize GetCertificate request data
Resolution: Check the encrypted field in the source.xml to ensure it has the password,domainConnPassword
values. For example: "encrypted": "password,domainConnPassword"

Error:
Error decrypting password attribute
Resolution: Check the encrypted field in the source.xml to ensure it has the password,domainConnPassword
values. For example: "encrypted": "password,domainConnPassword"

Error:
bea.jolt.JoltException: NwHdlr: ERROR: When environment variable TM_ALLOW_NOTLS is not set, an SSL connection must be specified.
Resolution:
The error occurs because the new release has LLE disabled by default. Therefore, Tuxedo client/ server exits with an error, when it detects LLE is in use.
Note
Add -DTM_ALLOW_NOTLS=Y in the Java options of your app server. For example, Tomcat or Websphere.
- On the VA, create or update the java_overwrites.yaml file located in /home/sailpoint/ccg/
- Add the line: Extra: -DTM_ALLOW_NOTLS=Y
- Restart the CCG service.

Error:
Missing Entitlements in Aggregations with more than 300 entitlement with same prefixed with “AH_”.
Resolution: Add the following entry using the application Debug page: update-source
In the body of the POST, use form-data as follows:
-
Key –
handleSpecialCharsForRoleSearch
-
Value –
true
Note
For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.

There is an error if the Confirm Password field does not match the New Password field.
Resolution: Perform the following:
Go to the user component interface.
Delete the Password field.
Drag and drop the OPERPSWD from PSUSRPRFL_WRK.
Rename the OPERPSWD field to Password.
Regenerate the jars file.

Error:
openconnector.ConnectorException: openconnector.ConnectorException: Could not find property info for: IDTypes
This error appears if the PSOPRALIAS attribute has not been renamed to IDTypes when creating the component interface.
Resolution: The PSOPRALIAS attribute must be renamed to IDTypes.

Error:
Cannot connect to PeopleSoft - Direct application from the Application configuration page with jars location specified.
The jar file that is created may not have the correct folder structure. For example, if the newly created folder is C:\CI
then the Class files must be present under the "C:\CI\PeopleSoft\Generated\CompIntfc"
directory. The jar command needs to be run from the outer directory.
Resolution: In a Command Window enter the following:
cd C:\CI
Run the command:
jar -cvf iiqPeoplesoftCompInt.jar *
When trying to connect the following error message appears:
DOWNbea.jolt.ServiceException: Invalid Session exception
This error occurs when the PeopleSoft server is not accessible and has one of the following reasons:
The application server is down
Resolution: Restart the Application Server by navigating to the application designer and then restarting it for the specified version.
The configuration details are not correct.
Resolution: Enter the correct configuration values for the respective fields.

Error:
Sailpoint.connector.ConnectorException: ERROR (0,0) : Failed to execute PSBusComp request ERROR (91,34) : Error changing value. {IIQ_USERS.IDTypes(2).Attributes(1).AttributeValue} (91,34) ERROR (15,11) : Invalid value -- press the prompt button or hyperlink for a list of valid values (15,11)
Resolution: The error occurs when the EMP_ID provided in the provisioning form is not a valid employee. Provide a valid active employee
in the provisioning form to assign the newly created user.

Error:
Failed to deserialize GetCertificate request data Test connection failed
Resolution: This error during the test connection. Upload the JAR file manually to the CCG/custom folder, and then reboot in order for the source to work in the test connection.