Uncaught exception when merging branches

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

Moderator: SourceGear

Post Reply
Guest

Uncaught exception when merging branches

Post by Guest » Tue Feb 01, 2005 10:55 am

I received the following error when merging branches.

Reproduction steps:
1. started merge branches
2. selected origin and targets
3. selected exactly 2 history points in the source branch.
4. Pressed next.
5. Decided I didn't want the history points I had selected.
6. Pressed back
7. Selected a different starting history
8. Pressed Next
9. Exception.

>> Exception Text:

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 VaultClientOperationsLib.MergeBranchesOpList.Merge(VaultClientFolder targetFolder, VaultClientFolder originFolderBegin, VaultClientFolder originFolderEnd)
at VaultClientOperationsLib.ClientInstance.CalculateMergeOpList(VaultClientFolder targetFolder, VaultClientFolder originFolderBegin, VaultClientFolder originFolderEnd, MergeBranchesOpFilter filter)
at VaultClientPresentationLib.FormMergeBranchWizard.wizard1_AfterPageSelect(Object sender, EventArgs e)
at ActiproSoftware.Wizard.Wizard.ᐁ(EventArgs )
at ActiproSoftware.Wizard.Wizard.set_SelectedIndex(Int32 value)
at ActiproSoftware.Wizard.Wizard.ᐃ(WizardPageCancelEventArgs )
at ActiproSoftware.Wizard.Wizard.ᐍ(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.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.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultGUIClient
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultGUIClient.exe
----------------------------------------
VaultLib
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultLib.DLL
----------------------------------------
VaultPresentationLib
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultPresentationLib.DLL
----------------------------------------
VaultClientUILib
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultClientUILib.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
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
VaultClientOperationsLib
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultClientOperationsLib.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
----------------------------------------
VaultClientNetLib
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultClientNetLib.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.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
b8stfni_
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
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
----------------------------------------
VCDiff
Assembly Version: 2.0.6.2219
Win32 Version: 2.0.6.2219
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VCDiff.DLL
----------------------------------------
ActiproSoftware.Wizard
Assembly Version: 1.4.60.0
Win32 Version: 1.4.60.0
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/ActiproSoftware.Wizard.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.

ericsink
Posts: 346
Joined: Mon Dec 15, 2003 1:52 pm
Location: SourceGear
Contact:

Post by ericsink » Tue Feb 01, 2005 4:52 pm

This problem looks identical to one that was reported a couple days ago. I am already looking it, and I hope to confirm that it is indeed the same problem.

Thanks for the report.
Eric Sink
Software Craftsman
SourceGear

ericsink
Posts: 346
Joined: Mon Dec 15, 2003 1:52 pm
Location: SourceGear
Contact:

Post by ericsink » Wed Feb 02, 2005 11:07 am

Ooops -- I just realized you are using 2.0.x, not 3.0. Is that right?

If so, this is probably not the same problem as the one I was investigating.

Could you confirm exactly which version you are using?
Eric Sink
Software Craftsman
SourceGear

Post Reply