Frequent lockups: Steps to reproduce

[dfrankson]

I figured it out steps to reproduce on my machine. Sourcegear 3.1.6 + .NET 2.0

1.) Open the SourceGear client and log into a repository.
2.) Lock your workstation by hitting CTRL-Alt-Delete then Lock Computer.
3.) Unlock the computer
4.) The SourceGear client is in an unresponsive state.

[dfrankson]

Two of our workstations exhibit this behavior, others don't. We will work to identify the common factor.

[lbauer]

Are the affected clients using the .NET Framework 2.0? Note that even if 2.0 is installed, the client may be using the 1.1 Framework. Check Help->Technical Support in the GUI Client for Framework and other info to help you compare.

[dfrankson]

The two machines that are locking up are both running .NET 2.0


Client Information
Vault Client Version: 3.1.6.3658
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Vault Server Version: 3.1.6.3658
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

[lbauer]

I was not able to reproduce this on my XP machine, which has nearly identical configuration in the Vault Client Help->Technical Support.

The only time the client appeared to hang was when I had restarted the Vault Server, but then I got a "session ended" dialog.

Dan's suggestions in your other post would be the next thing to try.
http://support.sourcegear.com/viewtopic.php?p=21812

Also, continue to compare the machines that work properly with those that don't to determine the differences.

[dfrankson]

Of all the developer workstations, the only two running .NET 2.0 are the ones getting lockups. The others are running 1.1 without problems.

The other developer uninstalled 2.0 and installed 1.1 and hasn't been able to get it to lock up. I am running SQL 2005 and can't uninstall 2.0. I will turn on logging and see if I can get any more information.