You might see the following driver errors in the DSTrace utility. An explanation of the error is given along with recommended solutions.
This is a fatal error that occurs when sapusershim.jar is not installed properly. Ensure that the file is in the proper location for either a local or Remote Loader configuration.
This error also occurs when the class name for the sapusershim.jar is incorrect. You should ensure that the Java class name is set on the Driver Module tab in a local installation and that the -class parameter is set in a Remote Loader configuration. See Section A.1.1, Driver Module.
The class name is com.novell.nds.dirxml.driver.sapusershim.SAPDriverShim.
This error occurs when the SAP Java Connector sapjco2.jar file or sapjco3.jar or the JCO native support libraries are not present or are improperly located.
Make sure the proper platform version of sapjco2.jar or sapjco3.jar is located in the same directory as sapusershim.jar.
Also check the JCO native support libraries to make sure they are present and properly configured. Use the JCO installation instructions for the appropriate platform.
This error occurs when the SAP Java Connector (JCO) native RFC12 support library is not present or is located improperly. Make sure the JCO native support libraries are present and configured properly. Use the JCO installation instructions for the appropriate platform.
This error occurs when the SAP Java Connector (JCO) native RFC support library librfccm.so is not present or is improperly located. This sample error is from a Solaris* system.
Make sure the JCO native support libraries are present and properly configured. Follow the JCO installation instructions for the appropriate platform.
This error occurs when the SAP Java Connector (JCO) components cannot be located.This error generally occurs if the driver or Remote Loader has not been restarted after the JCO has been configured. Restart Novell eDirectory if you are using a local configuration or restart the remote loader for a remote configuration.
This error occurs when the SAP authentication or connection information is not configured properly. Ensure that the values for Authentication and Driver Parameters are correct for authentication to the SAP host system.
This error occurs when the Publisher IDoc Directory parameter in the Publisher Settings of the Driver Parameters does not specify a valid file system location. Ensure that this parameter specifies the directory on the SAP system configured in the SAP ALE subsystem for IDoc file output.
This error occurs when the Remote Loader connection parameter information is incorrect. Configure the proper connection information for the remote connection to the system where the Remote Loader is running.
This error occurs when the Remote Loader password configured on the remote system does not match the Remote Loader password on the Driver object.
Set matching passwords for both remote loaders. In iManager, ensure that both the application password and Remote Loader passwords are set at the same time.
This error occurs when the driver password configured on the remote system does not match the Driver object password on the Driver object. To correct this, you should set both Driver object passwords identically.
You should ensure that the ALE and CUA processes are configured properly, and that you have correctly entered the data.
User data is distributed to the driver only if CUA has been properly configured and if the logical system representing the driver has been selected for distribution under the Systems tab in the SAP User Maintenance dialog box.
When creating users in the CUA central system, you must associate User objects with the client systems to which they authenticate. This occurs in the default policies when you set a value for the driver’s logical system in the DirXML-sapLocRoles or DirXML-sapLocProfiles attribute.
You should first test the ALE and CUA interface. Refer to your SAP documentation for more information.
If the IDoc interface fails:
Using transaction WE21, ensure that the file port is configured properly. You should validate the path to the directory and make sure the Transfer IDoc Immediately radio button is selected.
Using transaction WE20, ensure that the appropriate file port is selected in the Partner Profile. Also, verify that it is on the outbound parameters of the receiving system.
If the IDoc interface succeeds:
Ensure that the correct distribution model has been selected using transaction SCUA.
Ensure that the proper User field data distribution is configured using transaction SCUM.
You should first test the ALE and CUA interface. Refer to your SAP documentation for more information.
If the IDoc distribution succeeds but data is not received:
Verify that the driver is configured to receive data from the correct SAP Gateway.
Verify that the driver Program ID is unique.
Using transaction WE21, verify that the SAP port configuration is configured to distribute to the logical system representing the driver.
If the IDoc interface succeeds:
Ensure that the correct distribution model has been selected using transaction SCUA.
Ensure that the proper User field data distribution is configured using transaction SCUM.
You should first ensure that you have configured all of the driver parameters and that the proper passwords have been entered. If the SAP system is the central system of a CUA configuration, make sure the User object used for authentication is properly associated with the client logical system. See Section 10.2.12, Users Created in SAP Cannot Log On to the SAP System (CUA in Use).
If you are running the driver remotely, make sure that the Remote Loader has been started before you start the driver.
For detailed instructions on using the JCO Test utility and analyzing error messages, refer to Testing the SAP JCO Client Connection.
You might see the following error in DSTrace if the IDoc directory parameter specifies an invalid local file system container or if it specifies a mapped drive on a remote system.
*** NDS Trace Utility - BEGIN Logging *** Fri Sep 13 15:45:59 2005
DirXML Log Event -------------------
Driver = \FLIBBLE_TREE\n\Driver Set\SAP-UM
Channel = publisher
Status = fatal
Message = <description>SAP Document Poller initialization failed: com.novell.nds.dirxml.driver.sapusershim.SAPDocumentPollerInitFailure: Specified Publisher IDoc Directory is invalid.</description>
*** NDS Trace Utility - END Logging *** Fri Sep 13 15:46:31 2005
This error occurs because the Windows operating system service controls the rights of the local system, not the rights of a user. Thus, the local Windows system does not have rights to access any file resources outside of its own system, including the IDoc directory.