Sync failed/Aborted Error

[halaeliya]

Hello,

We are in the process of updating our FileMakerGo on the iPads from 13 to 16 but we are running into an issue with the sync. We are currently running MirrorSync 2.3 but will eventually upgrade to 3. Meanwhile, we need to get FMGO 15 or 16 work with our current MirrorSync.

The sync error doens't always show, sometimes it syncs and sometimes it doesn't.

Any ideas? 

Thanks

[Mark Stuller]

Probably a "Connection disruption". Fairly standard. We get this ~25% of the time. Most clients are in an area with just 'ok' connectivity. Good enough for voice, data not so much. We have found a VPN connection helps by keeping the connection 'alive'.

hth

[halaeliya]

Not data connection issue.

We don't get the error with FM GO 13 and the connection fast, we are on high speed wifi. 

[Mark Stuller]

Speed is not the issue. Ping time is a rough, but fairly effective metric of 'reachability' https://en.wikipedia.org/wiki/Ping_(networking_utility)

[halaeliya]

Why don't we get the same error with FM GO 13 and 14 ?

just 15 and 16 and on the same internet connection.

[Mark Stuller]

A good question - that I hope Jesse can weigh in on.

[Tsiry360Works]

This issue seems to be solve with the current version of MirrorSync 3.17. The client retries the sync in case it received empty response from the server. 

Thanks.

[Mark Stuller]

fwiw, we are on 3.17 and still get these errors routinely. Users 'merely' re-try and often a single re-try completes. It may be explained by the mix of versions.

[Jesse Barnum]

Mark, the fix we made in 3.17 is in the FileMaker script itself. This means that just updating the server is not enough to apply the fix; it will only apply after re-pasting the script steps with 3.17 and then having users download that version.

Are you still having problems even after the clients get an offline version with the 3.17 script?

[Mark Stuller]

  On 6/29/2017 at 4:15 PM, Jesse Barnum said:

Mark, the fix we made in 3.17 is in the FileMaker script itself. This means that just updating the server is not enough to apply the fix; it will only apply after re-pasting the script steps with 3.17 and then having users download that version.

Are you still having problems even after the clients get an offline version with the 3.17 script?

Expand  

Yes, our user's scripts are at 3.17. Server: 360Works MirrorSync 3.17, build 9239 (3/24/17) Clients: Generated "3.17"  By MirrorSync Version 2017-04-25 11:12:12

And we do still get disconnects. Fewer tho.

[Jesse Barnum]

OK thanks for letting me know. I thought that 3.17 would totally fix it, I guess not.