Session timeout

[Pierre Cogne]

Hi,
we are using Vault Standard 5.1.2.19281 with Visual Studio Pro 2010

Under VS2010 we use the SourceGear Vault Standard Visual Studio Enhanced Client.

Since we've been using this enhanced client plugin, all our developers started to complain they were losing their session to the vault to quickly with no easy way to reconnect but to close and restart Visual Studio. (Sometimes doing File->Vault Source COntrol -> Refresh status might work but still painfull and not working all the time, options might even be grayed out)

Even worse, they can edit the files just fine but get an error message when trying to save it saying the file is read-only and cannot be checked out.

Anyway to work this out?

Thanks

Pierre Cogné

[Beth]

How long does it take from the time a person starts working until they get a timeout?

Is Visual Studio or Vault left open overnight?

In the Vault Tools - Options - General, do your users have automatic refresh turned on? If so, how often is it set to refresh?

On the Vault Admin Web page under Advanced Settings, what is your session timeout?

[Pierre Cogne]

Thank you for your quick answer.

How long does it take from the time a person starts working until they get a timeout?

Hard to give a pattern as we don't notice when a file is already checked out. We notice it only when we try to check out a new file (or checkin, getlatest,...).
The feedback is 2 to 5 times a day

Is Visual Studio or Vault left open overnight?

Yes, but it happens also during the day, not only the morning. I already saw VisualStudio getting disconnected after 1-2 hour

In the Vault Tools - Options - General, do your users have automatic refresh turned on? If so, how often is it set to refresh?

Yes, automatic refresh is turned on for everybody, except for one developer who is annoyed with VisualStudio hanging while its refreshing)
We are all set to refresh every 10minutes

On the Vault Admin Web page under Advanced Settings, what is your session timeout?

Session Timeout = 10080 minutes


Regarding VS hanging while refreshing, I noticed that as well, and it is true that's annoying. Isn't there any way to setup something to stop VS hanging?

[Beth]

Can you have your users not leave Visual Studio nor Vault open overnight for a while until this is resolved?

Is the .sln file bound? To check that, go to File - Vault Source Control - Change Bindings.

Is the .sln file added to Vault?

Can you post a screenshot of the settings you have in the Visual Studio Tools - Options - Source Control - Integration Options?