An exception was encountered during the transaction

[brianpmccullough]

Hello,

I was working in a branch today, when I did something pretty close to the following:

• Checked out two .sql files
• Decided to delete the files from Vault (still checked out - forgot to undo checkout)
• Attempted to add the files back to Vault
• Received the following error message from Vault client (note that the times are off a bit from when it actually occurred as I have tried a number of things to correct this since then):

[11/19/2008 3:53:30 PM] Transaction failed
[11/19/2008 3:53:30 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)


The error message doesn't really give me much to go on. After some review on the threads here, I found that it would likely be helpful to post some more information.
Here are the server logs from the time the error started occurring on my end (formatting applied by me and some values changed to protect identities/file names/etc):

----11/19/2008 1:58:43 PM myuser.name--192.168.127.xx(192.168.127.xx)--SSL Enabled BeginTx: Critical Error! Error in the application.
at VaultServiceBase.VaultRepository.GetReferenceCopiesByPath(Int64 nRevID, HybridDictionary hdNewRefParents, String strAbsolutePath, Boolean bRefCopyLastObjectWithAllFolders, VaultFSObjects& fsoList, Int32& nPinCount)
at VaultServiceAPILib.VaultTransactionContainer.GetReferenceCopiesByPath(String strAbsolutePath, VaultFSObjects& fsoList, Int32& nPinCount)
at VaultServiceAPILib.VaultTransaction.PreCheckCheckIn(Int32 nCurrStatCode, VaultRequestCheckIn vrci, String strFileToken, VaultResponseCheckIn vRespCheckIn, VaultTransactionContainer txContainer)
at VaultServiceAPILib.VaultServiceAPI.BeginTx(Int32 nTxUserID, Int32 nRepID, VaultDateTime dtBeginTx, String strComment, VaultRequestItem[]& requests, String& strTxID, VaultIntTx& vit)
at VaultService.VaultService.DoBeginTx(String strCallerLogEvt, Int32 nTxUserID, Int32 nRepID, VaultDateTime dtBeginTx, String strComment, VaultRequestItem[]& requests, String& strTxID)
----11/19/2008 1:58:43 PM myuser.name--192.168.127.xx(192.168.127.xx)--SSL Enabled (14212451-1fad-4260-9bbb-f8e2af8c2d3e) BeginTx returned: FailInvalidToken
----11/19/2008 1:58:43 PM myuser.name--192.168.127.xx(192.168.127.xx)--SSL Enabled (14212451-1fad-4260-9bbb-f8e2af8c2d3e) CheckIn: $/Branches/Project/Path/SQL/Stored Procedures/MySp1.sql returned: nil
----11/19/2008 1:58:43 PM myuser.name--192.168.127.xx(192.168.127.xx)--SSL Enabled (14212451-1fad-4260-9bbb-f8e2af8c2d3e) CheckIn: $/Branches/Project/Path/SQL/Stored Procedures/MySp2.sql returned: nil





Here is my vault information retrieved from the client:

Client Information
Vault Client Version: 4.0.5.15922
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Service Pack: 2.0
OS Version: 5.2.3790
Total Physical Memory: 1.7 GB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Vault Server Version: 4.0.5.15922
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-04:00) Atlantic Time (Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
4 serial number(s):
1 of 4: 5 full users, permanent
2 of 4: 2 full users, permanent
3 of 4: 5 full users, permanent
4 of 4: 10 full users, permanent


Based on server logs it looks like my login is invalid? I don't know how this could be as it is integrated with AD and I have no problems accessing email and other network resources. This was working fine for me today, up until about 1pm EST.

[lbauer]

Is there a particular reason you wanted to delete files from the Vault repository and add back the same files, rather than just editing the files and checkingthem in?

Your login is ok -- but there was a problem with the session.

You can try restarting IIS (use "iisreset" from a command prompt) to see if the server error is cleared up.

[brianpmccullough]

Why I wanted to delete and then re-add:

1. I wasn't concerned with the history (it was only 1 previous checkin - initial creation).
2. The file was originally saved as UTF-8 rather than ANSI. UTF-8 gives my SQL deployment scripts fits, so I re-saved as ANSI. Vault started giving me fits during the checkin of the new ANSI encoded file, so I attributed to the fact the file was originally encoded as UTF-8 and was now ANSI, so I tried to delete and recreate.


I will have our network ops team try an IISRESET on the server.

If it helps any, we all work "disconnected". That is, we are all working at home, no VPN connection, and all login to our Vault repositories over HTTP(S).

Thanks!

[ian_sg]

Thanks for preemptively including the server log.

This error is caused by a hash collision in the server's in-memory model of the repository. (In our defense, this is the stock .NET 2.0 hash algorithm that's failing.) As Linda mentioned, restarting IIS on the server will make the error go away.

We fixed this issue in Vault 4.1.3, which is a free upgrade for you.

[brianpmccullough]

IISRESET seems to have resolved this issue.

We'll look to upgrade to 4.1.3 in the coming weeks.

Thanks!

[ian_sg]

Thanks for the follow-up. Let us know if there's anything else we can do to help.