Gianluca D'Aquino

The attempt to push data to the server has failed. (The message received from the server was: "111A01C0-27AE-414B-AC1C-DC56C83F877E

6 posts in this topic

Hello there,

I've set up 2 files syncing with Easysync. I've set up just a single table in sync called ES_TRIP (without pull or push, because I want to sync in both directions, is that correct).

I put the same cfg on mobile and on host file and the process start working but it throws me an error:

"The attempt to push data to the server has failed. (The message received from the server was: "111A01C0-27AE-414B-AC1C-DC56C83F877E"

The hosted file is on a fm server 15 that is reachable and working - I've tried the hosted link and it is correctly working.

The TRIP child table is set to add record (but not delete) on both files.

What should I check on it?



Share this post

Link to post
Share on other sites

The host file and mobile file are not the same. They each use different scripts. If you want to sync in both directions, you'll need both push and pull.

I suggest using Tim's samples to test your setup.

Share this post

Link to post
Share on other sites

Ok thanks.

What I mean is that based on the relationship that are set between sync table are the same on host and on mobile.

I've followed the setup on Tim's site and did everything as written. I set a single table to sync in 2 directions, so the name of the table is ES_TRIP.

I've tried setting on a push or a pull only configuration and in all the cases is not working.

If I put the example hosted file on the server and then I try to sync the mobile it works.



Share this post

Link to post
Share on other sites

Oh, you got trapped by the Device ID. You're blocking yourself. 



Share this post

Link to post
Share on other sites

Please read the link I proved. It's essentially that you understand round-tripping and the use of the Device ID to suppress it.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Joshua Willing Halpern
      Hey again. In a previous thread I suggested using javascript in a webviewer to return the difference between the server and client UUID lists in order to increase the sync check speed. It was much faster, but the code I used included an algorithm with quadratic time complexity, meaning that as the size of the lists increased the time that sync check took would grow exponentially. @GisMo helped test confirm that this solution would not scale well.
      However I think I've found a bit of javascript that solves this issue and will scale linearly. I've changed the script from the previous thread to use this new code instead. If you are using this javascript method for list comparison I highly recommend you change the sync check script to use this code. Simply open the new file, copy the calculation from set variable[ $url ] in "Sync Check Client", and paste it into your Set Variable[ $url ] step.
      Otherwise if you're using EasySync and struggling with sync check, give my solution a try!
      I've attached the new file below and linked to the old thread for continuity.
      Best, Josh
      EDIT: For anyone interested in a demonstration of just the algorithms' performance difference before updating sync check, I've uploaded a raw concept file.


    • By folks
      Have been using easySync for a while, but recently I have a problem where Close File ["Hosted_Database"]  does exactly that on OS X but leaves the server open on iOS.
          OS X: FM Pro 14 & 15
          iOS: FMGo 14 & 15    
      Tired adding a Close File ["Hosted_Database"] in line 136 of "Sync With Server"  at the beginning of #restore user interface
      but this just generates an error 301:  which is record is already in use.  But of course the error only occurs on FMGo.
      I must have done something simple to cause this but not sure what… any ideas are most welcome.
    • By Steve Cooper
      I am conducting an initial test of FM easy sync.  I am working on a system that I have in production with synchronization logic that I scripted myself (to iPads from FM Server).  The sync to the iPads using my logic is rather ponderous, so I am researching alternates to speed things up.
      I carefully applied the changes described in the FMEasySync setup document to my server file & the client file.  I cleared all data from the client file - anticipating it would then do a full synchronization from the server to the client. 
      The primary table has over 150,000 records, so I did not expect it to be quick, but I am puzzled at what happened.  It seemed to run without error, but was so slow, I thought it had stalled.  I waited over 24 hours and in that time the progress indicator said it has processed about 500 records.
      I conducted a brief review of where it was going in the debugger, but could not see any obvious problems with how I had inserted the elements into my solution.
      I figure, there must be something grossly wrong with how I put this together.  Any thoughts out there?
      ... Steve.
    • By folks
      Just wondering about compatibility of EasySync and EasyDeploy with Filemaker Pro, Go and Server 14 ?
    • By folks
      EasySync: Any Way To Sync Found Set?
      GZync does this is there a way to do this within FM Easy Sync?
      Perhaps I am missing the obvious.
      "Folks use this to deliver just one user’s records–usually very specific things like “my customer visits for today” or “my active orders in this territory”.…
      To control which records are pulled down to your iPads and iPhones: GoZync will look within the results of a find request for records that have changed since the last sync. If you can write a find request, you can sync that found set down to your users."
      In the application I am working on it would be useful to just pull data for a specific region, since a full sync of the database may get too big over time, depending of course how full people keep their iPads.
      Any Suggestions are most welcome,
      Thank you