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 sapjco.jar file or the JCO native support libraries are not present or are improperly located.
Make sure the proper platform version of sapjco.jar is located in the same directory as SAPShim.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.
If you have installed the SAP HR Management (JCO3) driver, you might see the following driver initialization errors in the DSTrace utility:
This error occurs when the SAP Java Connector sapjco3.jar file or the JCO native support libraries are not present or are improperly located.
Make sure the proper platform version of sapjco3.jar is located in the same directory as SAPHRShim.jar. Also check the JCO native support libraries to make sure they are present and properly configured. Use the JCO3 installation instructions for the appropriate platform.
This error occurs when the SAP Java Connector (JCO) native support library is not present or is located improperly. Make sure the JCO native support libraries are present and configured properly. Use the JCO3 installation instructions for the appropriate platform.
This section contains errors that are common to both SAP HR JCO2 and SAPHR JCO3 drivers.
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.
If the Mapping policy Add Dialog contains no data for the APP (application properties of class mappings), the driver can not find the HRMD_A schema metafile.
You should ensure that the metafile directory and Master HR IDoc driver parameters are set to a valid file system location and contain the proper IDoc name. Validate that the metadata file for the configured IDoc type is in the file system location. For example, if Master HR IDoc is set to the default HRMD_A03, ensure that HRMD_A03.meta exists in the metafile directory.
Ensure that the ALE and change pointer processes are configured properly, and that you have properly entered data.
The proper way of inserting or changing data is through using the > or > menus. If an error or a change is entered by overwriting an existing record and saving it, the change document is not created.
Verify that the driver parameters contain the correct client number and proper IDoc directory.
You should first test the ALE and IDoc 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. Validate the path to the directory and make sure the Transfer IDoc Immediately option 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 the change pointers have been configured.
Ensure that the scheduled processes are not scheduled too closely together. For example, if one job is in process and another job begins, the second job might be cancelled because the first job is still running.
First ensure that you have configured all of the driver parameters and that the proper passwords have been entered.
If you are using the Publisher Channel Only configuration of the driver, make sure you have entered the correct parameters. If you have previously used a Publish and Subscribe driver, make sure that all files have been replaced by the Publish-only files.
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 Section 5.3, Using the SAP Java Connector Test Utility.
You might see the following error in DS Trace 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
Identity Manager Log Event -------------------
Driver = \FLIBBLE_TREE\n\Driver Set\SAP-HR
Channel = publisher
Status = fatal
Message = <description>SAP Document Poller initialization failed: com.novell.nds.dirxml.driver.SAPShim.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.
The driver is designed to use a connection to SAP even when it is configured as a Publisher-only driver. The first purpose for using this connection is to verify the version of the SAP server so that the driver can configure itself for the proper version of IDocs it will consume. Otherwise the driver must be configured with a value for the Master HR IDoc parameter.
This connection also verifies the validity time stamps of desired infotypes during processing of future-dated event IDocs. This is an extremely critical function that should always be enabled if future-dated processing options are chosen in the driver configuration. Disabling this capability could result in the propagation of old or stale events that have been subsequently overridden.
If you don’t want a connection to the SAP server, you should remove at least one of the following connection parameters:
SAP Application Server (see Authentication Context or Connection Information)
SAP User ID (see Authentication ID or User ID).
SAP User Password (see Application Password or Set Password).
In this situation, the IDoc data being processed is used as a completely authoritative source of reliable data.
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.