After upgrade to 1.1, sessions expiring early
Moderator: SourceGear
After upgrade to 1.1, sessions expiring early
We recently upgraded Fortress Server to 1.1, and even though we have the session timeout set to 7,200 minutes (5 days), several users are experiencing timeouts daily.
Has anyone else experienced this, and/or is this a known issue with a known fix?
Has anyone else experienced this, and/or is this a known issue with a known fix?
We've had a few reports of this, and we think it might be an issue with the .Net framework.
Before we go further, we'd like to know what the exact client-side error is,
and we'd also like to take a look at your server log. The server log is sgvault.log, located in the %windir%\temp\sgvault directory.
You can attach a copy here, e-mail support at SourceGear.com, ATTN: Linda
Before we go further, we'd like to know what the exact client-side error is,
and we'd also like to take a look at your server log. The server log is sgvault.log, located in the %windir%\temp\sgvault directory.
You can attach a copy here, e-mail support at SourceGear.com, ATTN: Linda
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Just a quick update, on the chance it was the apppool recycling; we increased the time period there. I just got another of the same invalid session message less than 6 hours after the last recycle.
Another thing to note, all we have running on this server is Fortress and SQL Server 2005. So we are more than willing to tweak whatever needs to be tweaked or you think needs to be tweaked to try to fix this.
Another thing to note, all we have running on this server is Fortress and SQL Server 2005. So we are more than willing to tweak whatever needs to be tweaked or you think needs to be tweaked to try to fix this.