Wednesday, 8 July 2015

SAP Businessone Doc. Number 1618978 - Troubleshooting integration framework installation and upgrade

This document will help you to solve out issue while doing integration with SAP Business One Back-end to Dashboard or Mobility. ( In my case I used with dashboard - SUCCESSFUL)
Note: This Document is copyrighted by SAP Business One 


Symptom
You installed or upgraded the integration framework following the instructions in the SAP Business One administrator' s guide. the SAP Business One integration for SAP NetWeaver administrator's guide, or the installation or upgrade guide of the integration framework for SMEs. However you cannot  install or upgrade the solution and you require troubleshooting information.


Solution
This document contains frequently asked questions and troubleshooting information for the installation and upgrade of the integration framework.
The troubleshooting information for SAP Business One Cloud environment has moved to SAP note 2086174.
During Installation
1.1 Initialization fails to finish with the error message: Initialization has failed and terminates in 600 seconds; for more information, in the integration framework, chooseTools → Troubleshooting → and, in the Function Group field, select B1 Setup.
1.1.1 The SAP Business One Integration Service is not available in Microsoft Windows Services. Choose Start → Run, enter services.msc and press Ok.
Root Cause A: This is a system-specific environmental issue.
Solution A: To install the SAP Business One Integration Service, do the following:
  1. Run the Command Prompt as Administrator, and change to the ...\Tomcat\bin directory and run service install.
    The default location of the Tomcat\bin directory is: ..\SAP\SAP Business One Integration\B1iServer\Tomcat\bin.
  2. To manually register the service, choose Start → Run, enter services.msc and press Ok. Select the service, click the Start link, and change the Startup property from Manual toAutomatic.
1.1.2 SAP Business One Integration Service has the disabled status. Choose Start → Run, enter services.msc and press Ok.
Root Cause A: During a previous uninstallation of the integration framework, the Tomcat service has been marked for deletion but has not yet been deleted from the Microsoft Windows Services.
Solution A: To install the SAP Business One Integration Service, do the following:
  1. Reboot the machine.
  2. To install the service, do the following:
    1. Run the Command Prompt as Administrator, and change to the ...\Tomcat\bin directory and run service install.
      The default location of the Tomcat\bin directory is: ..\SAP\SAP Business One Integration\B1iServer\Tomcat\bin.
    2. To manually register the service, choose Start → Run, enter services.msc and press Ok. Select the service, click the Start link, and change the Startup property fromManual to Automatic.
Top 
1.1.3 SAP Business One Integration Service was created, but you cannot start it. Choose Start → Run, enter services.msc and press Ok.
Root Cause A: The SAP Business One Integration is not registered with the default Java Virtual Machine (JVM). To verify the root cause, choose SAP Business One Integration Framework Service and Properties, in the General tab, check the Path to executable value. The default path is C:\Program Files (x86)\SAP\SAP Business One Integration\IntegrationServer\Tomcat\bin\tomcat6.exe.  
Solution A: To register the SAP Business One Integration Service, do the following:
  1. Run the Command Prompt as Administrator and run sc delete <INCORRECT SERVICE NAME>.
  2. In the Control Panel → System → Advanced system settings → chose the Advanced tab, click the Environment Variables... button, and check whether the JAVA_HOME or CATALINA_HOME variable exists, for example, CATALINA_HOME1 or JAVA_HOME1.
  3. Run the Command Prompt as Administrator, change to the ...\Tomcat\bin directory and run service install.
    The default location of the Tomcat\bin directory is: ..\SAP\SAP Business One Integration\B1iServer\Tomcat\bin.
  4. Check that in Microsoft Windows Services the following entry is available: SAP Business One Integration Service. Select the service, click the Start link, and change the Startupproperty from Manual to Automatic.
Root Cause B: The SAP Business One Integration Service cannot start. In the Tomcat log (..\SAP\SAP Business One Integration\IntegrationServer\Tomcat\logs), you find the The application has failed to start because its side-by-side configuration is incorrect error. The JVM cannot run on the server. One of the reasons for this error is that the Visual C++ redistributable is not installed or corrupted.
To confirm the root cause: Change to the ..\Program Files\SAP\SAP Business One Integration\sapjre_7_64\jre\bin (64-bit) directory or to the ..\Program Files (x86)\SAP\SAP Business One Integration\sapjre_7_32\jre\bin (32-bit) directory and run java.exe.
Solution B: 
  1. Install or reinstall the relevant Visual C++ package (vcredist). Note that a computer restart might be necessary.
  2. If you still cannot run java.exe after reinstalling the Visual C++ package and the system displays the error below, repair the integration framework installation.
Root Cause C: The SAP Business One Integration Service has been created and has been started, but a configuration issue occurs.
Solution C: This is usually only a timeout message for the initialization and there is no other side effect. Check the menu mentioned in the warning message (Integration Framework UI -> Tools -> Troubleshooting -> Choose Functional Group as 'B1 Setup' -> Submit).
1.1.4 The SAP Business One Integration Service was created with a different name. Choose Start → Run, enter services.msc and press Ok.
Root Cause A: The integration framework installation is corrupt.
Solution A: Reinstall the integration framework.
1.1.5 The SAP Business One Event Sender Service cannot be started from Services panel.
Root Cause A: Environment specific issue.
Workaround A: Start Event Sender service from Start → All Programs → Integration for SAP Business One → SAP Business One EventSender → Run. Event sender service runs successfully if "Enter exit to exit EventSender:" command shows up. Keep the command prompt open to run Event Sender service. Type "exit" to stop the service. 
1.2 Initialization fails to finish with the error message: Initialization failed; open the jobsErr.txt file in the ..\SAP\SAP Business One Integration\IntegrationServer\Tomcat\webapps\B1iXcellerator\Setup\ folder, or in the integration framework, choose Monitoring → Process Control → Framework Processes → APICaller → Call Details.
Root Cause: Various.
Solution: Check the detailed error information in the jobsErr.txt file in the warning message.
1.3 The test connection fails in the 'Database Connection Parameters' installation step (step 3) with message: “Database connection failed: The TCP/IP connection to the host XXX, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port".
Root Cause A: The SQL server instance does not use the default 1433 TCP/IP port.
Solution A: The port set in the integration framework installation must match the TCP/IP port of the SQL server instance.
To check the port configured in the SQL Server instance, do the following:
  1. Choose Start → All Programs → Microsoft SQL Server 20XX → Configuration Tools → SQL Server Configuration Manager.
  2. Goto SQL Configuration Manager → SQL Server Network Configuration → Protocols for <INSTANCE NAME>.
  3. Right-click TCP/IP and select Properties.
  4. In the TCP/IP Properties dialog box, select the IP Addresses tab page.
Root Cause B: You run the SQL server on a named instance.
Solution B: If you use an SQL server named instance, in the Database Connection Parameters, enter SERVER\INSTANCE in the Database Server field. The port must match the TCP/IP port configured in the SQL Server named instance. See the steps above in the Root Cause A section to check the configured port). For more information, see SAP 1621563.
Root Cause C: You run the SQL Server with a dynamic port.
Solution C: The port field must be empty or must contain the following value: 0000. See the steps above in the Root Cause A section to check the configured port.
  1.4 You try to reinstall the integration framework and you receive one of the following error messages:
  • The version of SAP Business One Integration you want to install is identical with the current one. Installation is canceled. Please follow the user guide if you want to run on maintenance mode
  • The SAP Business One Integration version you want to install is lower than the one on your machine 
Root Cause: An integration framework with the same version already exists. Previously, some registry entries were not completely removed.
Solution: Check the .com.zerog.registry.xml file in ..\Program Files (x86)\Zero G Registry (64bit) or ..\Program Files\Zero G Registry (32bit) folder. These are hidden folders. If the file contains only data for the integration framework data, delete the file. If the file contains data for other programs and for the integration framework, only remove the integration framework-related components. 
 1.5 Installing the integration framework, you get the following warning message: The 8080, 8443 ports are not available; stop the process using the port(s), or manually change the integration framework ports after installation.
Root Cause: The ports 8080 or 8443 are occupied by other programs.
Solution: Stop the program or programs that are using the ports and run the installation program again. To change the integration framework port after installation, do the following:
  1. If the SAP Business One Event Sender Service is already running, stop the service.
  2. Change settings in the Server.xml Tomcat file in the following folder ..\Program Files (x86)\SAP\Integration Solution for SAP Business One\IntegrationServer\Tomcat\conf.
    You can find the settings in the connector port tags. Do not change any other settings in the file.
  3. Log on to the integration framework and choose Maintenance → Cfg Runtime, and change the port or ports.
    The integration framework additionally updates the setting in the SLSPP table of SAP Business One.
  4. Restart the SAP Business One Integration Service.
  5. To change the ports in the event sender, choose Start → All Programs → Integration Solution for SAP Business One → EventSender → Setup. Follow the steps of the wizard, and in the Configure B1i Parameters section, change the B1i Server Port entry and test the connection.
  6. Restart the SAP Business One EventSender Service.
  7. To change the properties for the menu entry, using the correct port number, choose Start → All Programs → Integration Solution for SAP Business One → Integration Framework.
 1.6 During installation, you receive one of the following error messages:
  • B1iP 2007 was previously installed
  • Setup detected Embedded B1i on your computer! Setup will exit
  • File jvm.dll not found! java Home temp =” 
Root Cause A: The version was not removed or the CATALINA_HOME variable was not removed.
Solution A: To remove a previous version, do the following:
  1. Open the Control Panel → Programs and Features and verify that old versions were removed. Check the properties of the SAP Business One Integration Service. This leads you to the path of the service executable ..\SAP\SAP Business One Server\IntegrationServer\.... Delete the folder with all content.
  2. In the Control Panel → System → Advanced system settings → chose the Advanced tab, click the Environment Variables... button, and check whether the CATALINA_HOMEvariable exists. If it exists, rename it, for example, to CATALINA_HOME1.
Root Cause B: The version was not removed, there are still registry entries available.
Solution B: To clean up the registry entries, use any standard third party registry cleaner tool.
1.7 <Integration Framework DB Name> is unavailable. For example, IFSERV is unavailable
Root Cause: During upgrade, the installation program detects that the integration framework database was deleted.
Solution: To solve the issue, it is necessary to uninstall the integration framework. Then, install the integration framework.
1.8 Tomcat already exists (Only relevant for SAP Business One 9.0 and 9.1)
Root Cause: Tomcat service registry entries are not removed from previous uninstallation.
Solution: Choose Start → Run... → Regedit and check whether the below keys exist. If they exist, delete the key folder.
  • For 32-bit server: HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat6
  • For 64-bit server: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\Tomcat6
For an SAP Business One integration 9.0 for SAP NetWeaver or Integration Framework for SMEs 1.0 installation:
  1. Check whether a process name containing the tomcat string exists.
  2. If the string exists, stop the process and install again.
Top 
 2 Upgrade/Repair  
 2.1 When upgrading the integration framework, you receive the following error message: The upgrade from SAP Business One Integration version lower than 8.8 is not possible.
Root Cause: Upgrade the Integration Framework from a version lower than 8.8.
Solution: Remove the old integration framework version and install the new version.
 2.2 Technology Component SAP Business One integration Server/EventSender/DIProxy Version file is missing on current computer, Upgrade or Repair can not be continued. (SAP Business One 8.82 installation relevant)
Root Cause: The product version file is corrupted. 
Solution: 
  1. Uninstall and reinstall the integration framework.
  2. If an upgrade is mandatory, create an SAP Business One support incident in SAP Service Marketplace.

After Installation
3.1 After installation, you logon to the integration framework, but you cannot open the menus or the integration framework does not display menus.
Root Cause A: The Microsoft Internet Explorer security and privacy settings prevent the user interface from responding.
Solution A: In the Microsoft Internet Explorer, add 127.0.0.1 to the trusted sites or reduce the security and privacy settings.
Root Cause B: The IP address is blocked by the firewall.
Solution B: in the firewall settings, create an exception for the IP address.
Root Cause C: The default integration framework ports 8080 or 8443 are used by other programs.
Solution C: Either stop the program or programs using the ports or change the port number for integration framework.
To change the ports manually do the following:
  1. Stop the SAP Business One Integration Service.
  2. Change the port settings in the Server.xml in the following folder: ..\SAP\SAP Business One Integration\IntegrationServer\Tomcat\conf. The settings are available in the connector port tags. Do not change any other settings in the file.
  3. Start the SAP Business One Integration Service.
  4. Log on to the integration framework and choose Maintenance → Cfg Runtime, change the port settings and save.
  5. Restart SAP Business One Integration Service.
 3.2 The SAP Business One Integration Service status us disabled. If you run the sc delete tomcat6 command, you get a notification that the service is marked for deletion.
Root Cause: A previous service is marked for deletion but was not deleted.
Solution: Do the following:
  1. To delete the previous service, reboot the machine.
  2. To register the SAP Business One Integration Service again, run the Command Prompt as Administrator, and change to the ...\Tomcat\bin directory and run service install.
    The default location of the Tomcat\bin directory is: ..\SAP\SAP Business One Integration\B1iServer\Tomcat\bin.
 3.3 You cannot start the SAP Business One Integration Service.
Root Cause: The TCP/IP 8080 and 8443 ports are used by another program.
Solution: Stop the programs using the ports and restart the SAP Business One Integration Service. Alternatively, change the ports manually:
  1. If the SAP Business One Event Sender Service is already running, stop the service.
  2. Change settings in the Server.xml Tomcat file in the following folder ..\Program Files (x86)\SAP\Integration Solution for SAP Business One\IntegrationServer\Tomcat\conf.
    You can find the settings in the connector port tags. Do not change any other settings in the file.
  3. Log on to the integration framework and choose Maintenance → Cfg Runtime, and change the port or ports.
    The integration framework additionally updates the setting in the SLSPP table of SAP Business One.
  4. Restart the SAP Business One Integration Service.
  5. To change the ports in the event sender, choose Start → All Programs → Integration Solution for SAP Business One → EventSender → Setup. Follow the steps of the wizard, and in the Configure B1i Parameters section, change the B1i Server Port entry and test the connection.
  6. Restart the SAP Business One EventSender Service.
  7. To change the properties for the menu entry, using the correct port number, choose Start → All Programs → Integration Solution for SAP Business One → Integration Framework.
 3.4 After installation of SAP Business One 9.1 PL00 and the integration framework, when clicking the Test Connection for the SLD entry of the SAP Business One company database, you get the error message:"Connection to <DATABASE>(B1DI) failed"
Root Cause: The integration framework (B1i) installation of SAP Business One 9.1 PL00 prevents an upgrade of the integration framework.
Solution: See SAP note 2049269.



Other terms
B1iC, B1iSN



Header Data
Released On
06.07.2015 17:33:35
Release Status
Released for Customer
Component
SBO-INT-B1IF SAP Business One integration framework
Other Components
SBO-INT-CKP Cockpit
SBO-INT-DAB Dashboards
SBO-INT-MOB Mobile Applications
Priority
Recommendations/additional info
Category
Consulting


Validity
Software Component
Version
B1 CCC/SLD
All versions
B1 INTEGRATION TECHNOLOGY
All versions
B1 INTERCOMPANY INTEGRATION
All versions
INTEGRATION FRAMEWORK FOR SME
All versions
SAP B1 VERSION FOR SAP HANA
All versions
SAP BUSINESS ONE
All versions


References
This document is referenced by:
SAP Business One Notes (3)
1844555

1765361

1917778