You can troubleshoot the driver using the DSTrace utility. You will want to configure the utility's options by selecting Edit > Properties > DirXML Drivers.
For each event or operation received, the driver returns an XML document containing a status report. If the operation or event is not successful, the status report also contains a reason, a text message describing the error condition. If the result is fatal, the driver shuts down.
After you have configured the DSTrace Utility, you can monitor your system for errors.
If the driver does not load, check DSTrace for the following error messages:
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 is a fatal error that 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.
The proper class name is com.novell.nds.dirxml.driver.sapusershim.SAPDriverShim
You might see the following driver initialization errors in the DSTrace utility. An explanation of the error is given along with recommended solutions.
This error occurs when the SAP Java Connector jco.jar file or sapjco.jar or the JCO native support libraries are not present or are improperly located.
Make sure the proper platform version of jco.jar or sapjco.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® eDirectoryTM 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 ConsoleOne® or iManager, ensure that both the application password and Remote Loader passwords are set at the same time.
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 manually associate User objects with the client systems to which they authenticate. You do this by editing the User object from the SAP User Maintenance dialog box, then adding an appropriate client logical system under the Systems tab. This problem should not occur when creating users in non-central CUA systems.
You should first test the ALE and CUA interface. Refer to your SAP documentation for more information.
If the IDoc interface fails:
If the IDoc interface succeeds:
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:
If the IDoc interface succeeds:
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 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 Using the SAP Java Connector Test Utility.
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 2002
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 2002
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.