VS2005 hangs while refreshing vault status

[papacha]

We're using Vault 4.1.4 (18402) with Visual Studio 2005 SP1 on both XP SP3 and Vista SP1. The server and clients are on a high speed local network. The server is a quad 3.8Ghz Xeon server, 15K SCSI drives, 4GB and hardly any usage except for Vault. Clients are all dual 3.6Ghz Xeons with 4GB.

Every minute or two Visual Studio freezes with the following message in the lower left corner:

"Refreshing vault status..."

This often happens while navigating through code, highlighting code, or adding/editing code. It's extremely frustrating because it happens so often. I ran all the standard performance fixes on the server, defragged the drive, rebuilt the SQL indexes, etc.

How can I either (1) stop Vault from constantly refreshing, (2) make Vault refresh faster, or (3) keep VS from freezing while refreshing?

[lbauer]

In the Vault GUI client under Tools -> Options -> Network Settings, check the box "Request database delta on repository cache miss." Or, if it is already checked uncheck it.

Does that make a difference?

[DoggettCK]

I and my lead dev get the same problem, and the suggested change didn't fix it. Any other suggestions?

[lbauer]

We'll need to see some logging to determine what's going on.

Enable client-side logging
http://support.sourcegear.com/viewtopic.php?t=1534

I'll also want to see a copy of the Vault server log for the same time period. The Vault server log is sgvault.log and is in %windir%\temp\sgvault on the server machine.

Send them zipped up to support at sourcegear.com, Attn: Linda.

[ian_sg]

The original poster asked if they could change the frequency or turn off that refresh, and we never answered that. You can.

In Visual Studio, this option is under Tools|Options|Source Control|Vault Options|Advanced Options.

[DoggettCK]

Thanks, Ian. Worked perfectly.

[lbauer]

Thanks for the update.

[gswartwood]

Linda, do you still need logs?

I have the same issue (Visual Studio being non-responsive for minutes at a time then getting the 'refreshing Vault status') and it is a good temporary fix to turn off the auto-refresh. Alas, that is a fixing the symptom, not the cause. Why is the Visual Studio pausing for minutes at a time?

[ian_sg]

If it's not too big a pain to get us the logs, I'd love to see what's going on for people reporting this problem. If you don't want to attach them here, you can email them to ian at sourcegear dot com.

[papacha]

Logs have been submitted via e-mail to ian @ sourcegear dot com.

[ian_sg]

If you turn off the automatic refresh (clear the checkbox in the dialog shown earlier in this thread), does the delay go away?

(You need to log out/in for this to take effect. Restarting Visual Studio is the best way to make sure you've done that.)

[papacha]

Automatic refresh was already turned off.

[ian_sg]

Strange. What I see in the log is perpetual refreshes during the non-responsive periods you indicated. Each refresh takes roughly 1 second, but they're occurring one after another for periods that perfectly coincide with when you say VS was frozen.

I'm not sure why this would ever happen, much less when the automatic refresh is turned off completely. I'll have to investigate some.

It looks like your were debugging just before some of the non-responsive periods. I'll start there, in terms of reproducing the problem.

You also mentioned a SOAP error, but I don't see that in the logs. Do you have any more information about that? What did the dialog say?

[papacha]

The SoapException generated isn't really an error. It's a business rule validation that failed in our web service. That's how the web service notifies the client of certain errors. I've seen this behavior when other types of exceptions are thrown. I don't think it's web service specific.

Let me know if you need me to try anything else on our end.

[ian_sg]

I see. I'm actually seeing incredibly frequent refreshes throughout the log, even during periods you didn't say were nonresponsive.

To help me narrow the possibilities, would you try this? Turn the auto-refresh back on, but set the interval high, to something like 120 minutes (and restart VS). Does that make any difference?