Error when trying to "Change Source Control"

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
stvyrayvhn
Posts: 11
Joined: Tue Nov 07, 2006 9:38 am

Error when trying to "Change Source Control"

Post by stvyrayvhn » Tue Dec 02, 2008 2:34 pm

I recently upgraded to Vault 4.0. I'm running Dell XPS M1730's with Vista (relax already, they work fine)... I have 3 different versions of Visual Studio on each of these machines, 2003, 2005, and 2008. My problem is with one machine that will not allow me to change the source control in Visual Studio 2003 so I can reconnect the bindings. Here's what I've done...
Installed the new Vault 4.0 client with all IDE's closed
Then enabled IDE integration found in the documentation under "Enable / Disable Integration"
To enable IDE Integration:

• Go to Tools on the Vault client menu bar. Select Options.

• Under General Options, check the Make Vault your default SCC provider.


Now after doing a lot of things including just blowing away the source directory on the users machine and getting a latest version. I am getting this error:

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.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.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.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
----------------------------------------
-dd_ohz5
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
----------------------------------------
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
----------------------------------------
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
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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 machine
rather than being handled by this dialog.


Any ideas what is going on?

-Larry

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Error when trying to "Change Source Control"

Post by lbauer » Tue Dec 02, 2008 4:26 pm

I could use info on why you are trying to change the bindings? Where was the solution previously bound?

If you are using VS 2003, you're using Classic Client integration, which is is the same type of integration as in earlier versions of Vault, so you don't need to unbind and rebind just because you've upgraded.

Have you tried backing up your working directories and doing a fresh Open from Source Control into empty working directories?
Linda Bauer
SourceGear
Technical Support Manager

stvyrayvhn
Posts: 11
Joined: Tue Nov 07, 2006 9:38 am

Re: Error when trying to "Change Source Control"

Post by stvyrayvhn » Mon Dec 08, 2008 2:20 pm

Because the bindings on this particular machine were not correct. So one of the many many things I did was delete the directory and got a refresh from the repository. Then for whatever reason I need to set the bindings. I can do this by changing the bindings but that's when I get that error.

-Larry

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Error when trying to "Change Source Control"

Post by lbauer » Tue Dec 09, 2008 3:16 pm

This sounds like a known integration bug in Vault 4.1.3. Upgrade client and server to the latest release, 4.1.4 and see if that takes care of the problem.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply