The way the iPayment server component and the add-on connection works here is that the server at regular intervals writes the current time of the server component to the U_SERVLASTRUN field in [@BOY_E0_CONFIG]. At the startup of the B1 Client / iPayment Add-on, the system reads this timestamp and compare it to the user's local workstation time. If these two times are more than 1 hour apart the message is shown.
This check is in place so that consultants wouldn't forget to install and configure the server component, or to give a warning that the server component is not running for some reason.
We recently realized that if the server and the users' machines are if different timezones, then it could make this check go haywire, as they are always an hour apart. We have plans on changing how this scenario works, but currently, there is no workaround. The warning itself is harmless and can be closed.
This also means that the iPayment add-on shouldn't be run in any databases that are not connected to the server component.
If you have already checked that the service is running correctly and U_SERVLASTRUN field in [@BOY_E0_CONFIG] is updated, please check the time difference between the machine you get this pop-up in and the server time as it can also explain the behavior.
If the times are matching and you still get the error, please send us a ticket through our web form with the following information:
- Copy of the user's event log (Location: %appdata%\Boyum IT\BOY_E0_MODIFICATIONS\Eventlogs)
- Copy of the server component event log (Location: C:\Program Files (x86)\Boyum IT\iPayment Server component\Eventlog )
Run this query in the query wizard inside SAP B1 and take a screenshot. Also, keep the company name visible in the screenshot.
SELECT "U_LASTUPDATE" FROM "@BOY_E0_CONFIG"
- Include a screenshot from the database-specific settings in the iPayment setup configuration, here's an example: