Nothing works or Can't Connect.
If the configuration checks out with green check marks but you get NO sync action, try clicking the "reset" button in the lower left of GoZync mobile: it may be just that you don't have changes since your last sync.
If that doesn't help, or you can't connect, it is likely your file references (External Data Sources): more on checking those here
You'll also want to make sure that the mobile users are authenticated into your hosted solution with a privilege set that lets them edit records. If all that sounds like stuff you've never heard of, this likely isn't your problem. This only comes up when folks have more elaborate security set ups.
Some fields not syncing.
The most common cause of unexpected sync behavior is that you're not syncing the layout you think you are. Remember, GoZync syncs the fields on your sync layout so visit the configuration tab in GoZyncHosted and make sure the layouts you've specified there are the ones you want to use.
Another cause could be that the field's name begins with a numeral or period, has the same name as a FileMaker function, or contains the word "or", "and" or "not", or a symbol that's being interpreted as an operator.
Related records not syncing.
It could also be that your related table uses a relationship not
based on the primary key of the parent's record table. Related tables to be synced must
be related to the primary key of their parent record. More complex relationships should be synced as their own tables.
Finally, you may have specified the wrong field or table when filling out the "required" column on the configuration tab of GoZyncHosted, so double check that.
One of my tables has a generic sync error
Check to make sure you have values in the UUID field this table is pulling from.
File is Locked or In Use when pulling down a new version
FileMaker Go13 takes a bit longer to close files than Go12 did so you may need to increase the time GoZync waits for your file to close before replacing it. Instructions for changing this are here
. If the 1 second delay mentioned there doesn't work, add 4 seconds and see if that gets it. Then back down to 3 or 2 seconds to find the time that works for your file.
What do error codes in the GoZync logs really mean?
Any errors encountered in the sync will be reported in the zync logs tabs in GoZyncMobile and GoZyncHosted.
Many of the errors will be self explanatory, but the guide below may help.
• 101 Record is missing.
This is about the table occurrence, not the field.
Most likely reason for this is that you don't have "Allow creation of records..." set to "on" for this table in its relationship with GoZync in the graph of GoZyncMobile.
Turn "Allow creation..." on for the table occurrence mentioned in the error and then try again.
• 102 Field Missing.
There are only a few reasons why you'd see a 102 error.
You've sent a field that doesn't exist in the destination. Remove the field from the sync layout on the source side (the sending side) to the receiving side. Note that fields don't have to be on the sync layout in order to be received; fields only need to be there to be sent.
The field exists but has a different name in the destination. See Custom Field Mapping
to transform the field name.
You've created a transformation (a custom field mapping) but your field is repeating and you haven't created a field mapping for each repetition.
• 106 Table is Missing
There is a mismatch between the table occurrence names on the mobile and hosted side of the relationship graph in GoZyncMobile. Even if your actual tables are named something different in the mobile and hosted files, the *occurrences* for those tables in GoZyncMobile's relationship graph need to have the same name (outside of the "gzm_" or "gzh_" prefixes).
You may connected the TO to GoZync on the destination side of the GoZyncMobile graph.
One other thing, that can be hard to spot at first, is that the relationship graph in GoZyncMobile *look* good, but the table occurrences--while named correctly--are either representing the wrong tables or are both pointing at the same file (ie gzm_Contacts and gzh_Contacts are both pointing to the contacts table in your hosted file, for example).
• 301 Record is in use by another user.
Commonly called "record lock".
This is exactly what it sounds like: it's not a configuration error.
FileMaker couldn't edit the record (or one of the related records for that entity) because another user was editing it. Feel free to try and sync the record later when the original user has stopped editing it.
• 500-511 Validation Errors.
These will occur when the data coming in fails to meet the validation criteria set up one one of your fields.
The log will tell you which field created the error and what kind of validation was offended.
You can turn off the validation or change it from "always" to "only during data entry" which will stop it from firing during scripted set fields like those used in GoZync.
You could include a flag-field condition in the validation calculation, then set that flag at the start of the Zync routine, and clear it when it's done.
You could modify the "Commit Records/Requests" step in the "Zengine ( IDsToSync )" script to "Skip data entry validation".
Or you could remove the field validation altogether and instead write a script to do it, then run that script on the server.
License Violation Detected
Pretty rare, but if you're seeing this message it can be caused by one of four things:
You're syncing more than your license allows.
You're trying to call some of the GoZync sub scripts without including our license file (unlikely, unless you're trying to bypass the license).
Or one of your layouts is unable to be read by FileMaker (this is a FMP bug short of corruption). For this one, sync each layout individually from GoZyncMobile and if you find one that gives the license error, delete that sync layout in GoZyncMobile and recreate it.
Authentication Errors in Server Logs
This isn't actually an error: FileMaker Server is just a little too verbose in its logging, and while many people have asked FileMaker to change this, it's been around for a while. What's happening is that the user has other files in the set up that open with "Admin" as the account name. When one of those files calls a script in GoZyncLicense, FileMaker tries to open GoZyncLicense using the same credentials--tries to pass that authentication into the related files. This is a great feature of FileMaker, but in our case, GoZyncLicense doesn't have an Admin account. So, the attempt fails--and FileMaker Server logs the "error" even though the user never sees it. FileMaker then tries the "On Opening" account setup in GoZyncLicense hosted and the solution opens right up. You'll see the same error in FileMaker Server any time two files in solution don't share the logged in account or password. It's not an error and we all wish it wouldn't show up in the log.