New problem behaviors since upgrade to 5.1.2 19281

[greenstone]

Hi,

We recently upgraded to Vault Standard 5.1.2 19281. We were at a prior version 5.x of Vault.

A couple of issues:

1.) We have "Concurrent Development Style" set to Edit/Merge/Commit (CVS Style), and all checkboxes on this page unchecked.

Almost all the developers have noticed that, when they change one of the source-controled files (in a text editor), that it does not display in the bottom window for some time. By some time, maybe 20 minutes or so. Then it shows up in the list as Type = "Modified".

Thoughts on what might be the issue?


2.) When we first installed 5.1.2 19281, it never asked us to reauthenticate (like in the morning after being idle all night). The prior version would always ask to authenticate. In the past few days (I don't believe any configuration has changed on the server), it now asks to authenticate each day (seems correct). But also one developer reports it's asking him to authenticate several times a day.

Thoughts?

Regards,

Andy

[Beth]

1) After the change, are they saving the file? If they save the file, does the change show up more quickly?

Go to Vault Tools - Options and check what your refresh rate is. If it's set to 20 minutes, set it to a lower number.

2) Vault typically has a timeout that make just leaving the client open over night and continuing the next day not feasible. The connection should time out and require another login.

For the developer that has to authenticate several times a day, is he/she reopening the Vault client or is it already open and saying that a reauthentication is needed? If an error is given, can you look in their Vault client log found at %temp%\vaultguiclient.txt for their error and post it?

[greenstone]

Hi Beth,

Regarding question 1.) Yes, we save the file (and it shows up very slowly-20 minutes or so). We use the stand-alone SourceGear Vault Standard client--and it only shows up after the file is saved. I'm speculating you're asking the "does it show up if not saved" question with regard to the integrated Visual Studio client?

[Beth]

If you weren't saving, then I would assume that an auto-save or something of that nature would kick off the shadow update.

Is the shadow folder on the same machine or a different machine than the Vault server? Is it on the same network?

I would like to see some debug level logging for the Vault server, I'd like to see the Vault shadow folder log with it (also under%windir%\temp).

Server level logging:
1) Go to %windir%\temp\sgvault and rename the log sgvault.log. This will force Vault to create a new one that will just cover the information that's needed.
2) Open the Vault admin web page and click on the logging link.
3) Change the logging level from Quiet to Debug.
4) Change the archive level from weekly to daily.
5) Click Save. All users will be disconnected and need to login again.

Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and the log files?