September 2004

SourceGear Vault is a source code control system designed specifically to replace Microsoft Visual SourceSafe. Vault is built on Microsoft SQL Server and .NET with a design that emphasizes reliability, network integration and openness.

Installation Requirements

The SourceGear Vault server requires either Windows 2003 Server or Windows 2000 Server (SP3) with the .NET Framework 1.1, IIS 5.0 or greater, and either Microsoft SQL Server 2000 or MSDE 2000.

The SourceGear Vault clients require at least Windows 2000 or Windows XP with the .NET Framework 1.1.

Upgrades from Previous Versions

It is recommended that you backup your Vault database prior to an upgrade. This can be done from either the Vault Admin tool, or the SQL Enterprise Manager tool.

To upgrade from a previous installation of Vault, simply invoke the new installer, and choose the same options that were selected when Vault was previously installed. Program files and configuration settings will be automatically updated to reflect the upgrade. Note that the server installation will not delete your database unless you explicitly tell it to.

You may also safely uninstall Vault first, and then install the upgrade. As with installation, an uninstall will not delete your database unless you explicitly tell it to.

NOTE: The Vault 2.0 server cannot be upgraded from a Vault 1.0 server installation (which includes Vault 1.0.1, 1.0.2 and 1.0.3), due to changes in installer technology. The Vault database can be upgraded, but the server installation itself cannot.

If you are currently running Vault 1.0, you can first upgrade from Vault 1.0 to Vault 1.1 or 1.2, and then upgrade to 2.0. Additionally, you can uninstall Vault 1.0, and then install Vault 2.0 as a new installation. Be sure to not delete your database when uninstalling, and to choose the existing database on the fresh install.

Release Contents

The programs included as part of Vault include:

  1. Vault Server (VaultService.asmx). This is actually a .NET Web Service installed in an IIS virtual directory. It uses SQL server to store the source control files, and accepts connections from Vault clients.

  2. Vault GUI Client (VaultGUIClient.exe). A Windows .NET client that connects to the Vault Server and allows users to locally manage files under source control in a windowed application.

  3. Vault Command Line Client (vault.exe). A command line client that supports many of the commands the GUI client supports, allowing the user to connect to the Vault Server via scripts or without user intervention. This client still requires the .Net framework in order to run.

  4. Visual Studio IDE Integration DLL (VaultIDE.dll). Allows Vault to be the source control provider in Visual Studio .Net, VC6, and VB6. Note that this uses the Microsoft MSSCCI interface to integrate with Visual Studio, and is therefore limited in functionality to what MSSCCI allows. The GUI client is recommended for a more full-featured interface.

  5. Vault Admin Tool Client (VaultAdmin.exe). A Windows .Net client that allows the user to configure the Vault Server and its repositories.

  6. SourceSafe Import Tool (VSSImport.exe). A wizard that creates Vault repositories from existing Visual SourceSafe databases (or parts of them). This wizard supports import of file history, labels, and additionally shares and pins files in Vault as they are in VSS.

Install Packages

These programs are included in the following installation packages:

  1. Server Installer:
    • Vault Web Services DLLs
    • Admin Tool (optional)
    • GUI Client (optional)
    • Command Line Client
    • Visual Studio IDE Integration DLL
  2. Client Installer:
    • GUI Client
    • Command Line Client
    • Visual Studio IDE Integration DLL
  3. Admin Tool Installer:
    • Admin Tool
  4. VSS Import Tool:
    • VSS Import Tool

License Numbers

Vault requires a demo license before any user other than Admin can log in. If you downloaded Vault from our website, you should have received a license number by email. If you do not have a license number, go to:
and select the "Demo Serial Number" link. This will automatically send you a license number for use in demoing Vault. Once you have a license number, login into the Admin Tool (using the "Admin" login and password that was specified during installation), and add the license number using the Licenses Tab.

ASP.NET Configuration

When running the Vault server on a machine with IIS 5.0, Vault users may wish to modify the responseDeadlockInterval parameter in the ASP.NET machine.config file on the Vault server machine. In its default configuration, ASP.NET assumes that an application is deadlocked if it requires more then three minutes to respond to a request. Under certain situations, ASP.NET may terminate the Vault server application if an operation requires more than three minutes. When this happens, ASP.NET will make an entry in the Application section of your Event Log:

aspnet_wp.exe (PID: xxx) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last 180 seconds.

This problem can be avoided by changing the responseDeadlockInterval to a longer time duration. Note, however, that this configuration parameter affects all ASP.NET applications on the server machine.

We recommend running the SourceGear Vault server on a dedicated machine with ASP.NET configured with a responseDeadlockInterval of one hour. This configuration is not strictly required, and may not be necessary for many users. If you choose to run the Vault server on a machine which is shared by other ASP.NET applications, you may wish to try using Vault with the responseDeadlockInterval unchanged.

To change this parameter, locate your machine.config file:


Within that file, locate the processModel element. On that element is an attribute called responseDeadlockInterval. To change this value to one hour:


Support and Contact Information

There are a number of ways to get access to Vault support:

  1. The SourceGear Vault documentation page at contains support resources, such as troubleshooting guides, tech notes, and FAQs.
  2. A public forum exists at where you can ask questions of the Vault community, and search a knowledge base for answers to common problems.
  3. Use the Help->Technical Support Menu item to send an email to SourceGear’s support department for any installation or usage issues concerning Vault.

Any questions regarding pricing or sales can be emailed to

Support for Vault is available from 9am-5pm Central Time Monday through Friday.

Changes for 2.0.6

The following changes have been made in the 2.0.6 release:

Changes for 2.0.5

The following changes have been made in the 2.0.5 release:

Changes for 2.0.4

The following features and changes have been included in the 2.0.4 release:

Changes for 2.0.3

The following features and changes have been included in the 2.0.3 release:

Changes for 2.0.2

The following features and changes have been included in the 2.0.2 release:

Changes for 2.0.1

The following features and changes have been included in the 2.0.1 release:

Changes for 2.0

The following features and changes have been included in the 2.0 release: