Connection lost during history dialog close

matt_stephens · Post by **matt_stephens** » Wed Mar 08, 2006 4:45 am

We're just evaluating vault having been sourceoffsite users for a while. So far it looks great but i just tried getting history from the client and then showed the Diff of a file. Having reviewed the differences for a while i closed the diff viewer and then closed the history dialog which hangs and eventually shows the following error message:

The Vault server could not be contacted to perform the operation. Your network connection to the server may have been interrupted. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.The underlying connection was closed: Could not establish secure channel for SSL/TLS.Unable to read data from the transport connection

Is this due to a session timeout on the server? Is there a way to keep sessions alive like there was in the SourceOffSite client?

If it makes any difference our server is set to use SSL and is running on Windows Server 2003 with latest patches.

Thanks

Matt

dan · Post by **dan** » Wed Mar 08, 2006 9:08 am

Yes, this fits the pattern of the session being timed out by IIS.

Windows 2003 is by default pretty aggressive in timing out IIS sessions. Check out this KB article to adjust those settings:

http://support.sourcegear.com/viewtopic.php?t=1014

If these don't help, you could try running it in IIS 5 isolation mode, and see if that helps.

matt_stephens · Post by **matt_stephens** » Wed Mar 08, 2006 9:41 am

Thanks, but what i don't understand is that the client works perfectly when left for a long time. It seems as though the history dialog is also happy to be left for a long time but not when it's been used to launch the diff viewer.

I am going to check this now, but i am pretty certain thats what i was seeing earlier.

When you say:

dan wrote:Yes, this fits the pattern of the session being timed out by IIS.

Does that mean you'd expect me to log on again, or does the client automatically do this for each operation? I am not getting asked for credentials except when i first launch the vault client.

Thanks

Matt

dan · Post by **dan** » Wed Mar 08, 2006 10:01 am

OK, from the description of the error message (which is a session ending/timeout message), I had assumed you just happened to get it while in History. If it *only* happens when diffing from history, that may be something different. After a true timeout, the login dialog would be displayed again.

Is this something that reliably happens when you diff from history?

Does it happen to everyone on your team (which would point to a server issue), or just you (which would point to a client issue)?

matt_stephens · Post by **matt_stephens** » Wed Mar 08, 2006 11:16 am

Maybe this was some sort of network problem. I saw the same thing a few times this morning, always from the history dialog and after spending some time in the diff viewer.
I've just tried repeating the same steps to clarify what was happening but it seems to be behaving itself properly now!

If i see the same issue again and find a way to reproduce it then i will let you know. So far though i have got to say we're very impressed with how well vault has imported a selection of our sourcesafe projects and how well it performs over a modest ADSL connection to our server.

Matt