25 Troubleshooting Generic Technology Connector Errors

This chapter provides solutions to some commonly encountered problems associated with using generic technology connectors. The information in this chapter is divided into the following sections:

Errors Encountered at the End of the Connector Creation Process
Common Errors Encountered During Reconciliation
Common Errors Encountered During Provisioning

25.1 Errors Encountered at the End of the Connector Creation Process

The following are error messages that may be displayed at the end of the generic technology connector creation process. Each message explains the event that causes or during which the error message is displayed.

An error was encountered while generating the import XML file for generic technology connector connector_name.
An error was encountered while updating the IT resource parameters with the values provided for the run-time provider parameters of generic technology connector connector_name.
An error was encountered while either generating the XML file for generic technology connector connector_name or saving it in the Oracle Identity Manager database.
An error was encountered while importing the XML file for generic technology connector connector_name. The required lock on the import operation could not be acquired.
An error was encountered while saving the information for generic technology connector connector_name. Check the application logs for more details.
An error was encountered while creating a resource object for the generic technology connector connector_name. An existing resource object has the same name as the one being assigned to this resource object.

25.2 Common Errors Encountered During Reconciliation

Table 25-1 provides solutions to some commonly encountered problems associated with the reconciliation process.

Note:

These errors are logged only if you are using the Shared Drive Reconciliation Transport Provider and the CSV Reconciliation Format Provider.

If any of these errors occurs, then the error message is written to the application server log file.

Table 25-1 Common Errors Encountered During Reconciliation

Problem Description (Error Message)	Solution
No run time provider parameters available	Use the Manage Generic Technology Connector feature to check the values specified for the run-time parameters. Then, retry reconciliation.
No design time provider parameters available	Use the Manage Generic Technology Connector feature to check the values specified for the design parameters. Then, retry reconciliation.
Staging directory location is not defined	Use the Manage Generic Technology Connector feature to check the value specified for the Staging Directory (Parent Identity Data) parameter. Then, retry reconciliation.
File encoding is not defined	Use the Manage Generic Technology Connector feature to check the value specified for the File Encoding (Parent Data) parameter. Then, retry reconciliation.
Archive directory location is not defined	Use the Manage Generic Technology Connector feature to check the value specified for the Archiving Directory parameter. Then, retry reconciliation.
Cannot process files as not even fixed-width delimiter has been defined	Use the Manage Generic Technology Connector feature to check if a value has been specified for one of the following parameters: Specified Delimiter Tab Delimiter Fixed Column Width Then, retry reconciliation.
No Parent files in staging directory No files available for reading	Ensure that data files are present in the directory specified as the value of the Staging Directory (Parent Identity Data) parameter. Then, retry reconciliation.
No child data present in staging directory No files available for reading	Ensure that data files are present in the directory specified as the value of the Staging Directory (Multivalued Identity Data) parameter. Then, retry reconciliation.
The Staging directory cannot be accessed. Either the directory path does not exist or necessary access permissions are missing	Ensure that the directories specified as parameter values have the required permissions. See "Shared Drive Reconciliation Transport Provider" for information about the required permissions. Then, retry reconciliation.
Data files could not be read as its File encoding is not supported.	Use the Manage Generic Technology Connector feature to check the value specified for the File Encoding parameter. Then, retry reconciliation.
Not able to parse metadata	Check the metadata (contents of the second row) present in the parent and child data files. There may be a problem with the delimiter used in the files. Fix the problem, and then retry reconciliation.
Not able to parse header	Check the header (contents of the first row) of the data files. There may be a problem in the format of the header. See "Shared Drive Reconciliation Transport Provider" for information about the header format. Fix the problem, and then retry reconciliation.
Current Record is erratic and cannot be parsed	Check the entry that is written to the application server log file. It may contain errors that cannot be parsed. Fix the problem, and then retry reconciliation.

25.3 Common Errors Encountered During Provisioning

The following table provides solutions to some commonly encountered problems associated with the provisioning process.

Note:

Most of these errors are logged only if you are using the Web Services Provisioning Transport Provider and the SPML Provisioning Format Provider.

If any of these errors occurs, then the error message is displayed on the UI and written to the application log file.

Table 25-2 Common Errors Encountered During Provisioning

Problem Description Solution

Problem Description	Solution
Response code: SPML Velocity Properties Not Read Response Description: The SPML template properties could not be read.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Template Not Read Response Description: The SPML template file was not found.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Unknown Operation Response Description: This provisioning operation is not one of the permitted operations: Create, Delete, Enable, Disable, Modify, and Child Table Operations.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: SPML Provisioning Input Null Response Description: SPML provisioning input data is null.	Check if the provider parameters have been correctly specified. Check if provisioning was initiated by direct provisioning or request provisioning. Retry the procedure by using the direct provisioning option.
Response Code: SPML Template Context Processing Error Response Description: An error was encountered while processing the template context for generation of SPML request.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the `DEBUG` level.
Response code: SPML Provisioning Operation Name Missing Response Description: The operation name for provisioning is missing.	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations (providers) but with fewer attributes. Try direct provisioning.
Response code: SPML Provisioning Child Name Missing Response Description: The child name is missing.	You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred. The connector may not have been created correctly. Try creating another connector by using the same set of configurations (providers) but only one multivalued attribute, which is the one that failed the first time. Try direct provisioning.
Response code: SPML Provisioning Child Meta-Data Null Response Description: The child metadata list is null.	You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred. The connector may not have been created correctly. Try creating another connector by using the same set of configurations (providers) but only one multivalued attribute, which is the one that failed the first time. Try direct provisioning.
Response code: SPML Provisioning Child Metadata Problem Response Description: An error was encountered while sorting the child metadata list.	You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred. The connector may not have been created correctly. There is a problem in the order that has been set for the provisioning fields. Try creating another connector with fewer attributes for the relevant multivalued field. Try direct provisioning. After each successful round of provisioning, try adding fields one by one by performing the Manage Generic Technology Connector procedure. The point at which you start facing this issue again identifies the field that is not in the correct order.
Response code: SPML Provisioning ID Missing Response Description: The unique ID is missing.	You are trying to run an operation on a created user. However, the Create User operation itself may not have run successfully and the unique ID (psoID) that was expected as the response was not received. Therefore, the provisioned instance data was not updated in Oracle Identity Manager. Check why this operation failed.
Response code: SPML Provisioning Target ID Missing Response Description: The unique Target ID is missing.	Check the provider parameters that have been entered. TargetID may be missing.
Response code: OIM API Error Response Description: An error was encountered in the Oracle Identity Manager API layer.	Check if Oracle Identity Manager is operating correctly for other operations. Check the connectivity between the Oracle Identity Manager front end and the database. Note: This error is not related to the providers that you use.
Response code: OIM Process Form Not Found Response Description: The process form was not found in Oracle Identity Manager.	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. Try direct provisioning. Note: This error is not related to the providers that you use.
Response code: OIM Process Form Instance Not Found Response Description: The process form instance was not found for the specified form during update.	The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning. If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations. Note: This error is not related to the providers that you use.
Response code: OIM Atomic Process Instance Not Found Response Description: The process instance found is not an atomic process.	The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning. If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations. Note: This error is not related to the providers that you use.
Response code: Column Not Found Response Description: An expected column was not found in the result set.	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. Try direct provisioning. Note: This error is not related to the providers that you use.
Response code: Invalid Provider Response Description: The provider name specified is invalid.	The Provisioning Format, Transformation, or Provisioning Transport Provider in use may not have been registered correctly. Check if you have correctly followed the steps to register the providers. If this error is displayed when a predefined provider is used, then check the directory on the Oracle Identity Manager server for the XML files of these providers. These XML files are in the following directory: OIM_HOME/xellerate/GenericConnector/ProviderDefinitions
Response code: IT Resource Instance Not Found Response Description: The IT resource instance was not found in Oracle Identity Manager.	The generic technology connector may not have been created correctly. Try creating another generic technology connector by using the same set of configurations. Try direct provisioning. Note: This error is not related to the providers that you use.
Response code: Version Not Found Response Description: The required process form version was not found in Oracle Identity Manager.	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. If you have edited an existing connector by adding a new field to an existing data set, then that operation may have failed. Try making the same change again in the connector. Note: This error is not related to the providers that you use.
Response code: Version Not Defined Response Description: The required process form version was not defined in Oracle Identity Manager.	The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. If you have edited an existing connector by adding a new field to an existing data set, then that operation may have failed. Try making the same change again in the connector. Note: This error is not related to the providers that you use.
Response code: Web Service Not Found Response Description: The Web service was not found on the target server. Check the service name and IP address.	Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running.
Response code: Web Service Connection Refused Response Description: The Web service connection could not be established. Check that the server is running and the specified port is correct.	Check if the Web service is running.
Response code: Web Service No Such Method Response Description: The Web service method could not be started. Check the operation name and parameters.	Check the operation name and parameters.
Response code: Web Service Null Parameter Value Response Description: The parameter value passed to the Web service is null.	Check if the provisioning process ran correctly. The Provisioning Format Provider may not have run correctly and, therefore, may have generated NULL output.
Response code: Web Service HTTP Library Missing Response Description: The Web service HTTP library is not included in the classpath.	There is a problem with the Oracle Identity Manager installation. Contact Oracle Support and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.
Response code: Web Service Null Result Value Response Description: The Web service result value is null.	Check if the Web service is running correctly. At present, it is generating NULL output as the response to the Oracle Identity Manager provisioning request.
Response code: Web Service Invocation Issue Response Description: An error was encountered while invoking the Web service.	Check the credentials of the Web service.
Response code: Web Service Target URL Missing Response Description: The Web service target URL required to invoke the Web service is missing.	Check the values of the provider parameters. The Web service URL may be missing. Modify the generic technology connector and provide this value again.
Response code: Web Service Target Method Name Missing Response Description: The Web service target method name required to invoke the Web service is missing.	Check the values of the provider parameters. The Web service operation name may be missing. Modify the generic technology connector and provide this value again.
Response code: Web Service Response XML Parsing Error Response Description: An error was encountered during XML parsing of the Web service response.	Check if the Web service is running correctly. It is generating an SPML response that does not conform to the format specified for the Web service provider.
Response code: Web Service Response ID Error Response Description: Either a unique ID is not getting generated from the Web service, or its value could not be parsed because of an incorrect attribute name in the response XML file.	Check if the Web service is running correctly. For the Create User operation, it is generating an SPML response that does not conform to the specified format. In addition, it is not returning the `psoID` created in the target system. The provider specification for the Web Service provider expects the return of the psoID field.
Response code: Web Service Protocol Connection Error Response Description: An error was encountered in the Oracle-SOAP HTTP connection.	Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.
Response code: Web Service Protocol Processing Error Response Description: An error was encountered while calling the Oracle-SOAP API.	Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.
Response Code: Unable to parse the date Response Description: Error encountered while parsing the date.	The value specified for the Target Date Format parameter is not correct. For information about the date formats that you can specify, see the following Web page: `http://java.sun.com/docs/books/tutorial/i18n/format/simpleDateFormat.html#datepattern`
Response Code: Data Access Error Response Description: A data access error occurred while executing the query or loading the result set.	Check if Oracle Identity Manager is operating correctly for other operations. Check the connectivity between the Oracle Identity Manager front end and the database. Note: This error is not related to the providers that you use.
Response Code: SSL Handshake Did Not Happen Response Description: An SSL handshake did not happen during the secure communication with the target Web service.	Check if the SEcure Sockets Layer (SSL) configuration between Oracle Identity Manager and the target system has been correctly completed. If required, perform the procedure again.
Response Code: Error in Initialization of SSL-Related Properties Response Description: An error was encountered during the initialization of SSL-related properties. The relevant values are read from the "RMSecurity" element in the `OIM_SERVER`/`xellerate/config/xlconfig.xml file.`	Check the configuration entries corresponding to the `RMSecurity` element of the `xlconfig.xml` file.
Response Code: Invalid Web Service Keystore or password Response Description: An invalid keystore name or password was encountered in the `OIM_HOME`/`xellerate/config/xlconfig.xml file.` Check the configuration entries corresponding to the "RMSecurity" element.	Check the configuration entries corresponding to the `RMSecurity` element of the `xlconfig.xml` file.
Response Code: Error Encountered During Web Service Keystore Initialization Response Description: Keystore initialization failed. Credentials of the keystore are mentioned in the `OIM_HOME/xellerate/config/xlconfig.xml` file under the "RMSecurity" element.	Check the configuration entries corresponding to the `RMSecurity` element of the `xlconfig.xml` file.
Response Code: Invalid ID Response Description: An invalid ID is present in the input SPML request.	Check the value specified for the `Target ID` parameter.
Response Code: Object already exists Response Description: This object already exists in the target system.	Check if the object that you are trying to create already exists on the target system.
Response Code: Operation Not Supported Response Description: The requested provisioning operation is not supported.	Check if the target system supports the requested provisioning operation. For information about the types of SPML provisioning operations that can be performed by using the SPML Provisioning Format Provider, see the "SPML Provisioning Format Provider" section.
Response Code: Invalid ID Type in Input SPML Request Response Description: An invalid ID type is present in the input SPML request.	Check the sample SPML request corresponding to the type of request that was sent, and determine if the target system supports all the ID values that were included in the request. You can access the sample SPML requests in the following directory: OIM_HOME/xellerate/GTC/Samples/spml
Response Code: ID in Input SPML Request Does Not Exist in the Target System Response Description: The ID in the input SPML request does not exist in the target system.	Ensure that the `psoID` value that was sent in the request exists in the target system.
Response Code: Requested Execution Mode Not Supported Response Description: The requested execution mode is not supported.	Ensure that the target system supports the execution of requests in synchronous mode.
Response Code: Invalid Container Response Description: The object cannot be added to the specified container. Refer to the log file for more information. Check the value of the "errorMessage" element in the SPML response.	Check if a container corresponding to the container ID specified in the request exists on the target system.
Response Code: Nonstandard SPML Error Response Description: A target-specific error was encountered. Refer to the log file for more information. Check the value of the "errorMessage" element in the SPML response.	Check the value of the `errorMessage` element in the SPML response. This element contains the target system error message that was generated when the error was encountered.
Response Code: SPML Response Is for Asynchronous Mode Response Description: The SPML response is for asynchronous mode, which is not supported for this release.	Ensure that the target system sends responses corresponding to the synchronous mode of request execution.
Response Code: Error Encountered While Parsing Constituent Elements of Web Service URL Response Description: An error was encountered while parsing the constituent elements of the Web service URL. Check if the specified URL contains the protocol, host name, port and the endpoint. Oracle recommends copying the URL from the relevant WSDL file while specifying provider parameter values during connector creation.	Check if the specified URL contains the protocol, host name, port, and endpoint. Oracle recommends copying the URL from the relevant WSDL file while specifying provider parameter values during connector creation.
Response Code: SPML Response failed V2 schema validation Response Description: SPML Response received is not compliant with the SPML V2 standard specifications.	Ensure that the SPML response returned by the target system conforms to the SPML V2 standard specification.

Response code:

SPML Velocity Properties Not Read

Response Description:

The SPML template properties could not be read.

There is a problem with the Oracle Identity Manager installation. Contact Oracle Support, and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.

Response code:

SPML Template Not Read

Response Description:

The SPML template file was not found.

Response code:

SPML Unknown Operation

Response Description:

This provisioning operation is not one of the permitted operations: Create, Delete, Enable, Disable, Modify, and Child Table Operations.

Response code:

SPML Provisioning Input Null

Response Description:

SPML provisioning input data is null.

Check if the provider parameters have been correctly specified.

Check if provisioning was initiated by direct provisioning or request provisioning. Retry the procedure by using the direct provisioning option.

Response Code:

SPML Template Context Processing Error

Response Description:

An error was encountered while processing the template context for generation of SPML request.

Response code:

SPML Provisioning Operation Name Missing

Response Description:

The operation name for provisioning is missing.

The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations (providers) but with fewer attributes. Try direct provisioning.

Response code:

SPML Provisioning Child Name Missing

Response Description:

The child name is missing.

You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred.

The connector may not have been created correctly. Try creating another connector by using the same set of configurations (providers) but only one multivalued attribute, which is the one that failed the first time. Try direct provisioning.

Response code:

SPML Provisioning Child Meta-Data Null

Response Description:

The child metadata list is null.

You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred.

Response code:

SPML Provisioning Child Metadata Problem

Response Description:

An error was encountered while sorting the child metadata list.

You may have been trying to perform provisioning for one particular type (for example, role or membership) of multivalued attribute when this error occurred.

The connector may not have been created correctly. There is a problem in the order that has been set for the provisioning fields. Try creating another connector with fewer attributes for the relevant multivalued field. Try direct provisioning. After each successful round of provisioning, try adding fields one by one by performing the Manage Generic Technology Connector procedure. The point at which you start facing this issue again identifies the field that is not in the correct order.

Response code:

SPML Provisioning ID Missing

Response Description:

The unique ID is missing.

You are trying to run an operation on a created user. However, the Create User operation itself may not have run successfully and the unique ID (psoID) that was expected as the response was not received. Therefore, the provisioned instance data was not updated in Oracle Identity Manager. Check why this operation failed.

Response code:

SPML Provisioning Target ID Missing

Response Description:

The unique Target ID is missing.

Check the provider parameters that have been entered. TargetID may be missing.

Response code:

OIM API Error

Response Description:

An error was encountered in the Oracle Identity Manager API layer.

Check if Oracle Identity Manager is operating correctly for other operations. Check the connectivity between the Oracle Identity Manager front end and the database.

Note: This error is not related to the providers that you use.

Response code:

OIM Process Form Not Found

Response Description:

The process form was not found in Oracle Identity Manager.

The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. Try direct provisioning.

Note: This error is not related to the providers that you use.

Response code:

OIM Process Form Instance Not Found

Response Description:

The process form instance was not found for the specified form during update.

The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning.

If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations.

Note: This error is not related to the providers that you use.

Response code:

OIM Atomic Process Instance Not Found

Response Description:

The process instance found is not an atomic process.

The provisioned instance information in the Oracle Identity Manager database may have become corrupted. Try direct provisioning.

If the problem persists, then there may be an issue with the generic technology connector. Create another generic technology connector by using the same set of configurations.

Note: This error is not related to the providers that you use.

Response code:

Column Not Found

Response Description:

An expected column was not found in the result set.

The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. Try direct provisioning.

Note: This error is not related to the providers that you use.

Response code:

Invalid Provider

Response Description:

The provider name specified is invalid.

The Provisioning Format, Transformation, or Provisioning Transport Provider in use may not have been registered correctly. Check if you have correctly followed the steps to register the providers. If this error is displayed when a predefined provider is used, then check the directory on the Oracle Identity Manager server for the XML files of these providers. These XML files are in the following directory:

OIM_HOME/xellerate/GenericConnector/ProviderDefinitions

Response code:

IT Resource Instance Not Found

Response Description:

The IT resource instance was not found in Oracle Identity Manager.

The generic technology connector may not have been created correctly. Try creating another generic technology connector by using the same set of configurations. Try direct provisioning.

Note: This error is not related to the providers that you use.

Response code:

Version Not Found

Response Description:

The required process form version was not found in Oracle Identity Manager.

The generic technology connector may not have been created correctly. Try creating another connector by using the same set of configurations. If you have edited an existing connector by adding a new field to an existing data set, then that operation may have failed. Try making the same change again in the connector.

Note: This error is not related to the providers that you use.

Response code:

Version Not Defined

Response Description:

The required process form version was not defined in Oracle Identity Manager.

Note: This error is not related to the providers that you use.

Response code:

Web Service Not Found

Response Description:

The Web service was not found on the target server. Check the service name and IP address.

Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running.

Response code:

Web Service Connection Refused

Response Description:

The Web service connection could not be established. Check that the server is running and the specified port is correct.

Check if the Web service is running.

Response code:

Web Service No Such Method

Response Description:

The Web service method could not be started. Check the operation name and parameters.

Check the operation name and parameters.

Response code:

Web Service Null Parameter Value

Response Description:

The parameter value passed to the Web service is null.

Check if the provisioning process ran correctly. The Provisioning Format Provider may not have run correctly and, therefore, may have generated NULL output.

Response code:

Web Service HTTP Library Missing

Response Description:

The Web service HTTP library is not included in the classpath.

There is a problem with the Oracle Identity Manager installation. Contact Oracle Support and send them information about this problem and the response code and description displayed. In addition, send the relevant logs generated after running Oracle Identity Manager with logging set to the DEBUG level.

Response code:

Web Service Null Result Value

Response Description:

The Web service result value is null.

Check if the Web service is running correctly. At present, it is generating NULL output as the response to the Oracle Identity Manager provisioning request.

Response code:

Web Service Invocation Issue

Response Description:

An error was encountered while invoking the Web service.

Check the credentials of the Web service.

Response code:

Web Service Target URL Missing

Response Description:

The Web service target URL required to invoke the Web service is missing.

Check the values of the provider parameters. The Web service URL may be missing. Modify the generic technology connector and provide this value again.

Response code:

Web Service Target Method Name Missing

Response Description:

The Web service target method name required to invoke the Web service is missing.

Check the values of the provider parameters. The Web service operation name may be missing. Modify the generic technology connector and provide this value again.

Response code:

Web Service Response XML Parsing Error

Response Description:

An error was encountered during XML parsing of the Web service response.

Check if the Web service is running correctly. It is generating an SPML response that does not conform to the format specified for the Web service provider.

Response code:

Web Service Response ID Error

Response Description:

Either a unique ID is not getting generated from the Web service, or its value could not be parsed because of an incorrect attribute name in the response XML file.

Check if the Web service is running correctly. For the Create User operation, it is generating an SPML response that does not conform to the specified format. In addition, it is not returning the psoID created in the target system. The provider specification for the Web Service provider expects the return of the psoID field.

Response code:

Web Service Protocol Connection Error

Response Description:

An error was encountered in the Oracle-SOAP HTTP connection.

Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.

Response code:

Web Service Protocol Processing Error

Response Description:

An error was encountered while calling the Oracle-SOAP API.

Check the service name and IP address provided in the Web service URL. If these are correct, then check if the Web service is running. Check the operation name and parameters.

Response Code:

Unable to parse the date

Response Description:

Error encountered while parsing the date.

The value specified for the Target Date Format parameter is not correct. For information about the date formats that you can specify, see the following Web page:

http://java.sun.com/docs/books/tutorial/i18n/format/simpleDateFormat.html#datepattern

Response Code:

Data Access Error

Response Description:

A data access error occurred while executing the query or loading the result set.

Check if Oracle Identity Manager is operating correctly for other operations. Check the connectivity between the Oracle Identity Manager front end and the database.

Note: This error is not related to the providers that you use.

Response Code:

SSL Handshake Did Not Happen

Response Description:

An SSL handshake did not happen during the secure communication with the target Web service.

Check if the SEcure Sockets Layer (SSL) configuration between Oracle Identity Manager and the target system has been correctly completed. If required, perform the procedure again.

Response Code:

Error in Initialization of SSL-Related Properties

Response Description:

An error was encountered during the initialization of SSL-related properties. The relevant values are read from the "RMSecurity" element in the OIM_SERVER/xellerate/config/xlconfig.xml file.

Check the configuration entries corresponding to the RMSecurity element of the xlconfig.xml file.

Response Code:

Invalid Web Service Keystore or password

Response Description:

An invalid keystore name or password was encountered in the OIM_HOME/xellerate/config/xlconfig.xml file. Check the configuration entries corresponding to the "RMSecurity" element.

Check the configuration entries corresponding to the RMSecurity element of the xlconfig.xml file.

Response Code:

Error Encountered During Web Service Keystore Initialization

Response Description:

Keystore initialization failed. Credentials of the keystore are mentioned in the OIM_HOME/xellerate/config/xlconfig.xml file under the "RMSecurity" element.

Check the configuration entries corresponding to the RMSecurity element of the xlconfig.xml file.

Response Code:

Invalid ID

Response Description:

An invalid ID is present in the input SPML request.

Check the value specified for the Target ID parameter.

Response Code:

Object already exists

Response Description:

This object already exists in the target system.

Check if the object that you are trying to create already exists on the target system.

Response Code:

Operation Not Supported

Response Description:

The requested provisioning operation is not supported.

Check if the target system supports the requested provisioning operation. For information about the types of SPML provisioning operations that can be performed by using the SPML Provisioning Format Provider, see the "SPML Provisioning Format Provider" section.

Response Code:

Invalid ID Type in Input SPML Request

Response Description:

An invalid ID type is present in the input SPML request.

Check the sample SPML request corresponding to the type of request that was sent, and determine if the target system supports all the ID values that were included in the request.

You can access the sample SPML requests in the following directory:

OIM_HOME/xellerate/GTC/Samples/spml

Response Code:

ID in Input SPML Request Does Not Exist in the Target System

Response Description:

The ID in the input SPML request does not exist in the target system.

Ensure that the psoID value that was sent in the request exists in the target system.

Response Code:

Requested Execution Mode Not Supported

Response Description:

The requested execution mode is not supported.

Ensure that the target system supports the execution of requests in synchronous mode.

Response Code:

Invalid Container

Response Description:

The object cannot be added to the specified container. Refer to the log file for more information. Check the value of the "errorMessage" element in the SPML response.

Check if a container corresponding to the container ID specified in the request exists on the target system.

Response Code:

Nonstandard SPML Error

Response Description:

A target-specific error was encountered. Refer to the log file for more information. Check the value of the "errorMessage" element in the SPML response.

Check the value of the errorMessage element in the SPML response. This element contains the target system error message that was generated when the error was encountered.

Response Code:

SPML Response Is for Asynchronous Mode

Response Description:

The SPML response is for asynchronous mode, which is not supported for this release.

Ensure that the target system sends responses corresponding to the synchronous mode of request execution.

Response Code:

Error Encountered While Parsing Constituent Elements of Web Service URL

Response Description:

An error was encountered while parsing the constituent elements of the Web service URL. Check if the specified URL contains the protocol, host name, port and the endpoint. Oracle recommends copying the URL from the relevant WSDL file while specifying provider parameter values during connector creation.

Check if the specified URL contains the protocol, host name, port, and endpoint. Oracle recommends copying the URL from the relevant WSDL file while specifying provider parameter values during connector creation.

Response Code:

SPML Response failed V2 schema validation

Response Description:

SPML Response received is not compliant with the SPML V2 standard specifications.

Ensure that the SPML response returned by the target system conforms to the SPML V2 standard specification.