I lead a dev team of about 5 people. We are all using Vault 2.03, served off of IIS 6. Like some other posters to the forum - we keep experiencing the dreaded lost session issue.
I have read the knowledge base article on the matter but it does not seem to help me at all.
I was wondering if I should try to using the ASPnet state server vs the InProc mechanism for keeping state? Would that cause any issues or am I really off.
The issue has become a real nuisance.
Vault session keeps timing out
Moderator: SourceGear
Can you expand on which exact values in the IIS Manager you are refering to (concerning the state server vs InProc)?
This session timeout is a real pain, since there are so many values that control it, and W2K3's defaults are set up to kill off processes quite often.
One clue that might help: When you lose your session, does the Vault server actually restart, or is it just individual sessions that are dropped? This would help determine which settings to look at. You can check the Vault server log file to see if the server has restarted.
One other place to check (which I just updated the KB article on), is the session state time limit within IIS. Vault's setting in the Admin Tool is supposed to override this, but perhaps IIS ignores it for w2k3. From the IIS Manager, check Web Sites->Vault Site->Properties->Home Page->Configuration->Options->Session State. By default, it is 20 minutes. Set it to the same value as the Vault Admin tool as see if that helps...
This session timeout is a real pain, since there are so many values that control it, and W2K3's defaults are set up to kill off processes quite often.
One clue that might help: When you lose your session, does the Vault server actually restart, or is it just individual sessions that are dropped? This would help determine which settings to look at. You can check the Vault server log file to see if the server has restarted.
One other place to check (which I just updated the KB article on), is the session state time limit within IIS. Vault's setting in the Admin Tool is supposed to override this, but perhaps IIS ignores it for w2k3. From the IIS Manager, check Web Sites->Vault Site->Properties->Home Page->Configuration->Options->Session State. By default, it is 20 minutes. Set it to the same value as the Vault Admin tool as see if that helps...