SAP Business One Integration Problems and Solutions - DI server DI API B1WS
4 likes28,691 views
The document discusses various integration problems and solutions for SAP Business One, including issues related to server connections, incorrect configurations, and internal errors. It provides detailed causes for common errors such as wrong passwords, mismatched versions, and connection refusals, along with recommended troubleshooting steps. Users are advised to check network settings, authentication configurations, and service statuses to resolve integration issues effectively.
SAP Business One Integration Problems and Solutions - DI server DI API B1WS
- 1. SAP Business One INTEGRATION PROBLEMS & SOLUTIONS DI SERVER, DI API, B1WS
- 2. PROBLEMS UNABLE TO CONNECT TO SBO-COMMON UNKNOWN HOST WRONG BLI PASSWORD / 8.81 : INTERNAL ERROR (500) 1000000013 – WRONG B1I LICENSE OR 100000048 – NO SAP LICENSES 103 FAILED TO CONNECT 8012 COMPANY VERSION MISMATCH CONNECTION REFUSED TO HOST: XXX-XXX-XXX-XXX / AN EXISTING CONNECTION WAS FORCIBLY CLOSED BY THE REMOTE HOST COM.SAP.B1I.ADAPTER.DIA.EXCEPTION.CONNECTIONFAILEDEXCEPTION:COM.SAP.SMB.SBO.API.SBOCOMUTIL ERROR HTTP 404 NOT FOUND/FILE NOT FOUND “THE IPO-STEP TO CREATE A CACHED AUTHENTICATION CONFIG-NODE FOR IS NOT KNOWN” HTTP 403 FORBIDDEN – XCL198 HTTP ACCESS CURRENTLY NOT ALLOWED FROM REMOTE CLIENTS, AS B1IP RUNS IN LOCAL-MODE OR SAFE-MODE HTTP 500 – INTERNAL ERROR ACTION CANCELLED INSTALL SAP BUSINESS ONE INTEGRATION SERVICE BEFORE ENABLING THE DASHBOARD WIDGET THE REQUEST DASHBOARD DOES NOT EXIST. 2032 CONNECTION TYPE: XML DATA (CANNOT ACCESS EXTERNAL DATA) NO COMPANY DATABASE APPEARS IN THE SLD WHAT IS THE USERNAME AND PASSWORD FOR EXPLICIT AUTHENTICATION 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
- 3. UNABLE TO CONNECT TO SBO-COMMON CAUSE SOLUTION This is a network issue which happens when the SERVER Name that has been used for connection is not configured in the local network, or the configured machine is turned off. To solve this issue, it is recommended to use the IP address of the server. Even though the logical name can be used, but it is recommended to use the same string that has been used in the EventSender setup. Before doing setup, it is also recommended to check the network configuration. 1
- 4. UNKNOWN HOST CAUSE SOLUTION Incorrect proxy configuration setup for your server. You need to setup the IP Address of the proxy server where DI Proxy is running. 2
- 5. WRONG BLI PASSWORD / 8.81 : INTERNAL ERROR (500) CAUSE SOLUTION This error is caused when incorrect password is used and the re- quest is unauthorized. The B1i password must be setup and changed in SAP Business one. In case of any further isse, reset the B1i Password and test again. 3
- 6. 8012 COMPANY VERSION MISMATCH 4 CAUSE SOLUTION There is a mismatch between the DI, SBO-Common and Company database versions. To solve this problem follow the steps below: 1. Start è Programs è Run, Type %temp%. 2. A temporary folder will open, delete / rename SM_OBS_DLL folder here. 3. Select SAPBobsCOM.dll è Go to properties. Ensure the Version is 8.8 PL 12 or higher. 4. SBO –Common : Query to the database table SINF using the following SQL Statement “select Version from SINF”, ensure the version is 880230 and patch level is 12 or higher. 5. If there is any decrepancies in this, run SBO-Common upbrader from PL12 or higher again. 6. In the company db, query using the following SQL Statement. “select Version from CINF” and ensure the version is 880230 or higher.
- 7. 103 FAILED TO CONNECT 5 CAUSE SOLUTION Incorrect company selected or company is not upgraded. Ensure the company field is ok and correct database is used. Also ensure the database has been upgraded to the correct patch. The database that is installed when you install B1iC is called B1if. This is not a normal SAP Business One database so should update the SLD to actual SAP B1 database name.
- 8. 1000000013 – WRONG B1I LICENSE OR 100000048 – NO SAP LICENSES CAUSE SOLUTION Licence not exists or not been assigned to the B1i user. 6 Ensure the licences B1iINDIRECT_MSS and B1i have been as- signed to B1i user.
- 9. CAUSE SOLUTION This happens when there is a problem with diProxyHost or diProxyPort. In the diProxyHost, replace the computer name with the ma- chine’s IP address and add this IP to PROXYHOME entry in the diProxyServer.properties file which resides in Drive:Program FilesSAPSAP Business One IntegrationDIProxy on the same server where SAP is installed. On the contrary, if the DIProxy is located on different machine, Ensure port 2099 is exempted in the Firewalls and also DI Proxy service is started. 7 CONNECTION REFUSED TO HOST: XXX-XXX-XXX-XXX / AN EXISTING CONNECTION WAS FORCIBLY CLOSED BY THE REMOTE HOST
- 10. CAUSE SOLUTION The JCO path is not correctly set in the diproxyServer.Properties. Locate the Java Connection for SAP Business One DI API (default path is C:Program FilesSAPSAP Business One DI APIJCOLIB). Enter this patch with double back-slashes in the JCO patch of the diproxyserver.properties file (default patch is C:Program FilesSAPSAP Business One IntegrationDIProxy). 8 COM.SAP.B1I.ADAPTER.DIA.EXCEPTION.CONNECTIONFAILEDEXCEPTION: COM.SAP.SMB.SBO.API.SBOCOMUTIL
- 11. 9 CAUSE SOLUTION Localhost is used when configuring B1i Server Address. Change the localhost in the B1i Server address with the IP Ad- dress assigned to that machine or even the Server name used for Local network connectivity. To do that: Open the Integration Framework Maintenance è Cfg Runtime, and change the corresponding setting. HTTP 403 FORBIDDEN – XCL198 HTTP ACCESS CURRENTLY NOT ALLOWED FROM REMOTE CLIENTS, AS B1IP RUNS IN LOCAL-MODE OR SAFE-MODE
- 12. ERROR HTTP 404 NOT FOUND/FILE NOT FOUND 10 CAUSE 1 SOLUTION The user manager is used instead of B1i user. Ensure the user B1i is used during setup and connection in the SLD and the B1i user has been correctly set up in SAP Business One.r manager is used instead of B1i user. CAUSE 2 SOLUTION There is an SQL server instance name. If you are using an SQL named instance make sure each instance uses a different TCP/IP port and, during the installation of the integration component, enter the server name as <server name> rather than <server name>instance name. Note: PL08 and higher will provide regular sup- port for named instances CAUSE 3 SOLUTION The IPO user was deactivated. Go to B1iP Control Center è Configuration è User Admin IPO-Steps – Toggle Activation for user B1iadmin and B1ipeer. Restart the Integra- tion server and Event Sender service and retry. CAUSE 4 SOLUTION The Proxy host was configured in the Event Sender set up. On Step 3/5 of the Event Sender set up ensure you do not configure Proxy Host or the Proxy Port.
- 13. ERROR HTTP 404 NOT FOUND/FILE NOT FOUND 11 CAUSE 5 SOLUTION SQL Server/Tomcat Services have not been started. Ensure SQL Server//Tomcat Services are started: Click Start è Control Panel è Administrative Tools è Services Locate the service name SQL Server (MSSQLS- ERVER) / Tomcat and ensure they are started CAUSE 6 SOLUTION Https Port 8443 is being used by another program. Open https://localhost:8443 using the browser and ensure it is the home page of Apache Tomcat. If not, the 8443 port is occupied by an- other program. Disable the other program that is using port 8443 or assign another port to the other program. CAUSE 7 SOLUTION The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error. Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings. Check the Message Log in the Integration Framework -> Monitoring for errors (Failure) connected to “Sender Trigger / Object” “500” (event to create SLD entry) or “120000008” (event to deploy dashboards) Check the Queue Monitor in the Integration Framework è Monitoring for pending processes – after in- stallation / upgrade some post-installation processing time may be required (depending on various fac- tors up to 2 minutes per B1 DB on slow systems) Go to the B1iP Control Center è Maintenance è IPO-Step Status and check “Deactivated steps only to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing. Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated.
- 14. CAUSE SOLUTION The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error. Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings. Check the Message Log in the Integration Framework -> Monitoring for errors (Failure) connected to “Sender Trigger / Object” “500” (event to create SLD entry) or “120000008” (event to deploy dashboards) Check the Queue Monitor in the Integration Framework -> Monitoring for pending processes – after installation / upgrade some post-installation processing time may be required (depending on various factors up to 2 minutes per B1 DB on slow systems) Go to the B1iP Control Center è Maintenance è IPO-Step Status and check “Deactivated steps only to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing. Activate the deactivated steps – and press “Refresh” to see whether the steps can successfully be reactivated. 12 HTTP 500 – INTERNAL ERROR
- 15. 13 “THE IPO-STEP TO CREATE A CACHED AUTHENTICATION CONFIG-NODE FOR IS NOT KNOWN” CAUSE 1 SOLUTION Installation did not install the systems in the System Landscape directory. Run the EventSender setup. Or detach the data- base from SQL Server Management Studio. Re- fresh company list and attach the database once again in SQL. Click refresh in the Choose Com- pany window in SAP Business One. CAUSE 2 SOLUTION Scenario has not been activated Open the Integration framework è Scenarios è Scenario Package Control. For the sap.Xcelsius click Activate. CAUSE 3 SOLUTION Changes made without restarting. If changes are made ensure Integration Service and Event Sender are restarted. CAUSE 4 SOLUTION Internal functions / IPO steps may have been “deactivated”. Go to the B1iP Control Center -> Maintenance -> IPO-Step Status and check “Deactvated steps only” to check whether any processes are halted. If so, the relevant error may be displayed – giving a hint for details that require fixing. Activate the deactivated steps – and press “Refresh” to see whether the steps can success- fully be reactivated.
- 16. ACTION CANCELLED 14 CAUSE 1 SOLUTION SAP Business One integration service may be stopped. Ensure the SAP Business One integration service is running. Stop and start the service and retry. CAUSE 2 SOLUTION Port 8080 is being used by another program Open http://localhost:8080 via the browser and ensure it is the home page of Apache Tomcat. If not, the 8080 port is occupied by another program. Disable the other program that is using port 8080 or assign another port to the other program. Note: From B1iC 8.81 PL05 to change the port you should follow the instruc- tions in the AdministrationGuide_Integration_Component section 2.7
- 17. 15 CAUSE SOLUTION You will receive the prompt “The server xxxx at B1iP- _ipo_/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.run- time/INB_HT_CALL_SYNC_XPT.ipo/proc requires a username and password”. If this occurs in SAP Business One you should restart the SAP Business One client. WHAT IS THE USERNAME AND PASSWORD FOR EXPLICIT AUTHENTICATION
- 18. 16 THE REQUEST DASHBOARD DOES NOT EXIST. CAUSE 1 SOLUTION Cockpit not activated correctly 1. Deactivate the cockpit in your Business One database – Disable My Cockpit and also disable cockpit in General Settings 2. Run EventSender Setup (in first step try to avoid using localhost or IP addresses), in third step press Test Connection, in fourth step make sure that your database is checked, press also Receiver button and then Test Connection. Finish EventSender setup. 3. Click on SLD in the B1i Framework and ensure connection to the Company database (B1DI and JDBC) is successful. 4. Go back to B1i Framework UI, click Scenarios in upper menu, then select Control in left menu and (re)activate Xcelsius scenario. 5. Restart EventSender service, Integration Service and Proxy services via Services (Computer Manage- ment) 6. Now you can enable cockpit in your Business One database – enable cockpit in General Settings and then enable My Cockpit. CAUSE 2 SOLUTION After installation of B1ic, the company is not listed in the SLD Delete all entries of table SLSP and SLSPP in SBOCOMMON. Restart integration service. In SAP Business refresh the company list. Dashboard: /com.sap.b1.dashboards/0010000100.sap_dashboard_001.dab001/default.html If this dashboard is newly imported, ensure that the SAP Business One EventSender Server has been started; then wait for several minutes and try again.
- 19. CAUSE SOLUTION Previous Tomcat/B1ic installation exists. Remove the Integration component and any Tomcat deployment before you upgrade/reinstall again. 17 INSTALL SAP BUSINESS ONE INTEGRATION SERVICE BEFORE ENABLING THE DASHBOARD WIDGET
- 20. CAUSE SOLUTION Company database does not exists or not created through installation process. De-activate and re-activate the sap.B1System scenario (B1i Framework UI, click Scenarios in upper menu, then select Control in left menu). 18 NO COMPANY DATABASE APPEARS IN THE SLD
- 21. 19 CAUSE SOLUTION Problem is when the current access user cannot access the file for storage. It could be because of Cross Domain policy setup which restricts the current user to access the file. Start “Server Manager”è Under the “security information section, click on the Configure IE ESC” link and Turn off for Administrators. 2032 CONNECTION TYPE: XML DATA (CANNOT ACCESS EXTERNAL DATA)
- 22. www. .com We Connect.You Grow. World’s easiest solution for connecting your E-Commerce Stores,Marketplaces and CRM with ERP!