Vault 3.5 server apparent hang
Moderator: SourceGear
Vault 3.5 server apparent hang
Hi,
We are running the latest Vault server on Windows 2000 with a local SQL 2005 database and are experiencing apparent hangs of the server that are fixed by killing aspnet_wp.exe. Once aspnet_wp has re spawned everything goes back to normal.
During a 'hang' the client will connect to the server and offer a Repository choice. After selecting a repository the client hangs.
The admin client can still connect fine and no errors / messages are logged in either the application log or the sgvault log file (we are running debug level logging).
The frequency of these hangs can be anything between once a day to once an hour.
How do we proceed in diagnosing / getting this resolved?
Regards
Ben Cwilewicz
We are running the latest Vault server on Windows 2000 with a local SQL 2005 database and are experiencing apparent hangs of the server that are fixed by killing aspnet_wp.exe. Once aspnet_wp has re spawned everything goes back to normal.
During a 'hang' the client will connect to the server and offer a Repository choice. After selecting a repository the client hangs.
The admin client can still connect fine and no errors / messages are logged in either the application log or the sgvault log file (we are running debug level logging).
The frequency of these hangs can be anything between once a day to once an hour.
How do we proceed in diagnosing / getting this resolved?
Regards
Ben Cwilewicz
It's possible the client's version of the Vault tree is many versions out of date and it's taking a long time to diff and update the tree. Does client finally show the folder tree after a period of time?
Are there any errors in the Vault log file that correspond to the hang? The log is in %windir%\temp\sgvault.
Are there any errors in the Vault log file that correspond to the hang? The log is in %windir%\temp\sgvault.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
The tree will be very recent, and I have left the client for a good while (longer than it takes a fresh install to get the tree) with no result.lbauer wrote:It's possible the client's version of the Vault tree is many versions out of date and it's taking a long time to diff and update the tree. Does client finally show the folder tree after a period of time?
Not a thing, the log file simply stops logging any attempts to access it. No errors are logged.lbauer wrote: Are there any errors in the Vault log file that correspond to the hang? The log is in %windir%\temp\sgvault.
The only errors logged anywhere on the server relate to the ASP.NET 2.0 performance counters (below) and I am currently trying to fix these. Does Vault need the perf counters?
Reagrds,
Ben
===================
Perf Counter Error:
EventId 1008, Source Perflib
The Open Procedure for service "ASP.NET_2.0.50727" in DLL "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_perf.dll" failed. Performance data for this service will not be available. Status code returned is data DWORD 0.
If you delete the client-side cache file, does the client connect quickly?
http://support.sourcegear.com/viewtopic.php?t=6
If so, then it's possible adjusting your TreeManagerSize will help.
This setting is in the vault.config file in the VaultService directory.
The default is:
<TreeManagerSize>-1</TreeManagerSize>
Change the -1 to 250 and see if that makes a difference.
Detailed discussion of TreeManagerSize here:
http://support.sourcegear.com/viewtopic.php?t=363
I'll do some further investigation on the perflib error.
http://support.sourcegear.com/viewtopic.php?t=6
If so, then it's possible adjusting your TreeManagerSize will help.
This setting is in the vault.config file in the VaultService directory.
The default is:
<TreeManagerSize>-1</TreeManagerSize>
Change the -1 to 250 and see if that makes a difference.
Detailed discussion of TreeManagerSize here:
http://support.sourcegear.com/viewtopic.php?t=363
I'll do some further investigation on the perflib error.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
This has no effect, and I didn't expect it to as the only cure we found is killing aspnet_wp.exe on the server machine.lbauer wrote:If you delete the client-side cache file, does the client connect quickly?
I have been able to fix these errors, and it is still happening so it isn't related to this.I'll do some further investigation on the perflib error.
Cheers,
Ben
Did you adjust your TreeManagerSize?
Find this line in the vault.config file in the Vault Service directory:
and change it to:
Then restart IIS.
If you continue to experience the hang, put the Vault Server log in debug mode (Admin Tool->Server Options->Logging), reproduce the hang and send me a copy of the sgvault.log file in %windir%\temp\sgvault. My email address is linda at SourceGear.com.
Find this line in the vault.config file in the Vault Service directory:
Code: Select all
<TreeManagerSize>-1</TreeManagerSize>
Code: Select all
<TreeManagerSize>250</TreeManagerSize>
If you continue to experience the hang, put the Vault Server log in debug mode (Admin Tool->Server Options->Logging), reproduce the hang and send me a copy of the sgvault.log file in %windir%\temp\sgvault. My email address is linda at SourceGear.com.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
The change made no differencelbauer wrote:Did you adjust your TreeManagerSize?
Emailed.If you continue to experience the hang, put the Vault Server log in debug mode (Admin Tool->Server Options->Logging), reproduce the hang and send me a copy of the sgvault.log file in %windir%\temp\sgvault. My email address is linda at SourceGear.com.
Cheers,
Ben