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.

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.

-
This error message appears when the Component Interface is not present on the PeopleSoft HRMS Application server:
Cannot find Component Interface {CI_PERSONAL_DATA} (91,2) ERROR (0,0) : Failed to execute PSSession request
Resolution: Ensure that the Component Interface is present on the PeopleSoft HRMS Application Server.
-
The jar file is created but the inflated structure is not properly extracted.
Resolution: Extract the jar file and ensure that the inflated structure is present in the
PeopleSoft/Generated/CompIntfc
directory. If the inflated structure is not properly created, recreate it as mentioned in the Creating the PeopleSoft HRMS Jar File section.

When the supported platform version is Java version 1.6, the following error message appears:
java.lang.UnsupportedClassVersionError: psft/pt8/joa/API: Unsupported major.minor version 51.0 (unable to load class psft.pt8.joa.API)
Resolution: Ensure that the supported platform version is Java 1.7.

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.

The following error message appears if minimum permissions are not provided for Component Interface:
Operation failed.Please Check logs for more details. InvocationTargetException: Method save for Class: PeopleSoft.Generated.CompIntfc.CiPersonalData not able to invoke
Resolution: Ensure that the steps mentioned in Configuring Component Interface Security are performed.

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:
-
Sign in using the administrator account (PS).
-
Browse for the user profile and search for the Minimum Permission Account.
-
Select the Roles tab and select the View definition link for the IIQ_HRMS_ROLE Role.
-
Select the Permission Lists tab and copy the Permission List value (that is, IIQ_HRMS_PERM).
-
Go to Set Up HCM > Security > Core Row level security > Security by Permission List.
-
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.
-
Execute the SJT (Security Joint tables) processes for synchronization purposes. These processes will update security classes and corresponding associations.
-
Go to Set Up HCM > Security > Core Row level security > Refresh SJT_CLASS_ALL.
-
Add a new Run control ID by providing any value, and then select Run.
-
Select Reset to Current Date/Time and then OK to execute the process.

The following error message appears when provisioning an email attribute:
Typed variable declaration : Can't assign sailpoint.connector.peoplesoftv2.PeopleSoftAPI$ComponentInterface to sailpoint.connector.peoplesoftv2.PeopleSoftAPI$ComponentInterface : at Line: 46 : in file: inline evaluation of: ``import sailpoint.object.ProvisioningResult; import sailpoint.object.Provi . . . '' : ci = connector .getCIHandle ( "CI_PERSONAL_DATA" )
Resolution: Perform the following:
-
Remove the psjoa.jar and PeopleSoftHRMS.jar from the lib and lib-connector folders.
-
Remove the jar path from the application.xml file.
-
Place the psjoa.jar and the PeopleSoftHRMS.jar files in in the WEB-INF/lib folder.
-
Use the OOTB rule.
Note
Ensure that there is only one set of jars in the IdentityIQ installation folder (in the lib folder).