I am getting the following error whenever I try to delete a file from a particular repository (we have three separate repositories). I am unaware of any changes to my system and have attempted using the client on the vault server directly using both my account (rusc) and the admin account, both produce the same error. I can check files in / out.
Here is the appropriate portion of the server log:
Login
----4/23/2004 6:22:45 PM rusc--endxdev(192.168.1.5)--SSL Disabled
Critical Error! Error in the application.
at VaultServiceBase.VaultRepository.a(Int64 A_0, Hashtable A_1, String A_2, Boolean A_3, VaultFSObjects& A_4, Int32& A_5)
at VaultServiceBase.VaultRepository.GetReferenceCopiesToPathFolderOnly(Int64 nRevID, Hashtable htNewRefParents, String strAbsolutePath, VaultFSObjects& fsoList, VaultFSObject& fsoLastItem, Int32& nPinCount)
at VaultServiceAPILib.VaultTransaction.PreCheckProcessDelete(Int32 nCurrStatCode, VaultRequestDelete vrd, Boolean bCommitWork, VaultTransactionContainer txContainer)
at VaultServiceAPILib.VaultServiceAPI.BeginTx(HttpApplicationState theApp, VaultUser vuLoggedInUser, Int32 nTxUserID, String strHostname, Int32 nRepID, DateTime dtBeginTx, String strComment, VaultRequestItem[]& requests, VaultLogFile vlfLogger, String& strTxID, VaultIntTx& vit)
at VaultService.VaultService.DoBeginTx(HttpApplicationState theApp, String strCallerLogEvt, VaultUser vUser, Int32 nTxUserID, String strHostName, Int32 nRepID, DateTime dtBeginTx, String strComment, VaultRequestItem[]& requests, String& strTxID)
Error: Server Unavailable for Transaction begin
Moderator: SourceGear
you stated nothing has been changed in your setup. are you certain?
i just ran through a trace of the code:
GetReferenceCopiesToPathFolderOnly() calls
GetReferenceCopiesByPath(long , Hashtable , string , bool , ref VaultFSObjects , ref int ) - which the declaration for your stack trace's VaultRepository.a().
there is nothing too fancy here. just use of a stack object to walk your source tree to root.
some questions:
1) is there anything unusual about the path to the file? is it possibly shared or in a shared folder that is also has a parent which is shared?
2) do you happen to have more than 2 GB of memory on your vault server? if so, what version of vault are you using?
3) can you do anything else to the file (like move it)? if you can move it, can you delete it after that?
i just ran through a trace of the code:
GetReferenceCopiesToPathFolderOnly() calls
GetReferenceCopiesByPath(long , Hashtable , string , bool , ref VaultFSObjects , ref int ) - which the declaration for your stack trace's VaultRepository.a().
there is nothing too fancy here. just use of a stack object to walk your source tree to root.
some questions:
1) is there anything unusual about the path to the file? is it possibly shared or in a shared folder that is also has a parent which is shared?
2) do you happen to have more than 2 GB of memory on your vault server? if so, what version of vault are you using?
3) can you do anything else to the file (like move it)? if you can move it, can you delete it after that?
Jeff Clausius
SourceGear
SourceGear
just a follow up here. it turned out crushton's repository (from 10 months ago) had some badly mis-aligned shares.
although not 100% certain, i believe this problem might have been caused by the (long since fixed) vault 1.0 -> vault 1.1 upgrade script timeout, and the problem lay dormant until now.
in the end, the story has a happy ending. he ran the fixshare utility, and a small database script which brought all shares back in line. the repository now seems to be working nicely.
although not 100% certain, i believe this problem might have been caused by the (long since fixed) vault 1.0 -> vault 1.1 upgrade script timeout, and the problem lay dormant until now.
in the end, the story has a happy ending. he ran the fixshare utility, and a small database script which brought all shares back in line. the repository now seems to be working nicely.
Jeff Clausius
SourceGear
SourceGear