|
Hi all, i have got a problem with MobiLink synchronization Version 17.07.3399: Quit often client get an error while there is no issue on the server. Client:
Server: I. 2017-11-15 09:20:26. <25932> Anforderung von "Dbmlsync 17.0.7.3399" für: Entfernte ID: 9c24b7cd-8d18-4714-9524-eed41f96c3e3, Benutzername: xxx, Version: Voll_1 I. 2017-11-15 09:20:26. <25932> Die aktuelle Synchronisation nutzt eine Verbindung mit Verbindungs-ID "SPID 227655" I. 2017-11-15 09:20:26. <25932> COMMIT der Transaktion: Synchronisationsbeginn I. 2017-11-15 09:20:26. <25932> COMMIT der Transaktion: Hochladen I. 2017-11-15 09:20:35. <25932> COMMIT der Transaktion: Download vorbereiten I. 2017-11-15 09:20:41. <25932> Download wird an eine entfernte Datenbank gesendet I. 2017-11-15 09:20:41. <25932> COMMIT der Transaktion: Herunterladen I. 2017-11-15 09:20:41. <25932> COMMIT der Transaktion: Synchronisation beenden I. 2017-11-15 09:25:07. <25932> COMMIT der Transaktion: Downloadbestätigung I. 2017-11-15 09:25:07. <25932> Synchronisation abgeschlossen Anyone an idea? Thanks, Axel |
|
It looks like there was a problem with the download acknowledgement. My best guess given just this information is that there was a loss of network connectivity when the remote database was applying the download. It received and applied the entire download, but when dbmlsync went to send the download acknowledgement to the MobiLink Server, the network was gone. Reg Does the MobiLink client send keep-alive bytes during this period, as described here? ( the Watcom Rule would say yes :)
(15 Nov '17, 09:19)
Breck Carter
|
|
Ok. Is there anything i can do? This insecures our end users of course... |