Session Timing Out

CSkardon · Post by **CSkardon** » Thu Feb 08, 2007 3:35 am

Hi there,

I'm constantly getting a message from Vault telling me the session is timing out when I'm connected via the client or via VS2005.

I've tried the steps listed on this site, but to no avail, the message is still popping up every so often.

We can still work, but it's becoming very annoying.

Please help!!

Thanks

Chris

Beth · Post by **Beth** » Thu Feb 08, 2007 8:40 am

There are a number of things that could cause the timeout, so the kind of timeout needs to be identified.

Do you get an error message in your server log?

Can you open a Vault client, go to Help - Technical support and provide me the information that appears there?

CSkardon · Post by **CSkardon** » Thu Feb 08, 2007 8:49 am

Hi there,

Here is the info:

Client Information
Vault Client Version: 3.5.0.4741
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 3 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 3.5.0.4741
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

License Information
4 serial number(s):
1 of 4: 5 users, permanent
2 of 4: 5 users, permanent
3 of 4: 10 users, permanent
4 of 4: 1 users, permanent

I had to reconnect to it as the connection had timed out...

Beth · Post by **Beth** » Thu Feb 08, 2007 9:16 am

I'll still need you to check your server log, but the first thing I noticed it that your client and server are using different .NET frameworks. That can have an effect on the communication between the two, and I have seen some have timeouts from that.

I am attaching a document with instructions on how to change the .Net framework that Vault uses on the client.

CSkardon · Post by **CSkardon** » Thu Feb 08, 2007 9:25 am

Sorry - didn't read the server log bit for some reason!

Erm, yes, there is an error:

----05/02/2007 08:50:06 steve--xxx.com(IP)--SSL Disabled An error occurred during the deletion of 4nbwjw454s0q5kintquylg3g. Please check that the session was removed from the database.\tTransaction (Process ID 61) was deadlocked on {lock} resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
----05/02/2007 08:50:13 marta--xxx.com(IP)--SSL Disabled Login
----05/02/2007 08:51:07 sgvaultsystem--()--
System Started
Version 3.5.0.4741
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://xxxcom/VaultService
Identity = XXX\USER

There is an awful lot of: login/logout stuff...

Can I send the file or should I attach?

Beth · Post by **Beth** » Thu Feb 08, 2007 10:24 am

I think that error is pretty benign. You will want to go ahead and put your server logging into debug mode. That will provide more information beyond the login/logout things. That is done in the Admin tool on the Server Options tab.

Did you try my first suggestion?

CSkardon · Post by **CSkardon** » Thu Feb 08, 2007 11:15 am

Hi, Yes, I've tried the framework settings, and so far it's looking good, I'll see how it goes for the next 1/2 day or so.

I'll get Vault onto debug as well..

Thanks

Chris

CSkardon · Post by **CSkardon** » Wed Feb 14, 2007 10:24 am

Hi there,

I'm still getting the timeout message, a bit less frequently than previously, but still there.

The debug file attached contains a period where the timeout occurred, I can't see any errors...

Thanks

Chris

Beth · Post by **Beth** » Wed Feb 14, 2007 10:37 am

Next time it happens, can you send me a screenshot of the actual error?

Are you the only one with the timeout issue, or do any of the other clients timeout?

CSkardon · Post by **CSkardon** » Wed Feb 14, 2007 11:06 am

Hullo,

All clients timeout, pressing 'OK' on the attached dialog box just appears to relogin and away we go...

Chris

Beth · Post by **Beth** » Wed Feb 14, 2007 11:25 am

Check your Vault Server log, sgvault.log in %windir%\temp\sgvault. Are there frequent "System Started" entries?

If so, IIS may be recycling too often. See this KB article for details:

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

Also, what App Pool do you have configured for Vault?

CSkardon · Post by **CSkardon** » Fri Feb 16, 2007 4:30 am

OK, App Pool is: VaultAppPool ->

* all recycle options off,
* Performance -> Only 'Limit Kernal request queue' is selected (at 4000).

There do seem to be a lot of 'System Started' messages... about 22 a day... But the recycling seems to be off...

I've done everything in the KB article, but to no avail.

Thanks

Chris

Beth · Post by **Beth** » Fri Feb 16, 2007 9:23 am

There have been some users that found they could work in IIS5 instead of IIS6. They had timeout issues too. This KB article, http://support.sourcegear.com/viewtopic.php?p=8430, talks about that and what to do.

Give that a try and see if it works for you. If that does work, you can either continue working that way as a feasible work around or attempt to fix what caused you to need IIS5. So far I've narrowed it down to an App Pool issue.

If you want to look at the App Pool again first then, is the Vault Service in IIS set to use the Vault App Pool or the Default App Pool? You may try the opposite of what it's set to and see if that works for you. If that's the case then you will know there's some difference in settings that is making the difference and you can compare the two.

Let me know how these suggestions work for you.

CSkardon · Post by **CSkardon** » Fri Feb 16, 2007 11:12 am

Using IIS 5 isn't really a possibility, there are 2 other services running on the IIS, FogBugz and a CommunityServer instance, and one of these doesn't work on the IIS5 setting.

I will experiment with the App Pool settings and see where I can get to from there, and let you know how it goes.

Thanks!

Chris

Beth · Post by **Beth** » Fri Feb 16, 2007 11:46 am

If you send me an email at support at sourcegear.com, I'll send you screen shots of my app pool settings so you can compare. Please add Attn: Beth and a link to this thread so I get that to the right person.