I am running an ultralite database version 16 build 2043 on a Windows mobile (version 6.5) handheld. It is replicating to a mobilink server of the same version/build. I'm using .NET 3.5 compact framework.
I have 2 problem scenarios since Windows mobile does not persist the data connection automatically:
1 - the cellular is disconnect: I have to set the network_name parameter in the stream parameters for replication. This forces the cellular connection to dial but immediately fails replication.
2 - the cellular is connected: If the network_name parameter is defined in the stream parameters in this instance, replication fails.
If replication is attempted after the cellular connection is made, replication is successful.
My question is why? Is there a parameter I'm missing in the first scenario that tells the engine to wait until the connection is made? Why would replication fail in the second scenario?
Thank you in advance for any information, feedback or suggestions!
asked 11 May '15, 08:43
There had been an issue in some MobiLink synchronization environments where the dial-up network would not establish a connection within a reasonable time and the client would timeout the connection attempt. If you are running a version prior to 18.104.22.1683, you should update the client to at least that version. The server was impacted by this issue and should not need to be updated.
If you are running a newer version that has this change, you may need to work with technical support to isolate this issue.
answered 11 May '15, 09:50