The error in the server log looks like this:[11/13/2007 2:53:13 PM] Ending the transaction
[11/13/2007 2:53:32 PM] An error occurred while trying to end a transaction.
[11/13/2007 2:53:32 PM] An exception was encountered during the transaction. Exception: 1 : Failure 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.EndTx(String strTxID, Int32 nTxAction, DateTime& dtTxBegin, Int64& nNewRevision, VaultResponseItem[]& responses)
at VaultClientNetLib.VaultConnection.EndTx(String strTxID, Int64& nNewRevision, VaultResponseItem[]& responses, Int32 nAction, DateTime& txBeginDate)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
[11/13/2007 2:53:32 PM] Transaction failed
[11/13/2007 2:53:32 PM] Transaction failed
We are using Vault client and server version 3.1.8.3771.----11/13/2007 2:53:13 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled Ending transaction
----11/13/2007 2:53:13 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled Beginning SQL transaction 19360
----11/13/2007 2:53:13 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled Attempting to acquire repository lock.
----11/13/2007 2:53:13 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled Acquired repository lock.
----11/13/2007 2:53:13 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled TreeManager Signal - Tx Begin - CacheLockId:19361
----11/13/2007 2:53:13 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled TreeManager: A transaction is pending, but it belongs to the current user. Returning cached tree, revID 29025
----11/13/2007 2:53:31 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled TreeManager Signal - Tx End - TxID:29027 CacheLockId:19361 RepID:2
----11/13/2007 2:53:31 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled SQL transaction 19360 successfully rolled back.
----11/13/2007 2:53:31 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled Critical Error! Object reference not set to an instance of an object.
at VaultServiceSQL.VaultSqlSCC.BranchObject(VaultSqlConn conn, Int32 nRepID, Int64 nRootObjVerID, DateTime dtModDate, Int64 nTxID, Int32 nTxItem, String strItemPath, Byte nTxType, String strComment, String strMiscInfo, String strXml, String strDestParentPath, HybridDictionary htTxModifiedItems, VaultFSObject& fsoOut)
at VaultServiceAPILib.VaultTransaction.a(VaultTransactionContainer A_0, String A_1, String A_2, String A_3, VaultFindFolderEntry A_4, VaultFindFolderEntry A_5, Int64 A_6, Int64 A_7, VaultRequestBranch A_8, Boolean A_9, HybridDictionary A_10, String A_11, String A_12, String A_13)
at VaultServiceAPILib.VaultTransaction.PreCheckProcessBranchOrSnapshot(Int32 nCurrStatCode, VaultRequestBranch vrb, Boolean bCommitWork, VaultTransactionContainer txContainer)
at VaultServiceAPILib.VaultServiceAPI.EndTx(HttpApplicationState theApp, VaultLoginInfo vliLoggedInUser, Int32 nTxUserID, String strTxID, Int32 nTxAction, VaultIntTx vit, DateTime& dtTxBegin, Int64& nNewRevision, VaultResponseItem[]& responses, VaultRepository& repNew)
at VaultService.VaultService.EndTx(String strTxID, Int32 nTxAction, DateTime& dtTxBegin, Int64& nNewRevision, VaultResponseItem[]& responses)
----11/13/2007 2:53:31 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled ***Tree cache would have been flushed here***
----11/13/2007 2:53:31 PM jamesv--192.168.1.48(192.168.1.48)--SSL Enabled (1421fff0-e771-468e-9fef-1d470652f3d1) EndTx (Revision - 0) returned: Failure
We are able to branch each file individually from this folder, but not the folder itself. I have seen this issue elsewhere in the forums, but with no follow-up from the original poster with more information.
Can anyone help?