Violation of PRIMARY KEY constraint 'PK_tblWindowsRelations'. Cannot insert duplicate key in object 'dbo.tblWindowsRelations'. The statement has been terminated. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_tblWindowsRelations'. Cannot insert duplicate key in object 'dbo.tblWindowsRelations'. The statement has been terminated.Have you got now some solution for this problem? Best Regards Vlada
Hi. Late response but might help someone. The problem still occurs and is most likely caused by trust relationships between domains. The easy fix is to simply remove the primary key on tbl_windowsrelations. The problem still occurs in CMS 5 R2.
EPiServer has two updated stored procedures that will fix this issue.
The problem still exists in SP3.
This is a known issue in which according to buglist should be fixed in EPiServer CMS R1 SP2,
#8865 Logging on with the Windows membership provider will sometimes give a "violation of primary key constraint"
There is a hotfix available from EPiServer Developer Support
Yes I've been told that this is a known issue and it should be fixed in SP2 but we are now running R2 and the problem still occurs. I've got the two SP's now and will try them out as soon as i get the time.
For everybody from EPiServer reading this, there is also an open supportcase (119334 ) regarding this case.