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.

The operation fails with the following error message:

[ InvalidRequestException ] [ Possible suggestions ] Please check if provided payload has valid attributes [ Error details ] Error while performing operation : Create Account Error code : 400 { "Errors" : [ { "description" : "Invalid, syntactically incorrect or unparseable input provided: department", "code" : "400", "uri" : "urn:oracle:apps:scim:errors:1.0:input:invalid" } ] }

Resolution: Ensure that the provided payload has valid attributes. Use the supported attributes for create and update operations.

The operation fails with the following error message:

["openconnector.ConnectorException: Error while performing operation : Create Account Error code : 409 {\n \"Errors\" : [ {\n \"description\" : \"Exception in IIP API: Ldap request processing failed - PER_IIP_220: An user with username 1213278@sndrvrtest.com already exists in Identity Store\",\n \"code\" : \"409\"\n } ]\n}"]

OR

openconnector.InvalidRequestException: [ InvalidRequestException ] [ Possible suggestions ] Please check if provided payload has valid attributes [ Error details ] Error while performing operation : Create Account Error code : 400 { "Errors" : [ { "description" : "Invalid, syntactically incorrect or unparseable input provided: department", "code" : "400", "uri" : "urn:oracle:apps:scim:errors:1.0:input:invalid" } ] }

OR

Applying List binding LOV_PersonNumber with given set of values

Resolution: Add the following attribute using the Rest API for updating a source:

  • Key= retryWaitTime Value= 60000 in ms, default: 30000 ms

  • Key=maxRetryCount Value=3, default: 3

  • Key=retryableErrors Value=[error messages]

Note

  • The default error message is, "Applying List binding LOV_PersonNumber with given set of values". If you do not mention any other error message, the connector will use the default error message and retry.

  • Ensure to pass the valid personNumber in the provisioning plan and it should not be the existing assigned personNumber( that is, assigned to other accounts).

The operation fails with the following error message when the PersonNumber being passed in the provisioning plan has multiple work relationships.

Applying List binding LOV_PersonNumber with given set of values leads to multiple matching rows for a row of type:UserAccount, key oracle.jbo.Key[ 300000020907599 null null null

Resolution: Add the following attribute using the Rest API for updating a source and then try creating a user with the personNumber.

Key = provisionPersonId Value = true

provisionPersonId is an boolean attribute.

Note
Ensure that you pass the valid personNumber in the provisioning plan. It should not be the existing assigned personNumber that is assigned to other accounts.