Trouble opening repositories.
Moderator: SourceGear
Trouble opening repositories.
On trying to start vault and open most of our repositories I gat a message which says
"Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate."
Does anyone have any idea how to resolve this problem?
"Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate."
Does anyone have any idea how to resolve this problem?
C Clarke-Williams
I T Manager
Wicks and Wilson Ltd
I T Manager
Wicks and Wilson Ltd
System Starteds Entries
Yes there do seem to be a fair number of these roughly once every minute or two. Here is a sample.
----27/03/2008 12:26:03 --()-- Vault Failed to establish a connection to the database. ----27/03/2008 12:27:51 sgvaultsystem--()--
System Started
Version 4.0.6.15954
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
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = NT AUTHORITY\NETWORK SERVICE
----27/03/2008 12:28:50 KevinK--dev-chris.wwl-int(200.128.1.102)--SSL Disabled Login ----27/03/2008 12:28:50 sgvaultsystem--()--
System Started
Version 4.0.6.15954
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
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = NT AUTHORITY\NETWORK SERVICE
----27/03/2008 12:26:03 --()-- Vault Failed to establish a connection to the database. ----27/03/2008 12:27:51 sgvaultsystem--()--
System Started
Version 4.0.6.15954
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
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = NT AUTHORITY\NETWORK SERVICE
----27/03/2008 12:28:50 KevinK--dev-chris.wwl-int(200.128.1.102)--SSL Disabled Login ----27/03/2008 12:28:50 sgvaultsystem--()--
System Started
Version 4.0.6.15954
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
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = NT AUTHORITY\NETWORK SERVICE
C Clarke-Williams
I T Manager
Wicks and Wilson Ltd
I T Manager
Wicks and Wilson Ltd
System starts.
OK I seem to have stopped the system from continually restarting but it still will not allow me to open most of my repositories.
Any ideas?
Any ideas?
C Clarke-Williams
I T Manager
Wicks and Wilson Ltd
I T Manager
Wicks and Wilson Ltd
similar issue
This looks similar to my issue:
http://support.sourcegear.com/viewtopic.php?t=9951
I have a full debug log attached in that post above.
http://support.sourcegear.com/viewtopic.php?t=9951
I have a full debug log attached in that post above.
Your problem.
Zumafan,
I agree the two problems do look similar. I may have resolved mione but as all the load is now off the server it being 7 p.m. I cannot be sure.
What I did was update to version 4.1.0.1626
I the increased the number of worker processes allowed for the Vault Application in the IIS administration tool to 24 from 12. I expect this to cause me problems tomorrow but at least I have the temporary illusion of a fix. Ironically fitting an extra Gig of RAM to the server seems to have broken Vault although Fogbugz was working.
Slightly working that neither of us have had any feedback on here from the SourceGear support people.
Best of luck.
I agree the two problems do look similar. I may have resolved mione but as all the load is now off the server it being 7 p.m. I cannot be sure.
What I did was update to version 4.1.0.1626
I the increased the number of worker processes allowed for the Vault Application in the IIS administration tool to 24 from 12. I expect this to cause me problems tomorrow but at least I have the temporary illusion of a fix. Ironically fitting an extra Gig of RAM to the server seems to have broken Vault although Fogbugz was working.
Slightly working that neither of us have had any feedback on here from the SourceGear support people.
Best of luck.
C Clarke-Williams
I T Manager
Wicks and Wilson Ltd
I T Manager
Wicks and Wilson Ltd
zumafan: I replied to your post. Yes, I think these could be the same.
Chris: I'd like you to do the same thing that I'm having Zumafan do. I'll copy that response here.
Chris: I'd like you to do the same thing that I'm having Zumafan do. I'll copy that response here.
This looks like it could your IIS settings. Go into your IIS manager and Check that your Vault service is set to use the Vault App Pool. Then go into your Vault app pool and check the settings there. You could have recycling going on there, or you could have a web garden limit set (default is 1 and that is no limit I think).
Thanks for that.
Thanks for that it may well have done the trick.
C Clarke-Williams
I T Manager
Wicks and Wilson Ltd
I T Manager
Wicks and Wilson Ltd