SourceGear Fortress 2.0.4 is a maintenance release for Fortress 2.0. If you have not upgraded to Fortress 2.0, 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 Fortress installations, the upgrade may take several hours.

Fortress 2.0 is not backwards compatible with previous versions of Fortress. In essence, Fortress 2.0.x clients will only interact with Fortress 2.0.x servers and vice versa. Fortress 1.x clients and servers are not compatible with Fortress 2.0 clients and servers.

For details on Fortress licensing, including upgrade policies and demo keys, please see the Licensing FAQ


Known issues:

Important note when upgrading from the 1.0.6 release: There was a bug in the uninstall routine for the 1.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 1.0.6 server and client before upgrading.

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


What's New Since Fortress 2.0.3:

Visual Studio Enhanced Client
  • Addressed problem where the Source Code Control "Output" for Fortress
    would not initialize correctly and was never displayed in Visual Studio 2010.
  • Fortress Work Item integration now works correctly in Visual Studio 2010
  • The Visual Studio Enhanced Client log file correctly identifies Visual Studio 2010.
  • Bound web site projects now display the source code icons within Visual Studio 2010's Solution Explorer.


Command-Line Client
  • Addressed issue with Get by Label where the same label text is applied to different folders of a shared file and the label is created on the shared file itself. As with all shared items within a folder, the label's sub-path must be supplied in order for the Get by Label to succeed.


CruiseControl.NET Support
  • Added support for CruiseControl.NET 1.5.
  • Fixed problem with deleteItemsThatAreNotInTheRepository option to work even if local working directories are not present on disk.


  • Addressed an issue where a file that is checked out, but had the read-only file attribute set would cause an error dialog when the file was edited.


Java Command-Line Client
  • Fixed problem where a COMMIT in the Java Command-Line client would block and not complete until after two hours.


Client/Server Version Compatibility

It is always recommended that your client and server versions match exactly (e.g., a 2.0.3 client should be connecting to a 2.0.3 server). 2.0.x clients are 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 not compatible with 1.x clients and servers.


Upgrading From Previous Versions

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

To upgrade from a previous installation of Fortress, simply invoke the new installer, and choose the same options that were selected when Fortress 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 Fortress first, and then install the upgrade. As with installation, an uninstall will not delete your database unless you explicitly tell it to.