Manually updating CollabNet Subversion Server and TortoiseSVN

With CollabNet releasing a new version of Subversion Server (1.6.11), and TortoiseSVN having a release a few days earlier, it's time to do an actual update, instead of a comment like I did last time.


I'm currently running CollabNet Subversion Server version on Windows 7 Home Premium, 64-bit.

The install directory is C:\Program Filies (x86)\CollabNet\Subversion Server\, and I'm installing version These instructions should work, with minor changes, for other versions of CollabNet Subversion and Windows.

Backups and downloads

First make sure you've backed up your repositories, just in case you need to roll back.

Next download CollabNet Subversion Server for your environment. You can also go ahead and and start downloading TortoiseSVN.

Browse to the CollabNet Subversion Server install directory (C:\Program Filies (x86)\CollabNet\Subversion Server\ on my system) and make sure you make a backup of the Apache configuration file, httpd\conf\httpd.conf.

Upgrading CollabNet Subversion Server

In the CollabNet Subversion Server install directory open httpd\bin\ApacheMonitor.exe and stop the currently running instance of Apache, then exit out of Apache Monitor.

Open the Services listing (Administrative Tools > Services) and stop CollabNet Subversion svnserve (or you won't be able to update any DLLs, without uninstalling first).

Start the CollabNet Subversion Server installer and when prompt, click Yes to upgrade.

Go ahead and click through the installer. Since we're upgrading, the settings should be just fine as they are.

Start Apache Monitor back up, and start the instance, or just start the CollabNet Subversion Apache service (you can stop it via this as well).

Test you can access the repository by browsing to it, if enabled, or going into a checked out repository and looking at the log.

Upgrading TortoiseSVN

Start the TortoiseSVN installer, clicking through as usual. To finish, TortoiseSVN will require a restart.

Once your system is back up, browse to a checked out directory and verify that you're able to use base functionality, even going so far as to commit changes to a test repository, as needed.