I’ve seen this error come up a few times now, and there’s a (dirty, ugly) hack you can use to fix it. So, for those who are fans of dirty, ugly hacks, here you go.

If you see the error:

ACM encountered the following error while performing synchronization:

Persistence_FlushSqlError
Violation of PRIMARY KEY constraint ‘IssueSolution_PrimaryKey’.
Cannot insert duplicate key in object ‘dbo.IssueSolution’.
Stale Data
The statement has been terminated.

Would you like to retry?

You can fix it by (remember, I said it was a dirty, ugly hack) removing the constraint:

ALTER TABLE [dbo].[IssueSolution] DROP CONSTRAINT [IssueSolution_PrimaryKey]

Good luck, and sorry for the bug.