I have a problem where on one of my machines, the Vault Client AND Visual Studio add-in will lock up (the client application and Visual Studio itself) while trying to retrieve repository information after a period of inactivity ranging from 5-15 minutes. The client will start the "retrieve repository information" process and never return, leaving the current instance of the application unusable in a way that it must be forcibly shut down.
This only happens on one machine, but it is my main development machine. It has a completely new installation of software, including Visual Studio 2003, Visual Studio 2005 Beta 2, Windows XP SP2, Vault Client 3.0.7 (I upgraded from 2.0.6 hoping to fix the problem), Office 2003, Xheo Licensing, Mozilla Thunderbird, FireFox, Internet Download Manager, Microsoft Anti-Spyware Beta, and Norton AntiVirus 2005.
Does anyone have any clue about what the problem might be and how to fix it? This forces me to have to shut down Visual Studio every 10 minutes or so in order to work...
Vault Client and VS Add-In Lock Up on XP SP2
Moderator: SourceGear
Vault Client and VS Add-In Lock Up on XP SP2
Travis J. James
President/CTO
Butterfly Software Group
President/CTO
Butterfly Software Group
We've not had other reports of this. Is VS 2005 running at the same time? Since they use different .Net frameworks, I wonder if something could be colliding.
I would suggest turning on client side logging - it might reveal more info about what is getting hung up. See http://support.sourcegear.com/viewtopic.php?p=7806 for how to do that. To reduce the size of the log file, you might want to only log the "refresh" class to start with.
I would suggest turning on client side logging - it might reveal more info about what is getting hung up. See http://support.sourcegear.com/viewtopic.php?p=7806 for how to do that. To reduce the size of the log file, you might want to only log the "refresh" class to start with.