Sourcegear 2.01 Client Crash after running overnight

[tstanley]

I am currently evaluation Sourcegear for purchase.

After running the Sourcegear 2.01 client on a workstation and leaving it running overnight, when attempting to use it in the morning, it crashes with an object is currently in use elsewhere error.

This happens in both the standalone Vault client GUI and the VS 6 IDE. When run within the VS IDE, it causes users to loose data (not a good thing ).

I have looked at how to stop W2K3 from restarting the IIS process each night, but I can not find a setting for that. Regardless, my thoughts are the Vault client should recover from this scenario more gracefully.

Could you please advise on what might be the issue?

Attempts were made for the recommended fixes on the client in the post for Object reference not set to an instance of an object, but the same problem occurs. See:
http://support.sourcegear.com/viewtopic.php?t=643

Each day, the server log files show the following entry:
----4/28/2004 5:58:38 AM sgvaultsystem--()--
System Started
Version 2.0.1.2137
Cache Level = 1
DataBase Buffer Size = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp

The server vault session timeout is: 4320 (the default).


See further client / server confiugration posted at the bottom of this text.

Error Details:
Error text: The object is in use elsewhere.

Error details:


************* Exception Text **************
System.InvalidOperationException: The object is currently in use elsewhere.
at System.Drawing.Graphics.Dispose(Boolean disposing)
at System.Drawing.Graphics.Dispose()
at System.Windows.Forms.PaintEventArgs.Dispose(Boolean disposing)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.GroupBox.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.573
CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultPresentationLib
Assembly Version: 2.0.1.2137
Win32 Version: 2.0.1.2137
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultPresentationLib.DLL
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
VaultClientOperationsLib
Assembly Version: 2.0.1.2137
Win32 Version: 2.0.1.2137
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultClientOperationsLib.DLL
----------------------------------------
VaultClientNetLib
Assembly Version: 2.0.1.2137
Win32 Version: 2.0.1.2137
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultClientNetLib.DLL
----------------------------------------
VaultClientUILib
Assembly Version: 2.0.1.2137
Win32 Version: 2.0.1.2137
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultClientUILib.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/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.573
CodeBase: file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
VaultLib
Assembly Version: 2.0.1.2137
Win32 Version: 2.0.1.2137
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VaultLib.DLL
----------------------------------------
System.Web.Services
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/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.573
CodeBase: file:///c:/winnt/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
qg7xhgvr
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll
----------------------------------------
VCDiff
Assembly Version: 2.0.1.2137
Win32 Version: 2.0.1.2137
CodeBase: file:///C:/Program%20Files/SourceGear/Vault%20Client/VCDiff.DLL
----------------------------------------

Client Configuration:

Client Information
Vault Client Version: 2.0.1.2137
Operating System: Microsoft Windows 2000 Professional
Service Pack: 4.0
OS Version: 5.0.2195
Total Physical Memory: 511.3 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Vault Server Version: 2.0.1.2137
Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Service Pack: 0.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: )

License Information
License ID: 0
Customer ID: 0
Number of Licenses: 10
License Type: Demo
Creation Date: 3/17/2004
Activated: N

License ID: 0
Customer ID: 0
Number of Licenses: 10
License Type: Demo
Creation Date: 4/13/2004
Activated: N

[sterwill]

I don't think I've ever seen an "object is currently in use elsewhere" message from Vault. Is it possibly an "object reference not set to an instance of an object" message instead?

[tstanley]

It may be an underlying exception being thrown, not an explicit one.

The post we had showing:
************* Exception Text **************
System.InvalidOperationException: The object is currently in use elsewhere.

was really just an exact copy of the exception dump. So to anwer your question, not I don't hink it was a message for "object reference not set to an instance of an object".
===
tstanley

[sterwill]

Could you tell me a little more about how the error happened? When you came back to Vault, was the error message already there? Or did you do an operation (like a refresh, or a get latest version) before the message popped up? Would it be possible to attach a screenshot of the error to this thread?

[tstanley]

After letting the Vault client run overnight. It seems like it's fine (i.e. no visible error yet).

Operations like:
Coming in and right clicking to get properties
Performing a refresh
Doing a get, or trying to check in a file all make things appear to
go into a wait mode (hourglass appears), followed by time passing, then the error appears.

I can send a screenshot Monday.

[Guest]

I upgraded to the server and client version 2.02 and this problem no longer occurs on at least one machine. This was listed in the V 2.02 fixes.

When letting the client run overnight and then attempting a client operation it correctly states that the session has timed out and prompts for a new login. This is different behavior than the V2.01 which threw the object is currently in use error.

If the problem occurs again in 2.02, I will post more information for a screenshot and a recreation scenario.