ERROR: Session is no longer valid

[jdpalmer]

We are receiving frequent (daily) errors in Visual Studio from a Vault Pro dialog box:

An error has occurred. The error message is: Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate.

When we added a large number of files to the Vault repository in the Spring of this year, the Vault Pro server application frequently threw OutOfMemory exceptions. Whenever these occurred, all of the Vault clients would receive the Vault error dialog box above, and they'd have to refresh the project's source control status in Visual Studio.

I worked with SourceGear Support to resolve the OutOfMemory exceptions by changing the Vault server's IIS Application Pool settings and also some vault.config changes as supported by the support team. After a few tweaks, this appears to have resolved that error.

However, as I mentioned above, we're still receiving the Vault error dialog boxes frequently, which is very frustrating, to say the least. The Vault server logs are still configured to log at the Debug level of verbosity, yet we do not see any Exceptions in the log when the users receive the error dialog.

Furthermore, it almost certainly has to be the Vault server recycling the application pool because once one developer receives the "Session is no longer valid" error, then all the developers receive the same error the next time they try to perform any source control operation. So it would not be the case that it's a per-user session timing out.

Please advise.

[lbauer]

When you look in the Server log, do you see 'System Started" coinciding with the times that users are disconnected?

[jdpalmer]

Yes, I see several "System Started" events in the log, and this week we're also re-experiencing System.OutOfMemoryException errors again.

[Beth]

Since we were working together on the out of memory errors before, I'm going to send you an email from the previous ticket and pick this up from there.

HS: 223077

[baclay]

I am also getting this error message. And when trying to open files for modification from within Visual Studio, it appears that the file(s) are checked out, but when you attempt to modify the file it prompts to check out the file again. The application event log has this warning message related to vault professional:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 7/25/2012
Time: 5:35:28 PM
User: N/A
Computer: INKWORKS2
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/25/2012 5:35:28 PM
Event time (UTC): 7/25/2012 10:35:28 PM
Event ID: 54e24562cfae46818be152f5699758df
Event sequence: 7
Event occurrence: 2
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/VaultPro-2-129877289412343750
Trust level: Full
Application Virtual Path: /VaultPro
Application Path: C:\inetpub\wwwroot\VaultPro\
Machine name: INKWORKS2

Process information:
Process ID: 6924
Process name: aspnet_wp.exe
Account name: NT AUTHORITY\SYSTEM

Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.

Request information:
Request URL:
Request path:
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM

Thread information:
Thread ID: 5
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at MantisServiceLib.Helpers.LogMessage(DNLogEntryType let, String strMsg)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss, Boolean signOut)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss)
at Mantis.Global.Session_End(Object sender, EventArgs e)


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[Beth]

baclay: Your case sounds like you could have conflicting working folder settings.

Are you able to check in your file or does it give you an error?

Open your Vault GUI client and look at the check out information on one of your files that gives errors. Does the check out information match what Visual Studio has for its location?