new install for evaluation but cannot add solution

[JohnWilk]

I have just downloaded and installed Vault for evaluation. I get an exception when I try to add a solution to source control from the IDE.

Vault's version is version 4.1.3. I am using VC2003 version 7.1.6030. I have enabled "Make Vault your default SCC provider". I have tried running aspnet_regiis -u and -i, followed by iisreset but to no effect.

I have appended the crash dump. Any help would be appreciated,

Thanks
John

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 VaultClientPresentationLib.FormIDEViewRepository.FormIDEViewRepository_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultPresentationLib
Assembly Version: 4.1.3.18336
Win32 Version: 4.1.3.18336
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VS2003_Client/VaultPresentationLib.DLL
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
VaultLib
Assembly Version: 4.1.3.18336
Win32 Version: 4.1.3.18336
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VS2003_Client/VaultLib.DLL
----------------------------------------
VaultClientOperationsLib
Assembly Version: 4.1.3.18336
Win32 Version: 4.1.3.18336
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VS2003_Client/VaultClientOperationsLib.DLL
----------------------------------------
VaultClientNetLib
Assembly Version: 4.1.3.18336
Win32 Version: 4.1.3.18336
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VS2003_Client/VaultClientNetLib.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System.Web.Services
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
gdoit2zu
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2407
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll
----------------------------------------
VaultClientUILib
Assembly Version: 4.1.3.18336
Win32 Version: 4.1.3.18336
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VS2003_Client/VaultClientUILib.DLL
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------

[billb]

Am having the exact same problem in the same environment.

[Beth]

Could you open your Vault GUI client, go to Tools - Options, and on the General page check to see that Vault is set as the default SCC provider? If not, then close VS, set that option in Vault, and reopen VS 2003.

if that doesn't help, then could you post screenshots of the values under these registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders

[JohnWilk]

I re-enabled the "Make Vault your default SCC provider" flag which I turned off to allow me to continue working with SourceSafe. This time the "Add solution to source control" menu command initially did not crash. It seemed to work, asking me to log on. However none of the other menu items became enabled and I could not see the project in the client. I then tried to add the solution again and got the previous crash.

Here are the screen shots you asked for:

reg1.jpg (42.39 KiB) Viewed 4538 times

reg1.jpg (42.39 KiB) Viewed 4538 times

[Beth]

Could you expand the InstalledSCCProviders folder as well and show that? I see 3 screenshots above that are all the same thing.

[JohnWilk]

Here is the screen shot for the InstalledSCCProviders folder. Sorry for the delay.

reg3.jpg (38.76 KiB) Viewed 4496 times

[Beth]

Could I have each of you set the parent folder of your project to where your working folder is at? It has to be the same as what Visual Studio says the location is.

After setting the working folder, perform a Get with the option 'Do not overwrite/Merge later' selected.

Then try the actions with VS again.

[JohnWilk]

I am afraid I do not understand what you are asking. I am trying to add a solution so I do not see how I can have a working folder for a project that is not yet under source control.

However the problem has now gone away. I am not sure why. I have not done a Get as you suggested. I deleted in the client "trunk" and "branch" folders that I had previously added, created a folder for a new project and set the working directory. From then on there everything has worked OK. I can now add new projects from Visual Studio even without first creating folders in the client.

Is this a known bug? It does not give you a warm feeling when the first thing you do in an evaluation, i.e. adding a project, causes a crash!

[Beth]

I think there is one with VS 2003, but I haven't determined yet if that is what you ran up against or not. Some changes will be made for the next release. If you run into it again, send an email to support at sourcegear.com with a link to this thread.

[jeremy_sg]

We've discovered the cause of this bug. A fix will be included in 4.1.4. A workaround would be to log in to the repository using the Vault GUI client as the same Vault user before trying the operation in VS 2003 . If you would like a prerelease build of 4.1.4, please email support at sourcegear.com ATTN: jeremy with a link to this thread.