Client sending wrong SyncLastReceivedAnchor Value? RRS feed

  • Question

  • I'm still in the development phase of a windows mobile 6.5.3 phone that is using microsoft sync services for ado.net (devices) to sync data between and sql compact database and sql server.  I'm currently using batching and eveything seems to be working fine for the most part.  The problem I'm experiencing now is that on syncs that occur after first initial sync some of the tables are having all of the rows updated back to the client even though there is has been no changes to synchronize.  I looked at the server trace log and it shows that one of these tables in particular passed the wrong SyncLastReceivedAnchor value.  The one it passed belongs to a record in that table that exists on the server side and it is a very old record that doesn't even exist on the client.  Have I set up something wrong and is there way for figure out where the breakdown may be occuring?  Thanks for any and all help.


    Friday, July 26, 2013 12:20 AM

All replies

  • afaik, the SyncLastReceivedAnchor  is not really the timestamp of the last row received from the server. it's the timestamp on the server for the last sync.
    Friday, July 26, 2013 3:26 AM
  • Ok.  Thanks.  In this case I had initially synced the client 2 days ago and since that time around 500 rows of data had changed, but when the client is syncing now it's updating all of the rows in the table (around 100000 records), instead of just that 500.  Have I set up something wrong?  Where should I look? 


    Friday, July 26, 2013 3:30 AM