GoZync4

Error Codes

GoZync4.ErrorCodes History

Hide minor edits - Show changes to output

July 17, 2013, at 01:23 AM by 67.190.87.90 -
Changed line 49 from:
--> Or you could disable all of the field validations and instead write a script to do it instead, then run that script on the server.
to:
--> Or you could remove the field validation altogether and instead write a script to do it, then run that script on the server.
July 17, 2013, at 01:22 AM by 67.190.87.90 -
Changed lines 43-49 from:
--> 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.
to:
--> 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 disable all of the field validations and instead write a script to do it instead, then run that script on the server
.
June 26, 2013, at 07:05 PM by 108.38.141.66 -
June 26, 2013, at 06:52 PM by 108.38.141.66 -
Deleted lines 22-29:
-> '''error = 102 ; message = "We couldn't set this field \"Options:\"" ; $ScriptName = "Set Fields" ;'''

--> When you see "Options:" this is a variant on a simple 102 error and indicates a problem on your sync layout.

--> GoZync can only sync related table occurrences linked to the primary key of the table the sync layout is based on. Tables linked to other fields or linked to related tables instead of the table the layout is based on will cause problems if fields from these tables are on the sync layout.

--> So check to make sure all the related fields on your sync layout are from relationships that are a) just one hop away, and b) liked the primary key of the table you're syncing.

Changed lines 25-30 from:
--> There is a mismatch between the table occurrence names found in the package being processed and the TO names connected to GoZync in your destination file (in GoZyncHosted or GoZyncMobile).

--> You may have related fields in your package but don't have their TO connected to GoZync in your destination file.

--> Or you simply don't have the right name either for
the TO on the graph itself, OR in the integration setup in GoZyncHosted: you may have selected the wrong table occurrence or changed the TO name since the integration was done.
to:
--> 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). 
Changed lines 33-36 from:
--> This is exactly what it sounds like.

--> FileMaker couldn
't edit the record (or one of the related records for that inbox entry) because another user was editing it. Feel free to reprocess the record later when the original user has stopped editing it.
to:
--> 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.
Changed lines 41-42 from:
--> Hover over the error and our tool tip will tell you the field which created the error and what kind of validation was offended.
to:
--> The log will tell you which field created the error and what kind of validation was offended.
June 26, 2013, at 06:41 PM by 108.38.141.66 -
Changed lines 5-6 from:
 > > screenshot
to:
%center% http://www.seedcode.com/rootimages/stikipad/gozync/errorlog.png
June 26, 2013, at 06:31 PM by 108.38.141.66 -
Changed lines 11-12 from:
--> 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 either GoZyncHosted or GoZyncMobile (whichever file where you're seeing the error).
to:
--> 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.
Changed lines 17-18 from:
--> 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) or add it to the receiving side.
to:
--> 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.
June 26, 2013, at 06:08 PM by 108.38.141.66 -
Added lines 1-51:
!! 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.

 > > screenshot

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 either GoZyncHosted or GoZyncMobile (whichever file where you're seeing the error).

--> 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) or add it to the receiving side.

--> 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.

-> '''error = 102 ; message = "We couldn't set this field \"Options:\"" ; $ScriptName = "Set Fields" ;'''

--> When you see "Options:" this is a variant on a simple 102 error and indicates a problem on your sync layout.

--> GoZync can only sync related table occurrences linked to the primary key of the table the sync layout is based on. Tables linked to other fields or linked to related tables instead of the table the layout is based on will cause problems if fields from these tables are on the sync layout.

--> So check to make sure all the related fields on your sync layout are from relationships that are a) just one hop away, and b) liked the primary key of the table you're syncing.

-> '''106 Table is Missing'''

--> There is a mismatch between the table occurrence names found in the package being processed and the TO names connected to GoZync in your destination file (in GoZyncHosted or GoZyncMobile).

--> You may have related fields in your package but don't have their TO connected to GoZync in your destination file.

--> Or you simply don't have the right name either for the TO on the graph itself, OR in the integration setup in GoZyncHosted: you may have selected the wrong table occurrence or changed the TO name since the integration was done.

-> '''301 Record is in use by another user.''' Commonly called "record lock".

--> This is exactly what it sounds like.

--> FileMaker couldn't edit the record (or one of the related records for that inbox entry) because another user was editing it. Feel free to reprocess 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.

--> Hover over the error and our tool tip will tell you the field which 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.
(855) SEEDCODE
support@seedcode.com
Follow us: