2024年4月27日发(作者:)

Root cause 2: User selected an old JCO folder during installation and warning was ignored during set-up.

Solution 2: Change the DIProxy properties files to point to correct JCO path and restart the DI Proxy services. To do this open the file (default location is C:Program

FilesSAPSAP Business One ties) and update the field JCOPATH.

Note: 8.8 PL2 and B1iC 8.81 validates the DI version and if incorrect a warning will appear in the setup process and will be included in the install_ file.

Root cause 3: B1i user is not a super user.

Solution 3: Ensure in SAP Business One the B1i user is set as a super user.

Root cause 4: User is locked after 5 consecutive failed attempts.

Solution 4: See Note 1556041 on how to resolve this.

Root cause 6: DI Proxy port conflict.

Solution 6: Change the DI Proxy port in the SLD for the SAP Business One database (different to 2099, 2100 for example). Enter same port number in RMI_PORT property of

ties file (folder Program Files/SAP/SAP Business One Integration/DIProxy). For B1iC 8.8 deactivate us package and activate us

package.

1.3 Error HTTP 403 Forbidden - XCL198 HTTP access currently not allowed from remote clients, as B1iP runs in local-mode or safe-mode

Root cause: You use localhost in the B1i Server address.

Solution: Ensure instead of localhost you use the IP address or the server name to connect. Open the Integration Framework -> Maintenance -> Cfg Runtime and change the

corresponding setting.

1.4 Error HTTP 404 not found/File not found

Root cause 1: The user manager is used instead of the B1i user.

Solution 1: 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.

Root cause 2 B1iC 8.8/B1iC 8.81 before GA: Incorrect JDK installed for a 64bit environment.

Solution 2: In 64bits machines you need to have JDK installed for both 32 and 64bits and point to both during the installation of B1ic.

Root cause 3: There is an SQL server instance name.

Solution 3: 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 rather than instance name.

Note: PL08 and higher will provide regular support for named instances – see note 1621563

Root cause 4: The IPO user was deactivated.

Solution 4: 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.

Root cause 5: The Proxy host was configured in the Event Sender set up.

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

Root cause 7: The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error.

Solution 7a: Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings.

Solution 7b: 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)

Solution 7c: 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)

Solution 7d: 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 te the deactivated steps – and press “Refresh” to see whether the steps can successfully be

reactivated.

Root cause 8: SQL Server/Tomcat Services have not been started.

Solution 8: 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

1.5 Error HTTP 500 – Internal Error

Root cause 1: The dashboard is not deployed correctly in B1ic for the selected company or may have encountered an error.

Solution 1a: Ensure the correct company database appears in the SLD. Deactivate and re-activate the dashboard in SAP Business One’s General Settings.

Solution 1b: 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)

Solution 1c: 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)

Solution 1d: 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 te the deactivated steps – and press “Refresh” to see whether the steps can successfully be

reactivated.