Vault 2.0.5 Release Notes

[dan]

The following features and changes have been included in the 2.0.5 release:
<UL>
<b>Client Only Changes</b>
<LI>Client now has logging capabilities. See http://support.sourcegear.com/viewtopic.php?t=1534 for more details.
<LI>Fixed mutex error that would happen intermittently in Vault clients.
<LI>Fixed error with cookie handling while downloading files on some systems.
<LI>Fixed incorrect error message when user logs in with an invalid account name.
<LI>The repository list in the admin tool is now sorted in the same way it is sorted in the database (fixing a problem where spaces and dashes were sorted differently and caused a problem on which row was being viewed).

<b>Server Only Changes</b>
<LI>Fixed error with default rights and label security when viewing an inherited label.
<LI>Fixed mutex-related Shadow folder errors when there were multiple shadow folders defined.
</UL>

<b>Client/Server Version Compatibility</b>
It is always recommended that your client and server versions match exactly (e.g., a 2.0.5 client should be connecting to a 2.0.5 server). 2.0.x clients should be able to communicate with any 2.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 2.0.x clients and servers are incompatible with 1.1.x or 1.0.x clients and servers.

The Vault Admin Tool must match the version of the Vault Server for the Admin Tool to work properly.

<b>Upgrading From Previous Versions</b>
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.