Client Hangs
Moderator: SourceGear
Client Hangs
After opening the client and executing a few gets/checkout/checkin operations, two or three, upon issuing the next one, the client hangs.
At the status bar it reports "Retrieving repository structure information from the server...", and windows task manager reports it as running.
If I kill the process and re-open it, it will work again for a few operations and hang again. It's not a timeout issue, I've tried waiting for several hours to no avail.
Please, any help is appreciated
At the status bar it reports "Retrieving repository structure information from the server...", and windows task manager reports it as running.
If I kill the process and re-open it, it will work again for a few operations and hang again. It's not a timeout issue, I've tried waiting for several hours to no avail.
Please, any help is appreciated
Further Info
I forgot to mention I'm using 3.1.0.3476. I upgraded to this version thinking the problem would go away.
Over team members are not experiencing this problem
Over team members are not experiencing this problem
I never like to blame-shift away from a potential problem with our software, but this just smells like a problem with your machine. Can you rule that out somehow? Any errors in Event Viewer? Is your hard disk okay? Stuff like that.
Another possible scenario is that Vault's client side cache files got hosed somehow, but if that were the case, it doesn't seem like the problem would be behaving the way you described, failing after 2-3 ops.
Another possible scenario is that Vault's client side cache files got hosed somehow, but if that were the case, it doesn't seem like the problem would be behaving the way you described, failing after 2-3 ops.
Eric Sink
Software Craftsman
SourceGear
Software Craftsman
SourceGear
I've upgraded to 3.1.1.3506 and I still see the same problem. Now I have other team members seeing the same problem, and I can't find anything wrong in the Event Viewer or anywhere else.
The interesting thing is, it works fine from VS.2005. It only has a problem when I'm using it from VS.2003 or stand alone.
The interesting thing is, it works fine from VS.2005. It only has a problem when I'm using it from VS.2003 or stand alone.
Let's do some additional troubleshooting.
Are other users experiencing the hang when using the same projects in the GUI client or in VS.NET 2003? Or does the hang seem more related to the number of operations or a period of time, rather than a particular project?
I'd like to see the info from your Vault GUI Client->Help->Technical Support.
Also, enable client-side logging:
http://support.sourcegear.com/viewtopic.php?t=1534
Log all classes.
Set Vault server logging to debug. (Admin Tool->Server Options->Logging.)
Reproduce the hang, then send or post the client log and server log. I'll need to know if the times in the client log correspond to the server log.
Are other users experiencing the hang when using the same projects in the GUI client or in VS.NET 2003? Or does the hang seem more related to the number of operations or a period of time, rather than a particular project?
I'd like to see the info from your Vault GUI Client->Help->Technical Support.
Also, enable client-side logging:
http://support.sourcegear.com/viewtopic.php?t=1534
Log all classes.
Set Vault server logging to debug. (Admin Tool->Server Options->Logging.)
Reproduce the hang, then send or post the client log and server log. I'll need to know if the times in the client log correspond to the server log.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Here is the info from the technical support window:
Client Information
Vault Client Version: 3.1.1.3506
.Net Framework Version: 1.1.4322.573
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1023.21 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.1.1.3506
.Net Framework Version: 2.0.50215.44
Operating System: Microsoft(R) Windows(R) Server 2003, Standard 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.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
License Information
1 serial number(s):
1 of 1: 5 users, permanent
Client Information
Vault Client Version: 3.1.1.3506
.Net Framework Version: 1.1.4322.573
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1023.21 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.1.1.3506
.Net Framework Version: 2.0.50215.44
Operating System: Microsoft(R) Windows(R) Server 2003, Standard 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.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
License Information
1 serial number(s):
1 of 1: 5 users, permanent
Here is the log file. I got it after I had to kill the process, half an hour after it hung
- Attachments
-
- VaultGUIClient.zip
- zipped log file
- (11.43 KiB) Downloaded 748 times
The log file doesn't show anything obvious, but there are a few questions we can ask based on it:
1. Is the E drive local or remote, and do you have access to it during the time the Vault client is running?
2. Is the status search pane always up when this happens? Does it hang if you switch to the pending change set or messages pane? (Just trying to figure out if it is related to background status searching)
3. If you rename your vault cache folder (say, rename %appdata%\SourceGear\Vault_1\Client to Client_Save) and then reinvoke the client, do you still have the same problem? This will cause you to lose all your client state, but would determine whether something in the cache is causing the problem. You need to exit the client before doing this, and if it doesn't help, you would want to rename it back after exiting and re-entering the client.
1. Is the E drive local or remote, and do you have access to it during the time the Vault client is running?
2. Is the status search pane always up when this happens? Does it hang if you switch to the pending change set or messages pane? (Just trying to figure out if it is related to background status searching)
3. If you rename your vault cache folder (say, rename %appdata%\SourceGear\Vault_1\Client to Client_Save) and then reinvoke the client, do you still have the same problem? This will cause you to lose all your client state, but would determine whether something in the cache is causing the problem. You need to exit the client before doing this, and if it doesn't help, you would want to rename it back after exiting and re-entering the client.
It's possible it could be server, if other users would see the same thing.
Check the server log, usually in the %windir%/temp/sgvault folder. If there is no "error" or "fail" string in it, put the server log in debug mode (via the admin tool), and try it again and send us the server results during the time the hang is happening.
Check the server log, usually in the %windir%/temp/sgvault folder. If there is no "error" or "fail" string in it, put the server log in debug mode (via the admin tool), and try it again and send us the server results during the time the hang is happening.
I don't really have any additional information to add, but one of the Vault users here just told me about symtoms she's having that sound exactly like this. She's the only one I've heard anything like this from out of the 40+ people we have using Vault. We're currently using 3.0.7 and I think her client is up-to-date.
I'm probably going to update our Vault server to 3.1.1 tonight, and I was going to clear out her Vault cache files before she updates her client (I'll probably do an uninstall/reinstall of the client also).
Mike
I'm probably going to update our Vault server to 3.1.1 tonight, and I was going to clear out her Vault cache files before she updates her client (I'll probably do an uninstall/reinstall of the client also).
Mike
Here's the info from her Help->Tech Support window.
Client Information
Vault Client Version: 3.0.7.2863
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 509.98 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.0.7.2863
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft(R) Windows(R) Server 2003, Standard 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.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
License Information
4 serial number(s):
1 of 4: 5 users, permanent
2 of 4: 10 users, permanent
3 of 4: 25 users, permanent
4 of 4: 10 users, permanent
Mike
Client Information
Vault Client Version: 3.0.7.2863
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 509.98 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.0.7.2863
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft(R) Windows(R) Server 2003, Standard 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.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
License Information
4 serial number(s):
1 of 4: 5 users, permanent
2 of 4: 10 users, permanent
3 of 4: 25 users, permanent
4 of 4: 10 users, permanent
Mike