Sharing a share generates primary key violation

[kasti]

Using Vault 3.5.0, but problem is in 3.*.*:

Every now and again, when sharing a Project (not file), we get the following error:

----04.10.2006 15:34:35 *********--172.16.11.218(172.16.11.218)--SSL Disabled System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK__@tbl__5DB5E0CB'. Cannot insert duplicate key in object '#5CC1BC92'.
The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at VaultServiceSQL.VaultSqlSCC.AddFSObjectShares(VaultSqlConn conn, Int32 nRepID, String strXml, Int64 nObjVerID, Int64 nFolderObjVerID, Int64 nTxID, Int32 nTxItem, String strItemPath, String strComment, VaultDateTime dtMod) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at VaultServiceSQL.VaultSqlSCC.AddFSObjectShares(VaultSqlConn conn, Int32 nRepID, String strXml, Int64 nObjVerID, Int64 nFolderObjVerID, Int64 nTxID, Int32 nTxItem, String strItemPath, String strComment, VaultDateTime dtMod)


This happens with quite a few projects that we have.

Current workaround: The projects in question have been shared to quite a few locations. We just share it from a different location and it will work without a problem.

Thanks,
Herbert.

[lbauer]

I believe you've reported problems with shares before -- we may have even worked on your Vault database. The errors indicate some type of database inconsistency -- possibly something that's been there a while but is exposed by a particular operation.

We may need to take another look at the database to resolve this. Email support@sourcegear.com if you want to pursue this.