In the event that your Vault client takes a long time to load the repository tree or hangs during that process or even gives you a blank tree, make the following changes. These can all be performed and kept at once.

1) If Vault opens and is ready, but the tree is just blank, the panel docking information may be causing the tree to not show. Close Vault. Then browse to your Client Side Cache. Delete the file vaultgui_dockpanel.config, and then reopen Vault.

2) If a long time to load or hanging, turn off Request Database Delta on Repository Cache Miss.

3) Change the order of the .NET Framework preferred runtime for the Vault client found in the client installation's VaultGUIclient.exe.config file. On some systems, the .NET Framework installed on the machine may be affecting behavior or performance. In later versions of Vault, this section

On some systems, it may be necessary to 'flip' the ordering of the supportedRuntime elements. Depending on your setup, v2.0.50727 may need to be listed first, and on other systems, v4.0 may need to be listed first.

To make the change:

a) Close Vault and Visual Studio.

b) Go to the directory where the Vault client is installed and edit the file VaultGUIclient.exe.config.

c) Find the line listing the <startup> element. After the comment, there will be two lines after those referencing the 2.0 and 4.0 .Net Frameworks. Swap the positioning of these two lines placing the the preferred .NET Framework which matches your environment above the other.

d) Save the changes to the file and close the editor.

e) Retry the client.

4) Check for excessive database log files. By default SQL Server will keep a running transaction log for the database. This log can grow to excessive sizes, thus affecting performance if they are not truncated by running a backup or not using 'Simple' recovery mode. If you need assistance, contact SourceGear Technical Support or search for 'SQL Server Transaction Log' for additional information.

5) Even though Vault doesn't directly touch the network (it goes through IIS and .NET), it has been reported that some network configurations or equipment are not yet ready for IPv6. Disabling IPv6 on the server has shown performance improvements for some users.

6) Sometimes the notification database can grow excessive if there is an incorrectly configured notification server. Check for excessive rows in sgnotify and remove them. You can find the total number with this SQL query:

8_) Ghosting can cause a performance hit, especially if either a remote location is ghosted or a very large area. The ghosting options are in the Vault Tools - Options - General. Turn off ghosting to see if performance is improved.

9) Folder Security can cause a performance hit if there are many permission settings for various folders. The way to check this is to go to the Vault Admin web page, expand the list of repositories on the left, click on each repository name and uncheck Folder Security. Restart the client before testing.

10) CVS mode causes a lot of additional scanning to catch when changes are happening which can slow things down depending on how much is being scanned. Go to Tools - Options - Concurrent Development Style and click the VSS mode button, and don't change any of the settings below the buttons except for Exclusive Locks. You can choose your preference for Exclusive Locks. After this change, perform a Get to change the writable settings on the files, and then check out files you need to edit.