Release Notes for Vault 4.1.1

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear

Post Reply
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear

Release Notes for Vault 4.1.1

Post by jeremy_sg » Thu Mar 27, 2008 3:42 pm

SourceGear Vault 4.1.1 is a maintenance release for Vault 4.1. If you have not upgraded to Vault 4.1 version, see for more information.

Installation Notes

• This upgrade includes an update to an index on the labels database table. This update may take a long time while installing.

• Please ensure you have a verified backup of your database before upgrading, and upgrade at a time when it is convenient to not have access to the server. On very large Vault installations, the upgrade may take several hours.

• Vault 4.1 does not support Dragnet integration. Users requiring integrated work item tracking should investigate Fortress. Fortress is an integrated solution for application lifecycle management (ALM), including work item tracking and work item clients integrated into Visual Studio and Eclipse.

• Vault 4.1 is not backwards compatible with previous versions of Vault. In essence, Vault 4.1 clients will only interact with Vault 4.1 servers and vice versa. Vault 2.0, 3.0, 3.1, 3.5 and 4.0 clients and servers are not compatible with Vault 4.1 clients and servers.

Known issues:

Important note when upgrading from the 4.0.6 release. There was a bug in the uninstall routine for the 4.06 for users who installed the server and the client together using the server's installer. Upgrading in that situation will succeed, but leave two client shortcuts on the desktop. Please follow the instructions at for instructions on removing the 4.0.6 server and client before upgrading.

When using the VS Enhanced Client's "Open From Vault" functionality in 2008, you will not be able to open solutions that have not yet been upgraded by Visual Studio to the Visual Studio 2008 format.

Web Site projects with large numbers of files or files accessed via a network will still suffer from some performance problems.

The following changes are included in this release:

* Power Toys - Small stand-alone applications that some users will find helpful. You can find out more about them at
* Some large customers were reporting very long startup times.
* Support for IIS7 on Vista and Windows Server 2008 in Integrated mode.
* The Enhanced Client was sometimes clobbering changes that had not been merged into a Needs Merge file.
* The Vault Client API is now fully supported.
* NTFS Permissions were not being set correctly when installing on 64 bit systems.
History paths were being clipped when folder security was turned on for a repository.
* The Enhanced Client now provides keyboard shortcuts for common operations.

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 4.1.1 client should be connecting to a 4.1.1 server). 4.1.x clients are able to communicate with any 4.1.x server, but specific bug fixes will not work correctly if they required both client and server changes. 4.1.x clients and servers are not compatible with 1.x, 2.x, or 3.x clients and servers.

Upgrading 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.

Post Reply