Duplicate key problem during Rebind

[kwalker]

Vault Team,

My company is evaluating Vault to replace Visual SourceSafe here.

I have installed Vault and built a repository using the Handoff feature. During the Handoff, only 10 files failed: 2 were .sln, 3 were .vssscc, 1 was .vspscc. I used Vault's Add Files feature (using your client application, not Visual Studio) to import them individually.

After that, I tried to use the Rebind feature on all the solutions and projects found in our repository, and it fails with this message:

Error while committing changes: A database error has occured (FailDBInsert)

The sgvault.log file indicates an exception has occurred:

System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'pk_tblfsobjectversionattrvalues'. Cannot insert duplicate key in object 'dbo.tblfsobjectversionattrvalues'.

I am attaching a file containing the log entries from last night's kickoff of the Handoff job through the exceptions from this morning's first Rebind operation. Let me know if I can provide more information. I would hate to have to manually Rebind all our projects and solutions. I might have to try building another repository from scratch and hope this problem does not occur the second time...

Thanks,
Ken

[Beth]

I think since you were having problems with the hand-off that we should step back and look at why that happened. I'd like to take this offline. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[kwalker]

Upon further investigation, Rebind was complaining about projects that were Shared. It did not seem to recognize that they were "copies" of the same project and whatever it was doing led to the "duplicate key" error. As a workaround, going through the list of projects to rebind and making sure only one copy of each shared project is checked seems to work.

Ken

[Beth]

Thank you for the update. I'm happy to hear you are working now.