Resolving Errors

This section contains potential problems and error codes you might encounter while configuring or using the driver.

The Driver Will Not Start

• Check that the nps8shim.dll is accessible.
• Check that the connection parameters are set correctly.

Attributes Do Not Get Refreshed on the Data Map Object

• Verify that the Component Interfaces are working correctly.

Data Does Not Show Up in eDirectory on the Publisher Channel

• Verify that the mapping rule and filters are configured correctly.
• Verify that the APIs are working correctly and data is being produced by them.

Error: Check Application Server IP Address and Jolt Port Number

• You should verify that PeopleSoft can connect succesfully to the JVM. Run jnitest.exe from PeopleSoft's External API directory: {pshome}\bin\client\winx86_api\.

  Before configuring the driver, you should install the PeopleSoft External Application Interface software (PSEXTAPI). The PSEXTAPI requires a Java Virtual Machine because the calls to the application server are done through Jolt. The JVM should be installed on the Operating System where the driver shim (nps8shim.dll) runs.
  
  If you don't have the JVM, you can download it from the Microsoft Download Center (msjavx86.exe); or you can use the JVM supplied with Sun's JDK 1.2.2. For additional information, please refer to your PeopleSoft documentation.

Data Does Not Update in PeopleSoft on the Subscriber Channel

• Verify that the mapping rule and filters are configured correctly.
• Verify that the APIs are working correctly.

No Transactions Are Coming across the Publisher Channel

• Verify that there are active transactions in the queue ready for processing.
• Ensure that driver parameters are pointing to the correct PeopleSoft database. For example, transactions will not process if they are in the PROD database, but the driver is still pointing to the test database (which is configured to run with the driver, but holds no transactions).

Transactions Are Not Placed in the PeopleSoft Queue

• Verify that PeopleCode is working properly.

No Data Is Returned When Running the Component Interface Test Program

No data is returned, particularly when you are running the Component Interface Test Program.

There are two typical reasons for this error:

• The Key Input elements are not pointing to the Search Record
• The field elements point to an invalid reference

Make sure the Key Input elements are associated with the Search Record entry. Also, make sure that the field elements are mapped to an appropriate field record definition that exists in the Component buffer. You should also ensure that the data elements exist on a page within the component and that the links are configured correctly.

Transactions Are Left in "Process" State and Not Processed

• Verify that all of the CI objects can be processed and that the status can be updated to a Success (S), Working (W), or Error (E) state.

  If e-mail is configured in PeopleSoft and the SMTP gateway is down, an error can occur, causing the update of the transaction to fail. You should verify that all online processing of the application works correctly. PeopleCode attached to the update might sometimes fail, causing the transaction to fail. If system connectivity is lost, the database or application server goes down during processing and causes the driver to abandon the transaction. The transaction is left in the state of selected with a status of 1.

  NOTE:  If notification processing is required, Novell recommends using the DirXML Notification Service instead of using SMTP processing as configured in PeopleSoft.

Receiving Errors on the Publisher Channel When Processing a Transaction

The following list gives a sampling of errors and what they represent:

• Operation vetoed by Create rule

  Possible required data missing in Create rule or other criteria in Create rule have an error.

• generateKeyPair: -216 DSERR_PASSWORD_TOO_SHORT

  The attribute used for the initial password does not comply to policy; however, the user object will still be created.

• Unable to read current state of 8101

  No association exists for this identity.

• nameToID: -601 ERR_NO_SUCH_ENTRY

  Possible Placement rule error with an invalid container object designated.

• No DN generated by Placement rule

  Possible missing or invalid data causing no valid DN to be created.

Component Interface Relationships Not Functioning

If data does not show up in the attributes, or isn't getting posted into PeopleSoft, or data is missing, you should begin looking at the component interface relationships.

First, verify that the API is getting the data from the PeopleSoft buffer.

After all of the CIs have been tested completely with validation of all processes that the driver is configured to do, there should be no issues regarding the driver accessing PeopleSoft through the CIs. Other problem areas include:

• Connectivity IP address and port for the application server
• ID and password
• Correct naming of all activities in the parameters for the driver.

For troubleshooting these problems, try three basic tests:

1. Test all of the processes manually online using the PeopleSoft applications as configured.
2. Test all of the processes using the Component Interfaces.
3. Test the driver connection to the API through the Component Interfaces.