Sap business one integration problems and solutions di server di api b1ws by APPSeCONNECT

SAP Business One INTEGRATION PROBLEMS & SOLUTIONS DI SERVER, DI API, B1WS

PROBLEMS 1 2 3 4 5 6 7

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

8 9

COM.SAP.B1I.ADAPTER.DIA.EXCEPTION.CONNECTIONFAILEDEXCEPTION:COM.SAP.SMB.SBO.API.SBOCOMUTIL HTTP 403 FORBIDDEN – XCL198 HTTP ACCESS CURRENTLY NOT ALLOWED FROM REMOTE CLIENTS, AS B1IP RUNS IN LOCAL-MODE OR SAFE-MODE

ERROR HTTP 404 NOT FOUND/FILE NOT FOUND

ACTION CANCELLED

HTTP 500 – INTERNAL ERROR

WHAT IS THE USERNAME AND PASSWORD FOR EXPLICIT AUTHENTICATION

14 15

“THE IPO-STEP TO CREATE A CACHED AUTHENTICATION CONFIG-NODE FOR IS NOT KNOWN”

INSTALL SAP BUSINESS ONE INTEGRATION SERVICE BEFORE ENABLING THE DASHBOARD WIDGET

NO COMPANY DATABASE APPEARS IN THE SLD

2032 CONNECTION TYPE: XML DATA (CANNOT ACCESS EXTERNAL DATA)

THE REQUEST DASHBOARD DOES NOT EXIST.

UNABLE TO CONNECT TO SBO-COMMON CAUSE 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.

SOLUTION 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.

UNKNOWN HOST CAUSE Incorrect proxy configuration setup for your server.

SOLUTION You need to setup the IP Address of the proxy server where DI Proxy is running.

WRONG BLI PASSWORD / 8.81 : INTERNAL ERROR (500)

CAUSE This error is caused when incorrect password is used and the request is unauthorized.

SOLUTION 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.

8012 COMPANY VERSION MISMATCH CAUSE There is a mismatch between the DI, SBO-Common and Company database versions.

SOLUTION 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.

103 FAILED TO CONNECT CAUSE Incorrect company selected or company is not upgraded.

SOLUTION 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.

1000000013 – WRONG B1I LICENSE OR 100000048 – NO SAP LICENSES

CAUSE Licence not exists or not been assigned to the B1i user.

SOLUTION Ensure the licences B1iINDIRECT_MSS and B1i have been assigned to B1i user.

CONNECTION REFUSED TO HOST: XXX-XXX-XXX-XXX / AN EXISTING CONNECTION WAS FORCIBLY CLOSED BY THE REMOTE HOST

CAUSE This happens when there is a problem with diProxyHost or diProxyPort.

SOLUTION In the diProxyHost, replace the computer name with the machineâ&#x20AC;&#x2122;s IP address and add this IP to PROXYHOME entry in the diProxyServer.properties file which resides in Drive:\Program Files\SAP\SAP Business One Integration\DIProxy 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.

COM.SAP.B1I.ADAPTER.DIA.EXCEPTION.CONNECTIONFAILEDEXCEPTION:

COM.SAP.SMB.SBO.API.SBOCOMUTIL

CAUSE The JCO path is not correctly set in the diproxyServer.Properties.

SOLUTION Locate the Java Connection for SAP Business One DI API (default path is C:\Program Files\SAP\SAP Business One DI API\JCO\LIB). Enter this patch with double back-slashes in the JCO patch of the diproxyserver.properties file (default patch is C:\Program Files\SAP\SAP Business One Integration\DIProxy).

HTTP 403 FORBIDDEN – XCL198 HTTP ACCESS CURRENTLY NOT ALLOWED FROM REMOTE CLIENTS, AS B1IP RUNS IN LOCAL-MODE OR SAFE-MODE

CAUSE Localhost is used when configuring B1i Server Address.

SOLUTION Change the localhost in the B1i Server address with the IP Address 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.

ERROR HTTP 404 NOT FOUND/FILE NOT FOUND CAUSE 1 The user manager is used instead of B1i user. SOLUTION 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 There is an SQL server instance name. SOLUTION 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 support for named instances

CAUSE 3 The IPO user was deactivated.

CAUSE 4 The Proxy host was configured in the Event Sender set up.

SOLUTION Go to B1iP Control Center è Configuration è User Admin IPO-Steps – Toggle Activation for user B1iadmin and B1ipeer. Restart the Integration server and Event Sender service and retry.

SOLUTION On Step 3/5 of the Event Sender set up ensure you do not configure Proxy Host or the Proxy Port.

ERROR HTTP 404 NOT FOUND/FILE NOT FOUND CAUSE 5 SQL Server/Tomcat Services have not been started.

CAUSE 6 Https Port 8443 is being used by another program.

SOLUTION Ensure SQL Server//Tomcat Services are started: Click Start è Control Panel è Administrative Tools è Services Locate the service name SQL Server (MSSQLSERVER) / Tomcat and ensure they are started

SOLUTION 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 another program. Disable the other program that is using port 8443 or assign another port to the other program.

CAUSE 7 The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error. SOLUTION 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.

HTTP 500 – INTERNAL ERROR CAUSE The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error. SOLUTION 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.

“THE IPO-STEP TO CREATE A CACHED AUTHENTICATION CONFIG-NODE FOR IS NOT KNOWN” CAUSE 1 Installation did not install the systems in the System Landscape directory. SOLUTION Run the EventSender setup. Or detach the database from SQL Server Management Studio. Refresh company list and attach the database once again in SQL. Click refresh in the Choose Company window in SAP Business One.

CAUSE 2 Scenario has not been activated SOLUTION Open the Integration framework è Scenarios è Scenario Package Control. For the sap.Xcelsius click Activate.

CAUSE 3 Changes made without restarting.

CAUSE 4 Internal functions / IPO steps may have been “deactivated”.

SOLUTION If changes are made ensure Integration Service and Event Sender are restarted.

SOLUTION 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 successfully be reactivated.

ACTION CANCELLED CAUSE 1 SAP Business One integration service may be stopped. SOLUTION Ensure the SAP Business One integration service is running. Stop and start the service and retry.

CAUSE 2 Port 8080 is being used by another program SOLUTION 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 instructions in the AdministrationGuide_Integration_Component section 2.7

WHAT IS THE USERNAME AND PASSWORD FOR EXPLICIT AUTHENTICATION

CAUSE You will receive the prompt “The server xxxx at B1iP_ipo_/vP.001sap0004.in_HCSX/com.sap.b1i.vplatform.runtime/INB_HT_CALL_SYNC_XPT.ipo/proc requires a username and password”.

SOLUTION If this occurs in SAP Business One you should restart the SAP Business One client.

THE REQUEST DASHBOARD DOES NOT EXIST. 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. CAUSE 1 Cockpit not activated correctly SOLUTION 1. Deactivate the cockpit in your Business One database â&#x20AC;&#x201C; 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 Management) 6. Now you can enable cockpit in your Business One database â&#x20AC;&#x201C; enable cockpit in General Settings and then enable My Cockpit. CAUSE 2 After installation of B1ic, the company is not listed in the SLD SOLUTION Delete all entries of table SLSP and SLSPP in SBOCOMMON. Restart integration service. In SAP Business refresh the company list.

INSTALL SAP BUSINESS ONE INTEGRATION SERVICE BEFORE ENABLING THE DASHBOARD WIDGET

CAUSE Previous Tomcat/B1ic installation exists.

SOLUTION Remove the Integration component and any Tomcat deployment before you upgrade/reinstall again.

NO COMPANY DATABASE APPEARS IN THE SLD CAUSE Company database does not exists or not created through installation process.

SOLUTION De-activate and re-activate the sap.B1System scenario (B1i Framework UI, click Scenarios in upper menu, then select Control in left menu).

2032 CONNECTION TYPE: XML DATA (CANNOT ACCESS EXTERNAL DATA)

CAUSE 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.

SOLUTION Start “Server Manager”è Under the “security information section, click on the Configure IE ESC” link and Turn off for Administrators.

www.

.com

Worldâ&#x20AC;&#x2122;s easiest solution for connecting your E-Commerce Stores,Marketplaces and CRM with ERP!

We Connect.You Grow.