Exception when checking in

[Tilman]

Hi,

we seem to be having a problem similar to this

http://support.sourcegear.com/viewtopic.php?t=9960

Technical Support Info:

Client Information
Vault Client Version: 4.0.6.15954
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 3.25 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 4.0.6.15954
.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) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
9 serial number(s):
1 of 9: 4 full users, permanent
2 of 9: 5 full users, permanent
3 of 9: 10 full users, permanent
4 of 9: 5 full users, permanent
5 of 9: 5 full users, permanent
6 of 9: 5 full users, permanent
7 of 9: 5 full users, permanent
8 of 9: 36 full users, permanent
9 of 9: 5 full users, permanent


What happens is, whenever someone tried to check in a specific file we got this exception:

[30/05/2008 11:33:35] 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 server log says this:

----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled BeginTx beginning transaction
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled TreeManager: cache matches repository revision and folder security hasn't changed. Returning cached tree, revID 277436
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled BeginTx: Critical Error! Error in the application.
at VaultServiceBase.VaultFolder.DeleteFolderEntryByName(HybridDictionary htParentObjects, String strSearchName, Int32 nObjType, Int32 nFSOHashCode)
at VaultServiceBase.VaultRepository.CreateFolderReferenceCopy(Int64 nRevID, HybridDictionary hdNewRefParents, VaultFolders vfOwners, VaultFolder vfOld)
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)
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled (8318139a-97d8-4225-92e8-b6a7b7bbd3e5) BeginTx returned: FailInvalidToken
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled (8318139a-97d8-4225-92e8-b6a7b7bbd3e5) CheckIn: $/Red Gate/Internal projects/SQL Server Central Blogs/Trunk/SSC/Themes/SSC/Blogs/blogs.Master returned: nil
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled Getting repository Structure-> Rep ID: 3 Base: 277436 Target: -1
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled TreeManager: cache matches repository revision and folder security hasn't changed. Returning cached tree, revID 277436
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled VaultServiceAPI::GetRepositoryTreeDelta() UserID:116 RepID:3 Base:277436 Target:277436 Calling VaultRepUtil.DiffRepTrees() - in-memory tree diff.
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled GetRepositoryStructure returned: Success
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled Getting list of checkout changes.
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled Beginning SQL transaction 23386282
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled GetCheckoutListChanges: Transaction Started
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled SQL transaction 23386282 successfully committed.
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled GetCheckoutListChanges: Transaction Committed
----5/30/2008 11:30:42 AM xxx.xxx--yyy.yyy.yyy.yyy(yyy.yyy.yyy.yyy)--SSL Disabled GetCheckOutListChanges returned: Success

Restarting IIS made the problem go away.

The files were added normally, i.e. no VSS import.

Cheers,

Tilman

[Beth]

This issue is still being worked on by the developers. I will follow up when I know a little more.

[Tilman]

Any news on this? It's happening again.

Cheers,

Tilman

[jeremy_sg]

This was found to be a bug with how older versions of Vault behaved under the .Net 2.0 framework. We've corrected the problem in Vault 4.1.3.