SAP Business One Integration Tool – Troubleshooting Guide

In this SAP B1 troubleshooting guide, we shall discuss some common errors, why they are caused, and how to resolve each error. So, let’s get started.

How Do you Troubleshoot in SAP B1?

Common errors in SAP B1 can be grouped under the following three categories:

• Global configuration errors
• Step configuration errors
• Runtime errors

In the next section, let’s discuss the category-wise errors in SAP B1.

SAP B1 Troubleshooting – Global configuration Errors

Configuration errors in SAP B1 occur when configuring this ERP tool for a specific customer. Here are the five most common configuration errors in SAP B1:

1.  Error Description: 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 of Error: This configuration error occurs when there is a mismatch in versions between the “SBOCommon” database and the organization’s database system.

Solution: Reinstall the DI API server.

2.  Error Description: An error has occurred while processing connection: Failed to Connect to DIAPI Server: SAP B1 Response – Unable to initialize OBServerDLL.dll (Error Code: -105)

Cause of Error: This configuration error is reported whenever the SAP license server details in the tool are incorrectly set up and configured.

Solution: Check if your SAP license server’s hostname and port number are valid for your SAP installation.

3.  Error Description: Failed to load company list from the 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 of Error: This configuration error is specific to version 1.0.311.0 of the SAP B1 integration tool, which only supports 32-bit API. From the SAP B1 integration tool version 2.0.630.0 onwards, this error does not occur as it supports both 32-bit and 64-bit DIAPI.

Solution: Install the 32-bit SAP DIAPI.

4.  Error Description: _Failed to Connect to DIAPI Server: SAP B1 Error Response – Failed to connect or log on to SLD, please check connection parameters and configure file (Error Code: -8037)

Cause of Error: This configuration error occurs when the backend server name in the Database tab is entered as “localhost.”

Solution: Replace “localhost” with the hostname of the database server.

5.  Error Description: _Failed to Connect to DIAPI Server: SAP B1 Error Response – Failed to connect or log on to SLD, please check connection parameters and configure file (Error Code: -8037)

Cause of Error: This configuration error occurs when the SAP System Landscape Directory (SLD) is incorrectly configured or is currently offline.

Solution: Get in touch with your SAP business partner immediately.

SAP B1 Troubleshooting – Step Configuration Errors

Step configuration errors in SAP B1 occur when you select a particular operation when configuring steps. Here is the most common error that occurs:

1.  Error Description: Unable to get object schema. Error occurred. You are not connected to a company.

Cause of Error: This step configuration error occurs when the user is not set up (under the Authentication tab of the global configuration tool) and has no assigned license with SAP Business One. Alternatively, the user may have an expired license.

Solution: From the SAP Business One main menu, navigate to Administration > License > License Administration – and assign a valid license to the user.

SAP B1 Troubleshooting – Runtime Errors

Runtime errors in SAP B1 occur when the system cannot continue executing a task and has to terminate it immediately. Here are the six most common runtime errors in SAP B1:

1.  Error Description: _Failed to Add SAP B1 Business Object (-5002): To generate this document, first define the numbering series in the Administration module.

Cause of Error: This runtime error occurs when the numbering series is not supported for the type of document – and is being mapped to the Series field.

Solution: Map a numbering series that is supported. Alternatively, you can leave the Series field unmapped. In this case, SAP Business One will map the default numbering series for that document type.

2.  Error Description: _Failed to Add SAP B1 Business Object (-5002): 10000047 – Date deviates from permissible range.

Cause of Error: This runtime error occurs only for A/P invoice and A/R invoice documents. It is caused because of the locking of the due date on the documents in the posting period.

Solution: From the SAP Business One main menu, navigate to Administration > System Initialization > Posting Periods – and set the document’s due date to the next calendar year.

3.  Error Description: Error validating source XML against schema – The element ‘ELEMENT_NAME’ has invalid child element ‘ELEMENT_NAME.’

Cause of Error: This runtime error is caused by an incorrect schema from the input data source. The Database query step is the input data source.

Solution: Open the Database Query step and add a line break or space character. On clicking OK, SAP B1 prompts you to “execute this new query to read the new schematics?” Click Yes to execute this prompt.

4.  Error Description: 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 of Error: This runtime error occurs due to the missing operation Metadata.

Solution: Reopen the step and select the operation again. Click OK to refresh the metadata.

5.  Error Description: An error occurred whilst processing the operation: You are not connected to a company.

Cause of Error: This runtime error occurs when the user is not set up (under the Authentication tab of the global configuration tool) and has no assigned license with SAP Business One. Alternatively, the user may have an expired license.

Solution: From the SAP Business One main menu, navigate to Administration > License > License Administration – and assign a valid license to the user.

6.  Error Description: Error code 998. An error occurred whilst processing the operation: Exception from HRESULT: 0xFFFFFB9E.

Cause of Error: This runtime error occurs when the SAP DIAPI component is in an inconsistent state. In this state, all subsequent transactions made for the same SAP business object will also fail.

Solution: Restart the SAP B1 integration agent service to disconnect and release the object.

Conclusion

In this guide, we have highlighted how to perform troubleshooting in the SAP Business One integration tool. We have also listed some of the common SAP troubleshooting examples and how to solve these problems.

As an award-winning SAP business partner, Praxis Info Solutions develops customized solutions in SAP Business One for small companies and startups across industry domains. Our team of SAP B1 professionals can help you troubleshoot common issues in a quick time.

Are you looking for an experienced SAP business partner for your organization? Contact us today and book our free product demo.