Skip to content

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.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

Operation Failed Error While Assigning the New Badge Number to the Existing Badge Type

Operation failed.Please Check logs for more details. ERROR (0,0) : Failed to execute PSBusComp request ERROR (91,37) : Error saving Component Interface. {BADGE} (91,37) ERROR (6555,1) : Badge {BADGE_TYPE} number {BADGE_NUMBER} is already assigned. (6555,1)

There should not be a record with the same Effective Date and Effective Sequence within the same badge type.

Resolution: If the Date/Sequence pair already exists for the same badge type, provide a different Effective Sequence.

Test Connection with PeopleSoft Managed System Fails

The following error message appears, when you try to establish test connection with the managed system:

bea.jolt.JoltException: NwHdlr: ERROR: When environment variable TM_ALLOW_NOTLS is not set, an SSL connection must be specified

Resolution: The new release of PeopleSoft has Link Level Encryption (LLE) disabled by default. As a result, Tuxedo client/server generates an error if it detects that LLE is being used. Therefore, ensure to add -DTM_ALLOW_NOTLS=Y in the Java options of your app server.

Test Connection or Aggregation Fails with a SQL Query Error

The following error message appears if the user does not have minimum permission:

Error in SQL Query: User might not have permission to access the table mention in the query

Resolution: Ensure that the permissions mentioned in the Required Permissions section are provided.

Operation Failed Error While Updating the Phone Number or Email

The following error message appears when updating the phone number or email even after the required permissions are provided to the Minimum Permission Account:

Operation failed. Please Check logs for more details." type="Error"

Resolution: Complete the following:

Permission List with Security Set:

  1. Sign in using the administrator account (PS).
  2. Browse for the user profile and search for the Minimum Permission Account.
  3. Select the Roles tab and select the View definition link for the IIQ_HRMS_ROLE Role.
  4. Select the Permission Lists tab and copy the Permission List value (that is, IIQ_HRMS_PERM).
  5. Go to Set Up HCM > Security > Core Row level security > Security by Permission List.
  6. Add the permission list as a new value. Paste the copied permission list name that is, IIQ_HRMS_PERM as the value for the Permission List along with Security Set as the PPLJOB. Select the Security Access Type value for the corresponding security set.
  7. Execute the SJT (Security Joint tables) processes for synchronization purposes. These processes will update security classes and corresponding associations.
  8. Go to Set Up HCM > Security > Core Row level security > Refresh SJT_CLASS_ALL.
  9. Add a new Run control ID by providing any value, and then select Run.
  10. Select Reset to Current Date/Time and then OK to execute the process.

PeopleSoft Connection Fails with an "Invalid Session" Error

When attempting to connect to a PeopleSoft application, the operation fails with the following Jolt service exception:

DOWNbea.jolt.ServiceException: Invalid Session

This issue is most commonly observed in environments using PeopleTools version 8.60 and above.

Resolution:

The resolution depends on whether your PeopleSoft integration is configured to use Transport Layer Security (TLS). Follow the steps for your specific use-case.

Use-Case 1: TLS is Enabled

If TLS is enabled for the connection, the error indicates that the Virtual Appliance (VA) cannot establish a secure connection because it does not trust the PeopleSoft server's certificate.

  1. Obtain the server certificate from the PeopleSoft application server.

  2. Copy the certificate file to the following directory on the Virtual Appliance:

    /home/sailpoint/certificates

  3. Restart the CCG service to apply the changes.

Use-Case 2: TLS is Not Enabled

  1. Add the following key to the Virtual Appliance's Java options to permit non-TLS connections:

    -DTM_ALLOW_NOTLS=Y

    You can do this by creating or editing the java_overwrites.yaml file. The file is located at the following path:

    /home/sailpoint/ccg/java_overwrites.yaml

  2. Restart the CCG service to apply the changes.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.