none
Value was either too large or too small for a UInt64 . already installed the hotfix but still getting the error

    Question

  • Value was either too large or too small for a UInt64 . already installed the hotfix but still getting the error
    Wednesday, November 13, 2013 3:22 AM

All replies

  • Hi,

    We have been seeing exactly the same behaviour.

    A sync which has worked perfectly for years has just started failing because of this issue.  We have installed the hotfix, but it's not fixed things.

    Any ideas or workarounds?

    Sunday, May 25, 2014 7:40 PM
  • does any get the answer for sync fx 4.0 CTP ??

    Friday, May 30, 2014 6:10 AM
  • The problem is the timestamp tracking tables and stored procedures updatematadata, insertmetadata,and insert trigger for each table:

    1. You should to install the hotfix from Microsoft, which updates the Sync Framework 2.1 API.

    2. You should to change the trigger on each table, the@@DBTS+ 1 is replaced by CAST (@@DBTS as bigint)+1, the same replacement is done in stored procedures,updatemetadata,insertmetada of each table.

    It's solves the after problems ,but it's not solves above records.To find records that generate conflict we search for tracking tables, filtering by columns, scope_update_peer_timestamp ,local_update_peer_timestamp, scope_create_peer_timestamp, local_create_peer_tiemsatamp, if it's negative, you should update its value through CAST (@@DBTSasbigint) + 1
    Wednesday, November 26, 2014 2:10 PM