Table of Contents
4. Produmex Service Broker
4.1. Service Broker cannot be started
Check the BXServiceBroker log file for more information. The log file is located: C:\ProgramData\BX\BX Service Broker\Logs
You can also open the log file by clicking on the ‘View log…’ icon on the Produmex Service Manager.
4.1.1. Module load error
ERROR Cannot start: System.Exception: BXMobileWH9WebAPI init fail: Module load error.
Solution
1. Check the version numbers. The version number of the Server Module, the Client and the SAP Add-on should be the same.
- The version number of the Server module can be checked on the ProdumexServiceBroker service configuration screen of the Service Broker
- The version number of the Client can be checked on the LoginScreen
- The version number of the SAP Add-On can be checked on the Add-On Management form
2. Check the DI API installation. For a 32 bit SAP DI an 32 bit Server Broker, for an 64 bit SAP DI an 64 bit Server Broker should be installed.
4.1.2. Connection to company failed
Connection to company failed: -8037 Failed to connect or logon to SLD, please check connection parameters and configure file
1. Remove and add the database again on the Setup Companies window of the Service Manager, then restart the Service Broker.
For more information about adding a database please see: Add new database
2. On HANA: Check the database server configuration on the Database connection screen of the ServiceBroker. It has to be in the exact same format as it was defined during the SAP DI installation. You can check it in the b1-local-machine.xml file. The file is located: C:\Program Files (x86)\SAP\SAP Business One DI API\Conf\
You can modify the connection data on the Setup Companies window of the Produmex Service Manager. For more information please see: Setup/Modify Connection data to the SAP company
4.1.3. Other
Check whether the add-on was started on the database. The add-on may contain changes and a database upgrade might be required.
4.2. Connection could not be established to the Service Broker
Issue
When starting the Produmex Scan application, the following error message is displayed:
No connection could be made because the target machine actively refused it.
When starting the Produmex PDC application, the following error message is displayed:
Connection could not be established to the Service Broker. Either it is not running or the application is not configured. Please run the configuration tool and/or check if the Service Broker has been started.
Solution
This document describes how to identify typical causes for this issue. It is possible it possible that your issue may be resolved by checking the listed steps.
4.2.1. Produmex Service Broker is not running
Check whether Produmex Service Broker is running or not. The connection cannot be established if the Service Broker is not running.
4.2.2. Produmex server component is not installed
Check whether the Produmex server component is installed for the Service Broker. The installed server modules are listed on the Produmex Service Broker tab of the ProdumexServiceBroker service configuration window.
If not, the following error message is displayed:
4.2.3. Check the Service Broker log file
If there are no error messages when starting up the Produmex Service Broker, check the log file of the Service Broker for more information. Please see: 4.1. Service Broker cannot be started
4.2.4. Incorrect IP address or port number
Run Configure Produmex Scan and check whether the correct IP address/server name and port number was added as the Server URL.
4.2.5. Firewall block
Check the firewall settings on the server. Make sure that both TCP and UDP connections are allowed to the port number of the Service Broker for the following services:
- BxServiceBroker.Service.exe
- BxServiceBroker.Console.exe
4.2.6. No valid certificate
When using https, make sure that you have a valid certificate that is bound to the port. For more information about configuring https and creating a self-signed certificate for Produmex Service Broker please see: Configure HTTPS for Produmex Service Broker
4.2.7. Network issues
In order to identify network issues, simulate the calls Produmex application makes. The testing protocol suggested below goes in increasing order of complexity, and identifying the specific step where tests fail can be a very valuable piece of information in order to find out the root cause of the connectivity issue.
4.2.7.1. Test access on the server
First simulate the calls on the server hosting Produmex Service Broker.
Produmex Service Broker Admin Page
Enter the following to the browser in order to access the Produmex Service Broker Admin Page: http://localhost:<PORT>/
Where the PORT is the port number.
Then try to connect to the Produmex Service Broker Admin Page with the following: http://<IP>:<PORT>/
Where the IP is the IP address of the hosting server and PORT is the port number. If the hosting server has multiple IP addresses, it is recommended to try the connection with all IP addresses.
Database access
To simulate the database query, add the following to the browser:
- Produmex Scan:
http://localhost:<PORT>/api/bxmobilelmsdatabases/ - Produmex PDC & Produmex Operator:
http://localhost:<PORT>/api/broker_databases/
Where the PORT is the port number.
Then replace localhost with the IP address and check whether the connection can be established or not. Enter the following to the browser:
- Produmex Scan:
http://<IP>:<PORT>/api/bxmobilelmsdatabases/ - Produmex PDC & Produmex Operator:
http://<IP>:<PORT>/api/broker_databases/
Where the IP is the IP address and the PORT is the port number. If the hosting server has multiple IP addresses, it is recommended to try the connection with all IP addresses.
If the connection cannot be established, it could mean that the Produmex Service Broker does not run or the server module is not installed.
If the connection can be established with localhost but not with the IP address of the server, it can mean:
- The IP address is not correct.
- The IP address is not accessible.
4.2.7.2. Test access on another computer
If you were able to connect to the Produmex Service Broker Admin Page and the databases with both the localhost and the IP address of the server on the server, test the connection from another computer that is on the same network as the device(s) where the Produmex application runs.
Produmex Service Broker Admin Page
To test the connection to the admin page, enter the following to a browser: http://<IP>:<PORT>/
Where the IP is the IP address of the server where the Produmex Service Broker runs and PORT is the port number. If the hosting server has multiple IP addresses, it is recommended to try the connection with all IP addresses.
Database access
To simulate the database query, add the following:
- Produmex Scan:
http://<IP>:<PORT>/api/bxmobilelmsdatabases/ - Produmex PDC & Produmex Operator:
http://<IP>:<PORT>/api/broker_databases/
Where the IP is the IP address and the PORT is the port number. If the hosting server has multiple IP addresses, it is recommended to try the connection with all IP addresses.
If the connection can be established on the server, but not on a different computer, then the issue is most likely that your network configuration, for example a firewall, is blocking the connection. We recommend that you contact your network administrator.
4.2.7.3. Test access on the device
If you were able to connect to the Admin Page on the server and on another computer, try to connect from the device.
Produmex Service Broker Admin Page
To test the connection to the admin page, follow the steps described here: 7.2.1. Produmex Service Broker Admin Page
Database access
To simulate the database query, follow the steps described here: 7.2.2. Database access
If the connection can be established on the server and on a different computer, but not on the device, check the network settings on the device.
4.2.7.4. Simulate other calls
To learn more about the required network configuration, you can simulate the other calls as well on the server, a different computer or on the device.
Calls, subsequent to the database query, require header authorization. These calls can be simulated with a help of a REST client.
Follow these steps to set the Authorization header data:
- Enter or select ‘Authorization’ as the Header name.
- Specify the following value:
<deviceID>@<companyName>\<user>:<password>
For example:- With login information:
0@TEST_SCAN\1:1234 - Without login information:
0@TEST_SCAN\:
- Encode the value into base64 with any Base64 encoder.
For example:- With login information:
MEBURVNUX1NDQU5cMToxMjM0 - Without login information:
MEBURVNUX1NDQU5cOg==
- Set the Header value to
Basic <base64text>
For example:- With login information:
Basic MEBURVNUX1NDQU5cMToxMjM0 - Without login information:
Basic MEBURVNUX1NDQU5cOg==
Produmex Service Broker logs the successful calls to the access log, which is located in C:\ProgramData\BX\BX Service Broker\Logs\. You can select any calls from the access log to simulate.
Example calls for Produmex Scan
Calls when the application starts
To check the startup configurations add http://<IP>:<PORT>/api/bxmobilelmscommon/ as the ‘Request URL’.
To check further configurations, add http://<IP>:<PORT>/api/bxmobilelmscommon/?dummy=1 as the ‘Request URL’.
To check Produmex Scan customizations, add http://<IP>:<PORT>/api/bxmobilelmscustomization/?sinceDate=0001-01-01&expandFileData=True as the ‘Request URL’.
Calls when the employee ID is added
To load the employee details, add http://<IP>:<PORT>/api/bxmobilelmsemployee/?pinCode=1 as the ‘Request URL’. Replace the pinCode value with the Pin Code or the employee ID of the employee you would like to check.
To get the printers set for a given employee, add http://<IP>:<PORT>/api/bxmobilelmsprinting/?employeeID=1 as the ‘Request URL’. Replace the employeeID with the employee ID of the given employee.
Call when the Login button is pressed
To test the login date, add http://<IP>:<PORT>/api/bxmobilelmsemployee/?employeeID=1&password=1234 as the ‘Request URL’. Replace the emplyoeeID with the employee ID of the given employee and the password with the password.
Call when the Logout button is pressed
To simulate the logout, add http://<IP>:<PORT>/api/bxmobilelmscommon/?dummyUser=dummy as the ‘Request URL’.
Example calls for Produmex PDC
Calls when the application starts
To check the startup configurations add http://<IP>:<PORT>/api/bxppsmobilepdccommon/ as the ‘Request URL’.
To check further configurations, add http://<IP>:<PORT>/api/bxppsmobilepdccommon/?dummy=1 as the ‘Request URL’.
To see the extended terminal configurations, add http://<IP>:<PORT>/api/bxppsmobilepdccommon/?employeeID=0&terminalID=1 as the ‘Request URL’.
To see the customizations, add http://<IP>:<PORT>/api/bxppsmobilepdccustomization/?sinceDate=0001-01-01&expandFileData=True as the ‘Request URL’.
Example calls for Produmex Operator
Calls when the application starts
To get admin info, add http://<IP>:<PORT>/api/bxmwcommon as the ‘Request URL’.
To check the configurations, add http://<IP>:<PORT>/api/bxmwcommon/?configuration=configuration as the ‘Request URL’.
To see the customizations, add http://<IP>:<PORT>/api/bxmwcustomization?sinceDate=0001-01-01&expandFileData=True as the ‘Request URL’.