FailDBInsert error on shared file

[mizuni.admin]

We started receiving an error on some shared files. I have attached the log files from the server.
The errors occur when we are trying to check in the files and they happen on any machine.
We're using Vault Standard Version 5.1.1.

When we try to check in from the Vault client we receive a message box stating "A database error has occured (FailDBInsert)".

This is what shows in the messages area:
[1/18/2011 6:44:13 PM] Beginning transaction
[1/18/2011 6:44:13 PM] Check in $/Mainline .NET 2.0/ComponentArt.Web.UI/VersionInfo.cs
[1/18/2011 6:44:13 PM] Ending the transaction
[1/18/2011 6:44:15 PM] An error occurred while trying to end a transaction.
[1/18/2011 6:44:15 PM] Transaction failed
[1/18/2011 6:44:15 PM] Transaction failed

The attached logs say " Internal Data Consistency Error -- attempted to write 2 duplicate entries of object id 186982 into the folder with object id 183728. "

We just started receiving these errors today and none of these file links have changed in months. I tried running a database check (DBCC CHECKDB) and it came up clean. I have also tried wiping out the Vault cache on a client machine and resetting IIS with no luck.

Does anyone have any other ideas?
Thanks,
Jeff Rausch

[Beth]

Was Vault 5.1.1 the first version of Vault you started with or were you on previous versions before? If so, which versions?

Can you open a Vault GUI client, login, then go to Help - Technical Support and copy the information from there to me? I don't need the license count at the bottom, just the client and server info.

(Note for myself: Additional information posted here: http://support.sourcegear.com/viewtopic.php?f=5&t=14433&)

[mizuni.admin]

This is not the first version that we had, we upgraded to this version in December from 5.0.2 (and to that version from previous ones much earlier). I think we have been using vault for 5-6 years now.

Just to give a little background of the issue... How we noticed this issue is that for each solution our build process checks out a shared text file within that solution, updates a version number, and checks the file back in. That file is shared within each project of the solution. Yesterday our build worked for the first 8-9 solutions but then failed with a checkin error on this file. Now trying to checkin any shared file receives errors (even the ones that worked for the first 8-9 solutions in our build).

Technical Support Information:
Client Information
Vault Standard Client Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.4952
Operating System: Microsoft Windows 7 Ultimate
Service Pack: 0.0
OS Version: 6.1.7600
Total Physical Memory: 4 GB
Time Zone: (UTC-06:00) Central Time (US & Canada)

Server Information
Server Version:
.NET Framework Version:
Operating System:
Service Pack:
OS Version:
Timezone:

EDIT: Not sure why my machine doesn't show the server information... Here's the Technical Support Information from the vault client on our build server. Also, at the time we upgraded to 5.1.1 we also moved the vault server and the database to new servers. We have been able to successfully build after that until yesterday.
Client Information
Vault Standard Client Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.3615
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Total Physical Memory: 3.75 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Server Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.4952
Operating System: Microsoft Windows Server 2008 R2 Standard
Service Pack: 0.0
OS Version: 6.1.7600
Timezone: (UTC-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)

[mizuni.admin]

Sorry about all these posts, just trying to narrow down things.

Ok, the second error that I got (on the related post) was an open transaction error caused by the first issue. After that transaction closed I can check in/out the second shared file so it's not an issue with all shared files.

[Beth]

Even though you may have already performed part of what I'm about to give you for instructions, I'd like you to do the steps I'm going to list here exactly as written and then let me know your results.

1) Shut down all instances of the Vault GUI client and Visual Studio and any programs that may be integrated with Vault on your machine.
2) Rename your client-side cache per the instructions posted here: Clear Client Side Cache
3) On the Vault server, reset IIS by going to Start - Run and typing iisreset. Stopping and starting IIS will not accomplish the same thing. If you have other websites on this server that are mission critical, then let me know and I'll give an alternative action.
4) Restart one instance of the Vault GUI client.
5) You will need to set your working folders again, and perform a Get Latest with the option Do Not Overwrite/Merge Later selected. That will set all the statuses again.
6) Try the action again on the shared file that is a problem and let me know your results.

[mizuni.admin]

After trying that I received the same error.

We're trying to get a build done because we need to do a product release ASAP so I'm also trying a few other things and I did get a little farther.

This issue is happening in 2 separate folders/solutions. In the first one I deleted all instances of the shared file, re-added the file, and then re-shared it. This worked correctly and now the file is able to be checked in/out.
In the second solution I tried the same thing. Deleted all instances of the shared file. Then checked it into the main solution folder. This works fine, I am able to check in/out that file. But now when I try to share the file I receive a different error.
I have attached 2 more files. The first one (Checkin_Error_On_Sharing_File.txt) contains logs from checking in the file again and then also shows the error received trying to share it out immediately after that. The second file (Error_On_Sharing_File.txt) is an error that I receive now when trying to share the file. I'm not sure why the error changes when trying to do the same thing but it seems to.

The messages in the logs say duplicate entries of an object exist, even after deleting the file. Do I need to obliterate the file so it really doesn't exist anymore?

Here's the messages from the messages pane in the GUI client. The timestamps correspond with the log files.
1/19/2011 2:47:17 PM] Preparing data to begin transaction
[1/19/2011 2:47:17 PM] Beginning transaction
[1/19/2011 2:47:17 PM] An error occurred while trying to begin a transaction.
[1/19/2011 2:47:17 PM] Transaction failed
[1/19/2011 2:47:17 PM] An exception was encountered during the transaction. Exception: Server was unable to process request. ---> Error in the application. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.BeginTx(Int32 nRepID, String strComment, VaultRequestItem[]& requests, String& strTxID)
at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]& requests, String& strTxID, String comment)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, String strChangeSetComment, Boolean keepCheckedOut, Boolean removeLocalCopy, CommitType committype, VaultDateTime dateImport, Int32 nUserIDImport, Int64& nRevID, Int32[]& retBegEndTx)
[1/19/2011 3:00:39 PM] Preparing data to begin transaction
[1/19/2011 3:00:39 PM] Beginning transaction
[1/19/2011 3:00:39 PM] Share $/Mainline .NET 2.0/Mizuni.URP/Mizuni.URP.Module/VersionInfo.cs
[1/19/2011 3:00:39 PM] Ending the transaction
[1/19/2011 3:00:39 PM] An error occurred while trying to end a transaction.
[1/19/2011 3:00:39 PM] Transaction failed
[1/19/2011 3:00:39 PM] Transaction failed

[Beth]

Don't do any obliterating right now. I'd like to take this conversation offline so that we can get more data. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?