1631 Error

[amallison]

1. I have a container field that stores the data in the FM file. It is on the sync layout but I am getting the following error.

 

• There was a problem writing record 'null' to FileMaker Server

sync_JOBS. 'SignOffSignature_r' could not be set to Binary object

‘Signature 23-05-2014 8.41.17 am.png' because of an error 1631,

which means that the connection failed while pulling container data

from MirrorSync server to FileMaker Server sync_.JOBS. The

remaining fields were written successfully. The record will be retried

on the next sync.

 

Any suggestions?

 

2. Related to this is:

The rest of the data is written to the hosted file. If I then make a data modification to a field on the server in that record and try and sync again, I loose the change. It looks like the mobile data rewrites back to the already synced field.

[Jesse Barnum]

Andrew, could you file a bug report using the 'report a bug' link on the MirrorSync launch page? This will send us your MirrorSync server log file, which should have more details about the error. Keep in mind that the logs reset every night at midnight, so be sure to file the bug report on the same day that the error occurred.

[amallison]

Thanks I have submitted the bug report though it look like it locked up. A confirmation email did come through.

[UltimateTech]

I had this exact same issue when I was trying to use a dodgy 3G/4G connection to sync the database. It always copied the text fields across, but caused issues with containers. and although it said it would try again on the next sync, the containers still never populated.

[Jesse Barnum]

@UltimateTech: I could not reproduce the problem where the container fields are not being retried. If you notice this happening again, please use the 'report a bug' link from the MirrorSync launch page to send me the server log file.