Hi,
We've been working with Vault since November last year, when we tried to address this issue in it's infant form. It's since grown up. We were initially only receiving the "Session is no longer valid. Either the server restarted" etc when we were first setting up a vault client for the first time on a client machine. We were able to remedy this (after trying all the other suggested measures, including the ones for earlier versions of Vault) by stopping and starting the Application Pool in which Vault lived.
Unfortunately, the issue has grown worse and it now happens regularly multiple times throughout the day to multiple users. Sometimes the error is resolved by simply re-connecting. Other times, however, the message would get thrown immediately, and forever after each attempt, until the afore mention app pool restart was carried out.
Now, the only fix suggested on these forums that we haven't tried, is to run IIS in IIS 5 Isolation mode. We cannot do this due to the other sites running on the server.
I have included below as a starting point the client/server info, as you can see, I've even tried one of the latest suggestions to run both in version 2.0 of the framework. I am basically hoping for some progress or something new to try in relation to this problem. Thank you for your time.
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT+10:00) Canberra, Melbourne, Sydney
Server Information
Vault Server Version: 3.5.1.4786
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT+10:00) Canberra, Melbourne, Sydney
SQL Version: Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Apparent Session Timeouts - But I've tried all the tips!
Moderator: SourceGear
-
- Posts: 1
- Joined: Tue Apr 03, 2007 12:12 am
We'd like to see another copy of your Vault Server log. Put the log in debug mode in the Vault Admin Tool, under Server Options->Logging. After a few restarts, send us a copy of the sgvault.log file from %windir%\temp\sgvault on the Vault Server machine. Email it to Linda at SourceGear.com.
Also, check the Windows Event viewer for errors that correspond to the restarts, the ASPNET account, etc.
Also, check the Windows Event viewer for errors that correspond to the restarts, the ASPNET account, etc.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager