vs.net 2003 constantly hanging with vault

ralphw · Post by **ralphw** » Wed Sep 01, 2004 3:25 am

I am getting IDE hangs when I use vault as my source control provider when:-

1. I type on a file which is checked in, and the IDE attempts to "auto-checkout".

2. when I "Get Latest Version" on a single file.

3. when I manually Check Out a single file.

I have used SOS for years and got IDE crashes/hangs only on the first scenario. I can live with a hang when I forget to check out before typing. But the other two I can't live with.

Is this a known fault? What is the workround.

I have a dual boot machine one partition running win2k pro (work), the other running winXP pro (play). I even installed my dev environment and vault on the XP partitition to see if it was OS related... but no joy.

I have a bandwidth throttling prog, and I can see that devenv.exe is not using any bandwidth when the hang occurs. It's doing nothing at all.

The MS bug report it auto sends when i kill the IDE from task manager after waiting 30minutes says "hungapp".

any ideas?

dan · Post by **dan** » Wed Sep 01, 2004 7:20 am

We get reports like this every now and then, but have never been able to reproduce it in-house. Obviously we would love to track this down and fix it, but no joy on our end yet either.

Sometimes it seems related to the server timing out and a login dialog either coming up behind the app, or not coming up at all. You might check the Vault server log and see if the session is being ended or if the server is restarting.

Also, is there anything in the VS.Net messages pane that indicates it tried to something that failed?

And one last question: Does this happens to others on your team/network? That might help in determining whether it happens with a particular network configuraiton, or a machine configuration.

Guest · Post by **Guest** » Wed Sep 01, 2004 10:20 am

Hi.

I work on the same team as ralphw. So far the other two of us on the team using Vault, one of whom works remotely and one over an intranet, have not had similar problems.

We are currently evaluating Vault and have been impressed with the functionality and speed. We'd really like to continue using it, however, if we can't sort this problem out then we have no choice but to go back to VSS.

Please let me know if I can provide any more information. Just a shot in the dark but could the problem be firewall related?

dan · Post by **dan** » Wed Sep 01, 2004 10:38 am

If the machine that hangs uses a firewall (and the other two don't) or there is some difference in the network path, then that would be a good clue. Is that the case?

Another question is whether the problem is limited to the VS.Net interface, or whether the standalone GUI client also has the same problem.

ralphw · Post by **ralphw** » Wed Sep 01, 2004 2:54 pm

my machine used a firewall on xp pro. First with WinXp SP1 then with the new firewall on winxp sp2.

my Win2k partition has NAV2004 installed, but i switched off all security settings.

the vault client works fine. It's just that vault integration crashes - or forces a complete hang of VS .Net 2003.

When I say a hang I mean I cannot "click" or set focus on any control within the IDE.

I have lost track of the crashes I have endured in 1.5 days coding. I am on the verge of giving up on vault entirely. which is a shame because it looks great in principle. If it worked....

Network wise we are both using ADSL 512 links with fixed IP's albeit with different providers from locations 200 miles apart (I am in the same city as the vault server).

ralphw · Post by **ralphw** » Wed Sep 01, 2004 3:02 pm

we checked the log and there is no sign of server restarts - there do not seem to be login timeouts relating to the crashes.

The VS.net message pane just says "checking out file(s)" or something as simple as that.

There is no login dialog coming up "behind the app". I am using profiles generally so i don't need to continually log in.

I will send in a copy of the log, but i will wipe our IP's if that is OK.

dan · Post by **dan** » Thu Sep 02, 2004 7:53 am

Hmmm. I would suspect the problem is manifested either by the network (perhaps it is intermittently losing the connection, which VS can't recover from), or it is machine config related.

Send me email and perhaps I can send out a build that logs calls into the IDE, which may give more info on where the problem is manifesting itself.

In the meantime, you could unbind the solution to stop the hang, and use the standalone client for SCC operations.