Community
Showing results for 
Search instead for 
Do you mean 
Reply

Problems syncing remotely

Accepted Solution Solved
jsk
Astute Commentator
Posts: 15
Country: USA
Accepted Solution

Problems syncing remotely

I have recently started having trouble syncing remotely. None of the other remote users are having any problems so I think it is with my laptop.


I get through to the end of the sync but then the following error messsage appears:

 


"Synchronization has failed. Cannot insert duplicate key row in object

‘sys.syscommittab’ with unique index ‘si_xdes_id’.

Failed to flush the commit table to disk in dbid 7 due to error 2601. Check the

Errorlog for more information

The statement has been terminated. Contact your administrator for assistance."

 

Any help would be great.




Accepted Solutions
Solution
Accepted by topic author jsk
‎09-25-2015 03:20 AM
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Problems syncing remotely

Here is an article with steps to resolve: KB Article 28141

Greg Martin
Sage

View solution in original post


All Replies
Solution
Accepted by topic author jsk
‎09-25-2015 03:20 AM
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Problems syncing remotely

Here is an article with steps to resolve: KB Article 28141

Greg Martin
Sage
Nickel Super Contributor
Posts: 843
Country: United States

Re: Problems syncing remotely

14.1.108 Premium

Same error here.

Tried KB 28141 but no luck.

Ended up recreating remote, and everything worked fine for a couple of weeks.

Error is back again.

HELP!!!

Rita Kogstad
RKA Associates
Stamford, CT
Bronze Elite Contributor
Posts: 1,409
Country: United_Kingdom

Re: Problems syncing remotely

Have also been having this problem recently over a number of sites. It looks like after a recent MS SQL update that things started to play up. It seems to behave like a flu virus passing from 1 database to another via sync.

 

I have tried the various solutions and now strongly promote running the scrip on all machines with a database and the server making sure no one syncs while this is done. )Using the  ACTDIAG option does not let you know if it has cleared the error even thought it reports success at the end.)

 

The script must be run until it come up with a (0) which I found meant 3 or 4 times.

 

Not in the article but essential is always right click on the script and run as administrator