Here's what I did:
Add a repository
Add files and directories to the repository
Delete those files and directories
Obliterate everything
(As admin) right click on the repository root and select directories to add - but don't actually add them.
Log in to vault admin at the same time and change what extensions to add for that repository.
Close vault admin
Close the client.
Open the client - Now my previously obliterated directories are listed but I can't delete them again.
Open the vault admin
Delete the repository
CRASH
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at VaultAdmin.FormMain.CheckRepOptEnabled()
at VaultAdmin.FormMain.CommandDisplayRepOptions()
at VaultAdmin.FormMain.CommandApplyRepOptChanges()
at VaultAdmin.FormMain.CommandCheckRepOptionsUpToDate()
at VaultAdmin.FormMain.FormMain_Closing(Object sender, CancelEventArgs e)
at System.Windows.Forms.Form.OnClosing(CancelEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
VaultAdmin
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VaultAdmin.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
VaultClientOperationsLib
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VaultClientOperationsLib.DLL
----------------------------------------
VaultLib
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VaultLib.DLL
----------------------------------------
VaultClientUILib
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VaultClientUILib.DLL
----------------------------------------
VaultPresentationLib
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VaultPresentationLib.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
VaultClientNetLib
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VaultClientNetLib.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
nsdg60qa
Assembly Version: 3.1.8.3771
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
ovehmowy
Assembly Version: 3.1.8.3771
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
vs
Assembly Version: 1.0.2256.31774
Win32 Version: 1.0.2256.31774
CodeBase: file:///C:/Apps/Admin%20Tool/vs.DLL
----------------------------------------
VCDiff
Assembly Version: 3.1.8.3771
Win32 Version: 3.1.8.3771
CodeBase: file:///C:/Apps/Admin%20Tool/VCDiff.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Crash :(
Moderator: SourceGear
I don't have that setup anymore but I can give you a bit more information.
The first time around I created a directory called "Raknet" and added some directories and files under that.
The repository name was also "Raknet"
But I decided that I wanted those subdirectories under the root, rather than under a directory with the same name as the repository. Since I didn't know how to move them, I deleted everything instead. It seemed to work OK. I was logged in as admin in the client. I then logged in as admin with the Vault Admin Tool and obliterated that repository.
That's when I recreated the repository, opened the client again, and right clicked to add the subdirectories to the root. But it added some file extensions I didn't want so I (possibly reopened and) used the Admin tool to change the visible extensions while logged in. I probably closed and opened the admin tool several times while I was looking for the setting to use. When I found it, I didn't cancel the dialog in the client, I just task-switched to the admin tool. It gave the message that I had to shut down the client, so I did so, probably by just closing the client without closing the dialog. When I next logged in that's when the obliterated stuff showed up again.
The only other unusual thing I have is that I was previously changing ports a lot to try to figure out something that would get past my work firewall. Right now, and at the time of the crash, it's set to localhost:22 without SSL
The first time around I created a directory called "Raknet" and added some directories and files under that.
The repository name was also "Raknet"
But I decided that I wanted those subdirectories under the root, rather than under a directory with the same name as the repository. Since I didn't know how to move them, I deleted everything instead. It seemed to work OK. I was logged in as admin in the client. I then logged in as admin with the Vault Admin Tool and obliterated that repository.
That's when I recreated the repository, opened the client again, and right clicked to add the subdirectories to the root. But it added some file extensions I didn't want so I (possibly reopened and) used the Admin tool to change the visible extensions while logged in. I probably closed and opened the admin tool several times while I was looking for the setting to use. When I found it, I didn't cancel the dialog in the client, I just task-switched to the admin tool. It gave the message that I had to shut down the client, so I did so, probably by just closing the client without closing the dialog. When I next logged in that's when the obliterated stuff showed up again.
The only other unusual thing I have is that I was previously changing ports a lot to try to figure out something that would get past my work firewall. Right now, and at the time of the crash, it's set to localhost:22 without SSL
When you say "obliterated the repository", do you mean deleted and then obliterated the folders in that repository (in the obliterate tab), or deleted the whole repository from the admin tool (in the repositories tab)?
We need to determine whether this is a client state issue, or a problem with the DB itself. To do that, you should login to Vault from a different machine and see whether the obliterated items exist there. If they don't, it is a client state issue, and perhaps the Vault client got killed as it was writing state info to the cache file. Removing the cache files should resolve that.
We need to determine whether this is a client state issue, or a problem with the DB itself. To do that, you should login to Vault from a different machine and see whether the obliterated items exist there. If they don't, it is a client state issue, and perhaps the Vault client got killed as it was writing state info to the cache file. Removing the cache files should resolve that.