We are using Vault 3.5.2 (5087) running on Windows 2003 R2 using IIS 6
On a regular basis while using the Vault GUI client we are getting session time out errors when trying to access our Vault repositories. We have looked through a number of the posts here on this site in an attempt to correct these issues and have checked\changed a number of our settings as per recommendations found here (ie http://support.sourcegear.com/viewtopic.php?t=1014)
While further researching the problem I came across a number of “.Net Runtime 2.0 Error” entries in the Event Viewer Application Log. The Event ID on these are 5000 with the description text as follows:
“EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 4c2d, P8 6, P9 udta330idobh2roz2ayvlcelag5agtls, P10 NIL.”
We also get a number of warnings in our Event Viewer System log. These Say Source “W3SVC” with an Event Id of 1011 and a description as follows:
“A process serving application pool 'VaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '1328'. The data field contains the error number.”
From my reading on this site I think that these entries would probably cause the site to be restarted and thus our Session Timeouts. Could this the case? Any idea on how we can fix it?
We also have a set of tools that we have created that utilize the Vault command line so we can call them programmatically. We often are using the command line tools as well as the GUI on the same workstation at the same time.
Thank You
Mike
Session Timeout
Moderator: SourceGear
The same kind of issue was confirmed in this KB article where it recommends going to IIS 5 Isolation mode: http://support.sourcegear.com/viewtopic.php?p=8430.
That is one possible solution, but I have found it most certainly is something in the App Pool. I just haven't narrowed it down to what exactly yet. If you would like, send me an email through support at sourcegear.com (attn: Beth) with a link to this thread. Then we can walk through your exact settings and see if we can get this narrowed down or an exact fix. Everyone I ran across got fixed, but mostly through trial and error so far.
That is one possible solution, but I have found it most certainly is something in the App Pool. I just haven't narrowed it down to what exactly yet. If you would like, send me an email through support at sourcegear.com (attn: Beth) with a link to this thread. Then we can walk through your exact settings and see if we can get this narrowed down or an exact fix. Everyone I ran across got fixed, but mostly through trial and error so far.