Hello,
I have a problem with the Vault 3.1.9 client.
It frequently is frozen after resuming from standby on my laptop (Windows XP, connected by wireless network). I have noticed this several times this week, all occured when I had a single file checked out and was looking at the "pending changes" pane.
I am just reporting this as something you might want to look into for a future release.
Your product is great all-around.
Freeze after resume from standby
Moderator: SourceGear
I just need a little more information.
Does this occur on any other system or only your system? Are you connecting to your network remotely? Are you using Vault alone or integrated with either Visual Studio or Dreamweaver? Is either the client or server a 64-bit system?
Could you set up your Client Side Logging and send the log after this happens again?
Does this occur on any other system or only your system? Are you connecting to your network remotely? Are you using Vault alone or integrated with either Visual Studio or Dreamweaver? Is either the client or server a 64-bit system?
Could you set up your Client Side Logging and send the log after this happens again?
Beth,
Sure.
It may well occur on other systems, but I don't have any other similar configurations to test it on, so I don't know. Sorry.
I am connecting to my vault server over the internet. I am connected to a local wireless network, and from there to a router/NAT, and from there to the internet, and then there is another router/NAT on the server's side. I am not using a VPN if that is your question. Network connectivity and vault in general seem to work fine when vault is started (I can perform all the normal operations, and their results persist), but it hangs when resuming from standby.
Neither client or server is a 64-bit system.
I will set up the logging now.
Thanks.
Sure.
It may well occur on other systems, but I don't have any other similar configurations to test it on, so I don't know. Sorry.
I am connecting to my vault server over the internet. I am connected to a local wireless network, and from there to a router/NAT, and from there to the internet, and then there is another router/NAT on the server's side. I am not using a VPN if that is your question. Network connectivity and vault in general seem to work fine when vault is started (I can perform all the normal operations, and their results persist), but it hangs when resuming from standby.
Neither client or server is a 64-bit system.
I will set up the logging now.
Thanks.
Are there any other applications this happens with? I've only heard of this kind of behavior once before with the Virtual Desktop Manager from Microsoft, and that tool we don't support (Microsoft doesn't even support it). I have several versions of Vault always sitting in a stand-by state in a couple VMWare virtual machines, and I've never had one hang there no matter how long I ignore them. Did you want to send me a client log right after a hang? Just read about Client Side Logging to set that up.
No, it doesn't happen with any of my other applications.
I've never heard of the Virtual Desktop Manager, so I can't speak to that.
As far as the virtual machine goes, I wonder if the wireless networking is an important component of the problem? Maybe the client initiates some kind of network operation before the wireless connection has been reconnected after resume-from-standby, or something along those lines?
I will send you the logs later this afternoon, unfortunately I am away from my laptop computer on travel at the moment.
Thanks.
I've never heard of the Virtual Desktop Manager, so I can't speak to that.
As far as the virtual machine goes, I wonder if the wireless networking is an important component of the problem? Maybe the client initiates some kind of network operation before the wireless connection has been reconnected after resume-from-standby, or something along those lines?
I will send you the logs later this afternoon, unfortunately I am away from my laptop computer on travel at the moment.
Thanks.
Trace and repro steps
Sourcegear,
Attached is a trace.
Here are my repro steps (which appear to be consistent, but may not be minimal because I didn't have time to try too too many variations):
0. Find a computer with Windows XP, Vault 3.1.9 Client, and a wireless netwok connection. (I also have the Vault Admin Tool installed on this computer, but it was not running.)
1. Open vault client (and autoconnect through saved profile)
2. Take an (exclusive) checkout
3. Edit the checked out file using the system default editor (in my case, Open Office Writer)
4. Edit the file in some way and save
5. Leave the editing program window active and maximized
6. Place the computer in standby mode
7. Resume from standby
8. Do not dismiss the wireless network reconnection message popup from the system tray
9. Click on the Vault Client in the taskbar
10. Observe that the Vault Client is not painting or responding to mouse input.
Attached is a trace.
Here are my repro steps (which appear to be consistent, but may not be minimal because I didn't have time to try too too many variations):
0. Find a computer with Windows XP, Vault 3.1.9 Client, and a wireless netwok connection. (I also have the Vault Admin Tool installed on this computer, but it was not running.)
1. Open vault client (and autoconnect through saved profile)
2. Take an (exclusive) checkout
3. Edit the checked out file using the system default editor (in my case, Open Office Writer)
4. Edit the file in some way and save
5. Leave the editing program window active and maximized
6. Place the computer in standby mode
7. Resume from standby
8. Do not dismiss the wireless network reconnection message popup from the system tray
9. Click on the Vault Client in the taskbar
10. Observe that the Vault Client is not painting or responding to mouse input.
- Attachments
-
- VaultGUIClient.txt
- Trace
- (16.79 KiB) Downloaded 193 times
After speaking with a colleague, it seems that Vault 3.1.9 can have an issue with redrawing when used with .NET 2.0. This has been fixed in Vault 3.5, but that is a paid upgrade. You can contact our store at sgstore at sourcegear.com for more information on that.
The other option is to change which .NET framework Vault uses. To register the .NET 1.1 Framework, type the following command at a command prompt, then press ENTER:
"\<Windows folder>\Microsoft.NET\Framework\<Version Number>\aspnet_regiis.exe" -i
NOTE:Replace <Windows folder> with the name of the directory where the operating system is installed and replace <Version Number> with the .NET Framework version installed on your computer.
The other option is to change which .NET framework Vault uses. To register the .NET 1.1 Framework, type the following command at a command prompt, then press ENTER:
"\<Windows folder>\Microsoft.NET\Framework\<Version Number>\aspnet_regiis.exe" -i
NOTE:Replace <Windows folder> with the name of the directory where the operating system is installed and replace <Version Number> with the .NET Framework version installed on your computer.