Folder 'stuck' in vault, not available in Admin Tool

[danroot]

I'm using Vault 3.5.1.4786. I have a folder that is available in my client tool that checkins were failing for with the error 'Transaction failed'. I decided to delete it and start over, but delete fails with '] An error occurred while trying to end a transaction. Transaction Failed. Item $foldername caused the transaction to fail:Deletion failed'. Since I could not delete, I decided to try to obliterate the folder and start over. However when I go to the Admin tool, the folder is not visible in the obliterate tab. We only have one repository & server, and all other folders are visible, so I'm sure I'm connected to the right place.

Why is the admin tool and client tool out of sync? How can I either delete or obliterate this folder?

Below is a client log when trying to delete the folder:
1/16/2009 11:22:59 AM <generic>: Emergency logging enabled in Windows Forms client
1/16/2009 11:23:11 AM <busy>: Setting GUI to busy.
1/16/2009 11:23:13 AM <mutex>: Took mutex 1268
1/16/2009 11:23:13 AM <refresh>: Serialized CacheMember_ChangeSetItems
1/16/2009 11:23:13 AM <mutex>: Released mutex 1268
1/16/2009 11:23:13 AM <commit>: Beginning commit with 1 items
1/16/2009 11:23:13 AM <commit>: Creating requests.
1/16/2009 11:23:13 AM <createrequest>: createrequest started for $/Miller ChangeSetItem_DeleteFolder
1/16/2009 11:23:13 AM <createrequest>: createrequest finished for $/Miller ChangeSetItem_DeleteFolder
1/16/2009 11:23:13 AM <connection>: BeginTx started.
1/16/2009 11:23:13 AM <connection>: BeginTx finished.
1/16/2009 11:23:13 AM <connection>: EndTx started.
1/16/2009 11:23:13 AM <connection>: EndTx finished.
1/16/2009 11:23:13 AM <commit>: dummy exception
1/16/2009 11:23:13 AM <commit>: at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, String strChangeSetComment, Boolean keepCheckedOut, Boolean removeLocalCopy, CommitType committype, VaultDateTime dateImport, Int32 nUserIDImport, Int64& nRevID, Int32[]& retBegEndTx)
1/16/2009 11:23:13 AM <refresh>: Refresh started
1/16/2009 11:23:13 AM <refresh>: delta passed in was null, retrieving one
1/16/2009 11:23:13 AM <refresh>: calling GetRepositoryStructure(1, 9924, -1, ref, 2/22/2007 6:49:54 PM)
1/16/2009 11:23:13 AM <connection>: GetRepositoryStructure started.
1/16/2009 11:23:13 AM <refresh>: GetRepositoryStructure started
1/16/2009 11:23:13 AM <refresh>: Calling client service GetRepositoryStructure(1, 9924, -1, 2/22/2007 6:49:54 PM, ref, ref, ref)
1/16/2009 11:23:13 AM <refresh>: Client service GetRepositoryStructure returned: dtLatestCheck 2/22/2007 6:49:54 PM, nReturnDestRevision 9924, rd not null True
1/16/2009 11:23:13 AM <refresh>: GetRepositoryStructure finished
1/16/2009 11:23:13 AM <connection>: GetRepositoryStructure finished.
1/16/2009 11:23:13 AM <mutex>: Took mutex 1284
1/16/2009 11:23:13 AM <refresh>: Serialized CacheMember_LastStructureGetTime
1/16/2009 11:23:13 AM <mutex>: Released mutex 1284
1/16/2009 11:23:13 AM <refresh>: GetRepositoryStructure returned: returnedRevision 9924, newLatestDate 2/22/2007 6:49:54 PM, delta not null: True
1/16/2009 11:23:13 AM <checkoutlist>: RefreshCheckOutList started
1/16/2009 11:23:13 AM <checkoutlist>: Call GetCheckOutListChanges(Rep 1, Rev 14494, LastUpdt 2/22/2007 6:49:54 PM)
1/16/2009 11:23:13 AM <connection>: GetCheckOutListChanges started.
1/16/2009 11:23:13 AM <connection>: GetCheckOutListChanges finished.
1/16/2009 11:23:13 AM <checkoutlist>: GetCheckOutListChanges returned: Rev 14494 completeList False, newLastUpdt 2/22/2007 6:49:54 PM
1/16/2009 11:23:13 AM <checkoutlist>: New items:
1/16/2009 11:23:13 AM <checkoutlist>: <null>
1/16/2009 11:23:13 AM <checkoutlist>: Release items:
1/16/2009 11:23:13 AM <checkoutlist>: <null>
1/16/2009 11:23:13 AM <checkoutlist>: Source and target check out list revisions are both 14494, and last locking date match. Returning with no update
1/16/2009 11:23:13 AM <checkoutlist>: RefreshCheckOutList finished
1/16/2009 11:23:13 AM <refresh>: Calling Repository.Update with delta
1/16/2009 11:23:13 AM <refresh>: Repository.Update finished, calling SaveRepositoryIfNothingOnDisk()
1/16/2009 11:23:13 AM <mutex>: Took mutex 1240
1/16/2009 11:23:13 AM <refresh>: SaveIfNothingOnDisk: not saving
1/16/2009 11:23:13 AM <mutex>: Released mutex 1240
1/16/2009 11:23:13 AM <refresh>: Refreshing working folder associations from disk
1/16/2009 11:23:13 AM <mutex>: Took mutex 1244

[Beth]

Is that folder by any chance listed in your Pending Checkins? Is it a fully committed add? Can other users see that folder?

If the folder has not been committed, then removing it from the Pending Checkins and it will not be seen in your client.

[danroot]

There are no pending checkins for this folder - there were, and I was unable to check in due to similar 'Transaction Failed' errors. I was able to 'undo checkout', though, and now the entire folder & subfolder is considered 'checked in.' Other users see the folder in vault client, including the default 'admin' user. The same admin user cannot see the folder in vault admin tool. I'm not sure what you mean by 'fully committed add'. We've been working against it with no problems for a few weeks, so there have been fully committed transactions against the folder.

[danroot]

I also noticed that I could not add new folders to the repository root, or files to any existing projects (not just the one that initially was 'stuck'). I was able to resolve this, I think, by rebooting the server. After that, the "stuck" folder had checked out files in the vault client, even though I had checked them in previously. It also still did not appear in the obliterate menu. I was able to check in the files and then delete the folder. I re-added the folder and solution, and now it appears in obliterate (though I no longer have a need to use that).

[Beth]

It sounds like the culprit may have been some bad information in your client-side cache. It sounds like you're working ok at the moment though. If you have any further questions, just let me know.