SAP Business One Integration Tool – Troubleshooting Guide
GLOBAL CONFIGURATION ERRORS
Creating a connection fails with error: An error has occurred while processing connection ‘CONNECTION_NAME’: Failed to Connect to DIAPI Server: SAP B1 Error Response – OBServerDLL.dll version is older than the DI API version (Error Code: -8003)
Cause 1: This error occurs when there is a version miss-match between the SBOCommon database and the Company database.
Solution 1: To resolve this problem requires reinstall of the DI API.
Creating a connection fails with error: An error has occurred while processing connection : Failed to Connect to DIAPI Server: SAP B1 Response – Unable to initialise OBServerDLL.dll (Error Code: -105)
Cause 1: The error means that the SAP license server details setup within the tool are incorrect.
Solution 1: Check that both the license server host name and port number are valid for your SAP installation.
Creating a connection fails with error: Failed to load company list from server. Exception occurred retrieving the COM class factory for component with CLSID: {632F4591-AA62-4219-8FB6-22BCF5F60090} Failed due to the following error: 8007007e The specified module could not be found.
Cause 1: The error is specific to SAP Business One Integration Tool version 1.311 which supports only the 32-bit API. From version 2.630 on, both the 32-bit and 64 bit DIAPI are supported.
Solution 1: Install the 32-bit SAP DIAPI.
Creating a connection fails with error: Failed to Connect to DIAPI Server: SAP B1 Error Response – Failed to connect or logon to SLD, please check connection parameters and configure file (Error Code: -8037)
Cause 1: The ‘Backend Server Name’ (found under the ‘Database’ tab), has been entered as ‘localhost’.
Solution 1: Use the database server hostname in place of ‘localhost’.
Creating a connection fails with error: Failed to Connect to DIAPI Server: SAP B1 Error Response – Failed to connect or logon to SLD, please check connection parameters and configure file (Error Code: -8037)
Cause 1: The SAP System Landscape Directory (SLD) is not configured correctly or is offline.
Solution 1: Contact your SAP partner to resolve the issue.
STEP CONFIGURATION ERRORS
At step configuration, when you select an operation you get the error: “Unable to get object schema. Error occurred. You are not connected to a company”.
Cause 1: Occurs when the user setup under the ‘Authentication’ tab in the tool global configuration, has no license assigned within SAP B1, or the license has expired.
Solution 1: From SAP Business One Main Menu, choose Administration -> License -> License Administration, and assign a license to the user.
RUN TIME ERRORS
At task runtime, the step fails with the error: Failed to Add SAP B1 Business Object (-5002): To generate this document, first define the numbering series in the Administration module
Cause 1: This error occurs when a numbering series that is not supported for the document type is being mapped to the ‘series’ field.
Solution 1: To resolve the issue, map a supported numbering series. Alternatively, leave the series field unmapped to allow SAP B1 to use the default numbering series for that document type.
At task runtime, the step fails with error: Failed to Add SAP B1 Business Object (- 5002): 10000047 – Date deviates from permissible range
Cause 1: This error occurs on A/R Invoice and A/P Invoice documents, and is caused by the due date on the document in a posting period being locked. (By default, a posting period’s due date is set to cover January 1 – December 31 of a calendar year.)
Solution 1: This can be resolved within SAP Business One from the Main Menu -> Administration -> System Initialization -> Posting Periods and setting the document due date into the next calendar year.
At task runtime, the step fails with error: Error validating source XML against schema – The element ‘ELEMENT_NAME’ has invalid child element ‘ELEMENT_NAME’.
Cause 1: The error is caused by an invalid schema from the input data source, i.e. the Database Query step will be the input data source.
Solution 1: To resolve the error, open the Database Query step and make a minor change, for example, key in a line break or a space character. When you click OK to save the change you will get a prompt to “execute this new query to read the new schematics?” Click yes to accept the prompt.
At task runtime, the step fails with error: Error occurred: Could not load file or assembly ‘SboMetadataSvcModel, Version=1.0.34.0, Culture=neutral,
PublicKeyToken=2a74e7488c2054c1’ or one of its dependencies. The system cannot find the file specified.
Cause 1: The error is caused by missing operation Metadata.
Solution 1: To resolve the issue, open the step and reselect the operation and click OK to save the change. This will refresh the operation Metadata.
At task runtime, the step fails with error: An error occurred whilst processing the operation: You are not connected to a company.
Cause 1: The error occurs when the user setup under the ‘Authentication’ tab in the global connection setting, has no license assigned within SAP Business One, or the license has expired.
Solution 1: From the SAP Business One Main Menu, choose Administration -> License - >License Administration, and assign a license to the user.
At task runtime, the step fails with error: Error code 998. An error occurred whilst processing the operation: Exception from HRESULT: 0xFFFFFB9E.
Cause 1: The error occurs when the SAP DIAPI component is in an inconsistent state. Subsequent transactions against the same SAP business object while the component is in this state will fail.
Solution 1: Disconnect and release the com object, by restarting the SAP Business One Integration Agent service.
SAPB1 Errors
Objective
This technical note explains why certain SAP Business One errors occur.
Description
These are some of the common errors that can occur when you develop an iBOLT integration project that uses the SAP B1 component.
1001 Connect process: Could not connect to the company database
This error is quite rare. It means that none of the known errors occurred, but that the session was still not opened.
1003 Disconnect process: Failed to disconnect the company database
This error is also quite rare. It means that there has been a problem in the disconnection process. 1005 SAP Business One1 Error return <Err No> : <Err Description>
Connectivity to SAP Business One, using a Data Interface Application Programming Interface (DI API), contains two phases:
1. Connectivity to the DI API.
2. SAP Business One approval of the data and execution.
When this error is returned, it means that the first phase was completed successfully. The error is a SAP Business One error, and there are several possible reasons for its occurrence:
∙ (-1) Duplicate key. When using the multi-add option and you get this error, you also get (in the description) the number of the BO in the array that caused the failure. For example, if you try to add 5 BPs and the 3rd one is already in there, you'll get 1005+(B1's -1) with a pointer to the 2nd BO (the index is zero-based).
∙ (-8008) There is a problem with the DB user named OBSCommon. In this case, the user should re-create that user.
∙ (###) The exchange rate is not set. When adding a document into SAP Business One (orders, invoices, etc.), the exchange rate for the document date should be set. Two new Direct Access Methods (DAMs) were added that allow you to automate the exchange rate update: SetExchangeRate and GetExchangeRate.
1006 Internal error return <Err No> : <Err Description>
This error means that the first phase, discussed above, failed.
Here are some ground-rules for understanding the error and what causes it:
∙ Errors 3/13: This means that the DI crashed when calling the method mentioned in the description, and that the session is no longer open. “Session was closed” appears in the suffix of the description.
∙ “Failed calling method GetBusinessObjectFromXML” appears when you use an add action with an XML interface. This means that the XML that was generated or given is in the wrong structure, and/or one of its simple nodes holds a value that is not valid.
1007 Unknown\Unsupported data object: <data object name>
This error usually tells you that the component could not find its internal metadata, called SAP Business One Metadata (until iBOLT V2.5 SP2) or SAP Business One Metadata2 (from iBOLT V2.5 SP2).
1008 The iBOLT SAP Business One adaptor is not licensed
The license that you used to activate iBOLT is not a valid SAP Business One license. 1009 Error retrieving mandatory parameter from XML (parameter<Param Name>)
When you use an XML interface to update or delete an object (this error can occur only with this interface), the user must enter a value to the simple element of the compound QueryParams. If the user does not enter a value in this element, this error is returned.
1010 Could not find resource: <resource name>
This error indicates that there was an error in finding the resource.
1011 Query failure
Query returned an error message.
1012 iBOLT's SAP Business One connector exceeded the number of database connections permitted by your license. Can not access database <Server_DBName>
The SAP Business One License contains the number of database connections that are permitted. This error message is returned when the iBOLT SAP Business One connector exceeds this amount.
1013 The 'ibolt_notification' stored procedure does not exist in the <ServerName_DBName> database When the 'ibolt_notification' stored procedure is not found, an error message is returned.
1014 There is no reference to the 'ibolt_notification' stored procedure in the <ServerName_DBName> database's 'SBO_SP_TransactionNotification' stored procedure
This error indicates that the 'ibolt_notification' stored procedure does not exist in this context.
