VS.NET 2003 freezes on second operation

mcjohso · Post by **mcjohso** » Tue Jun 29, 2004 1:42 pm

I've been having a problem with Vault lately that manifests itself in the following manner: I open Visual Studio, perform some Vault operation (i.e. check-out a file) which works fine. However when I perform a second operation, regardless of the amount of elapsed time, VS.Net freezes. Recently I left it in that state for an un-measured number of hours and a error dialog came up saying it was unable to connect to the repository. However when this occurs, I am able to open up the Vault client and connect to the repository and do any operations I choose. I am currently using 2.0.3 (2174) however I had this same problem with 2.0.2 (2163).

I should also mention that when I forcibly quit VS.Net, then load it back up again and perform a vault operation it works great, but on the second it freezes again, so I'm guessing the "can't connect" message is bs.

Any help is greatly appreciated.

dan · Post by **dan** » Tue Jun 29, 2004 8:34 pm

This will be a tough one to diagnose. Does the Output pane in VS having any useful info? Is it any second operation, or do you always invoke the same operation the same second time?

Also, I'm assuming the GUI client does not have this problem?

mcjohnso · Post by **mcjohnso** » Thu Jul 01, 2004 4:02 pm

It doesn't appear to be dependent on the operation I perform. The output pane shows nothing related to Vault. It simply freezes up. I recently reinstalled VS.Net 2003 and Vault and I still have the same problem.

dan · Post by **dan** » Fri Jul 02, 2004 7:16 am

Does this happen on all machines and users, or is it localized to a single user or single machine?

mcjohnso · Post by **mcjohnso** » Tue Jul 06, 2004 4:30 pm

I've only had it occur on one machine.

mikrogen · Post by **mikrogen** » Wed Jul 07, 2004 12:14 am

Hi, I am having this problem too (2174). I suppose it is related to VS .NET 2003.

Does SourceGear Client create any logs?

dan · Post by **dan** » Wed Jul 07, 2004 7:36 am

Unfortunately, the client doesn't have any logging in it. Send me email and I'll see if I can get a debug version of the IDE with some logging in it. Also, send me the output of Help->Technical Support from the Vault client too, and the version of Visual Studio.

Thanks

Chris Phillips · Post by **Chris Phillips** » Sat Jul 10, 2004 8:44 am

I've had this same problem. That second operation never seems to work. In the status pane of my VS it says "Checking in file...." or "Getting latest version..." There are no commands that don't make the thing freeze.

Both my client and the server are behind firewalls. Could this have anything to do with this problem? Are there any settings that need to be changed with my firewall or router?

dan · Post by **dan** » Sat Jul 10, 2004 3:55 pm

It is strange that it only happens in VS and only on the second operation. I can send you a debug output build of the Vault IDE component on Monday if you email me, and perhaps it will reveal something useful.

dan · Post by **dan** » Mon Jul 12, 2004 8:31 am

Actually, jeffc had a good suggestion on this. Is it possible that the connection to Vault is timing out, so that it isn't so much the second operation as it is an amount of time that is transpiring? Sometimes, the Vault login window comes up behind Visual Studio, and you have to Alt-Tab to get to it, but it make VS appear hung.

We see a lot more timeout problems when the Vault server is on Win2003 server, because it is very agressive by default in timing out and recycling IIS apps.

SourceGear Support

VS.NET 2003 freezes on second operation

VS.NET 2003 freezes on second operation

VS freezes