Release Notes for 4.1.4

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 4.1.4

Post by jeremy_sg » Mon Nov 24, 2008 1:25 pm

SourceGear Vault 4.1.4

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

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

* Folder Security Admin Web Client page loaded very slowly for repositories with large trees
* Adding a shadow folder needed to be performed twice if the disk path did not exist


* An Object Reference exception was being thrown when upgrading 4.1.2 -> 4.1.3 using IIS 7 with compatablity mode turned off
* Upgrading from 3.X to 4.X, was resetting users' repository access rights


* The DiffMerge Shell Extension now works on 64bit Vista systems.

Class Client

* Encoding was accidentally changed when EOL conversion was applied
* The Classic client could not add a solution if there was no repository cache file.

Visual Studio Enhanced Client

* Status glyphs were inaccurate in certain project types.
* Files in web site bin folders were being added when they shouldn't be
* The changes made by an implicit get latest/checkout/reload can no longer be undone
* msscci2vsip binding converter now handles projects that aren't beneath the solution on disk. msscci2vsip is now a supported Power Toy
* NodeCounter helps users explore their source control repository to find which folders have the most subitems, as well as which folders have the largest disk space usage. NodeCounter in now a supported Power Toy
* When a project was in the root of a drive, repository paths were not being determined correctly

Command-Line Client

* HTML help is now implemeted for the Java CLC
* CLC GETLABEL fails when an item has been shared two or more times inside the label
* DIFF is now implemented for the Java CLC

Eclipse Plugin

* The Eclipse client was erroneously prompting for file reloads anytime a file was checked in

Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 4.1.4 client should be connecting to a 4.1.4 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.
Subscribe to the Fortress/Vault blog

Post Reply