Hi,
I have upgraded to Vault 3.0.5 from 3.0.1, when I start the client (and Admin I think) I get a .Net exception being thrown:
'An unhandled exception ('System.ArithmeticException') occurred in VaultGUIClient.exe [3148].
This was happening with 3.0.1 and now 3.0.5 - I tried uninstalling and re-installing but with the same problem. I have got Visual Studio 2005 and 2003 installed on this machine, but I have got this setup on another machine that works fine.
Any ideas how to solve it, the integration with Visual Studio works, in that I can check things in and out, but it would be nice to have the client working as well.
Thanks in advance,
Rupert.
Vault Client 3.0.5 Exception
Moderator: SourceGear
I have .Net Framework installed on both machines, it works OK on one and not on the other, which is the strange thing.
This is what I get in a dialog box when I run the admin tool:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArithmeticException: Overflow or underflow in the arithmetic operation.
at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
at System.Drawing.Font..ctor(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
at System.Windows.Forms.ControlPaint.FontInPoints(Font font)
at System.Windows.Forms.Control.get_DefaultFont()
at System.Windows.Forms.Control.get_Font()
at System.Windows.Forms.Form.ApplyAutoScaling()
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.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultAdmin
Assembly Version: 3.0.5.2833
Win32 Version: 3.0.5.2833
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultAdmin.exe
----------------------------------------
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
----------------------------------------
VaultPresentationLib
Assembly Version: 3.0.5.2833
Win32 Version: 3.0.5.2833
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultPresentationLib.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
----------------------------------------
VaultLib
Assembly Version: 3.0.5.2833
Win32 Version: 3.0.5.2833
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultLib.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.
There is no mention of any .Net Framework 2 assemblies being called here though...
This is what I get in a dialog box when I run the admin tool:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArithmeticException: Overflow or underflow in the arithmetic operation.
at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
at System.Drawing.Font..ctor(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
at System.Windows.Forms.ControlPaint.FontInPoints(Font font)
at System.Windows.Forms.Control.get_DefaultFont()
at System.Windows.Forms.Control.get_Font()
at System.Windows.Forms.Form.ApplyAutoScaling()
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.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultAdmin
Assembly Version: 3.0.5.2833
Win32 Version: 3.0.5.2833
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultAdmin.exe
----------------------------------------
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
----------------------------------------
VaultPresentationLib
Assembly Version: 3.0.5.2833
Win32 Version: 3.0.5.2833
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultPresentationLib.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
----------------------------------------
VaultLib
Assembly Version: 3.0.5.2833
Win32 Version: 3.0.5.2833
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultLib.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.
There is no mention of any .Net Framework 2 assemblies being called here though...
Try adding this to our VaultGUIClient.exe.config file, within the <configuration> element:
<startup>
<requiredRuntime version="v1.1.4322">
</startup>
This will ensure that all assemblies that get loaded are the 1.1 version of the framework. It may already be doing this, but we'll see...
Also, verify that the 1.1 framework files in Windows\Microsoft.Net look like they haven't been deleted. (Sometimes updating the framework will wipe out the previous version).
Dan
<startup>
<requiredRuntime version="v1.1.4322">
</startup>
This will ensure that all assemblies that get loaded are the 1.1 version of the framework. It may already be doing this, but we'll see...
Also, verify that the 1.1 framework files in Windows\Microsoft.Net look like they haven't been deleted. (Sometimes updating the framework will wipe out the previous version).
Dan
Dan
I tried adding the startup bit into the configuration section but the client wouldn't start at all, complained about the "application configuration being incorrect". Below is part of the config file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<requiredRuntime version="v1.1.4322">
</startup>
<system.net>
<defaultProxy>
...
</appSettings>
</configuration>
Does this look correct?
I tried adding the startup bit into the configuration section but the client wouldn't start at all, complained about the "application configuration being incorrect". Below is part of the config file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<requiredRuntime version="v1.1.4322">
</startup>
<system.net>
<defaultProxy>
...
</appSettings>
</configuration>
Does this look correct?