Note
Note Please consider newer version of the article if you are upgrading to VisualSVN Server 2.6: KB61: Upgrading to VisualSVN Server 2.6.

The article walks you through the upgrade process to the VisualSVN Server 2.5. Upgrading to a newer VisualSVN Server version is usually straightforward, but this article helps you to workaround possible edge cases. You should not consider the article if you have VisualSVN Server 2.5 already installed and just applying a patch update for it.

The article consists of two checklists that should be completed before and after installation of VisualSVN Server 2.5:

  • pre-upgrade checklist,
  • post-upgrade checklist.

When this article is applicable?

You should consider this article only if you are upgrading from VisualSVN Server 2.1 or older. You should not consider the article if you have VisualSVN Server 2.5 already installed and just applying a patch update. Installation of patch updates is straightforward unless stated otherwise in the corresponding release notes.

For example, you should not complete the checklists provided below if you are upgrading from VisualSVN Server 2.5.6 to the version 2.5.8. However, you should complete the checklists if you are upgrading from VisualSVN Server 2.1 to the version 2.5.

Where can I get the latest version of VisualSVN Server 2.5?

Please download the latest VisualSVN Server 2.5 installer at the official download page.

Pre-upgrade checklist

You should consider only those steps in the post-upgrade checklist that apply to the version of VisualSVN Server you have upgraded from. You can see a list of versions to which a checklist step applies in the "Upgrade from" column. For example, you should consider a checklist's step if you have upgraded from VisualSVN Server 1.7 and this version is listed in the corresponding "Upgrade from" column. You should skip the step if you have upgraded from a newer version.


Step Upgrade from

[ ]

Do not uninstall the existing VisualSVN Server instance

You must not uninstall the existing VisualSVN Server instance before installing a newer version. VisualSVN Server is designed to be always installed over the existing version. Important server settings could be lost when you uninstall VisualSVN Server instance.

2.1; 2.0; 1.7; 1.6; 1.5; 1.1; 1.0

[ ]

Make sure that you have administrative permissions on the computer

The step applies to an upgrade from all VisualSVN Server versions. To upgrade successfully, you should start the VisualSVN Server installation package under account with administrative permissions.

2.1; 2.0; 1.7; 1.6; 1.5; 1.1; 1.0

[ ]

Adjust access permissions if your repositories are stored on a network share

The step applies to an upgrade from VisualSVN Server 1.7 and older version. You should perform this step only if your server is configured to store repositories on a network share. Please skip this step if your repositories are stored locally in the folder such as C:\Repositories\.

Before the VisualSVN Server 2.0, the server was set to run under the built-in Local System account. For better security and isolation, these defaults were changed in the VisualSVN Server 2.0. Your server will be automatically reconfigured to run under the built-in Network Service account if you are upgrading from VisualSVN Server 1.7 or older version. So you are required to grant appropriate network share access permissions to the built-in Network Service account.

For the list of required access permissions, consider the KB22: Storing repositories on a network share article.

1.7; 1.6; 1.5; 1.1; 1.0

[ ]

Adjust access permissions if VisualSVN Server is installed to a custom location

The step applies to an upgrade from VisualSVN Server 1.7 and older version. Usually, this is an obligatory step if your VisualSVN Server is installed to a non-default location.

As said above, starting from version 2.0 VisualSVN Server runs under the built-in Network Service account. It is required that Network Service account must have read access permissions to the folder where VisualSVN Server is installed and for all its parent folders. With the default settings, the Network Service account should have read access permissions to the following folders:

  • C:\Program Files (x86)\VisualSVN Server\
  • C:\Program Files (x86)\
  • C:\

The upgrade process will fail if VisualSVN Server is installed to a non-default location (for example, D:\Applications\VisualSVN Server) or the computer has non-standard security settings configured. In this case you are requested to configure permissions for the above mentioned folders manually. For the further details please consider the KB37: Permissions required to run VisualSVN Server article.

1.7; 1.6; 1.5; 1.1; 1.0

[ ]

Upgrade without starting VisualSVN Server service if you run it under a custom account

The step applies to an upgrade from VisualSVN Server 1.7 and older version. Perform this step if you run VisualSVN Server under a custom user account. Please skip this step if have not changed default account used to run the server.

To avoid issues during the upgrade process, you must perform installation without starting VisualSVN Server service. Run the installation package using the following command:

VisualSVN-Server-2.5.8.msi NO_START_SERVICES=1

The new version will be installed but the service will not start automatically after the upgrade. You are required to manually reconfigure the server to run under the custom account. For further detail please consider the corresponding step in the post-upgrade checklist.

1.7; 1.6; 1.5; 1.1; 1.0

Post-upgrade checklist

You should consider only those steps in the post-upgrade checklist that apply to the version of VisualSVN Server you have upgraded from. You can see a list of versions to which a checklist step applies in the "Upgrade from" column. For example, you should consider a checklist's step if you have upgraded from VisualSVN Server 1.7 and this version is listed in the corresponding "Upgrade from" column. You should skip the step if you have upgraded from a newer version.


Step Upgrade from

[ ]

Enable Integrated Windows Authentication

The step applies to an upgrade from VisualSVN Server 2.0 and older version. For better security and usability, consider to enable Integrated Windows Authentication that is new feature of VisualSVN Server 2.1.

Please refer to the article KB43: How to configure Integrated Windows Authentication in VisualSVN Server for detailed instruction.

2.0; 1.7; 1.6; 1.5; 1.1; 1.0

[ ]

Reconfigure VisualSVN Server to run under your custom dedicated account

The step applies to an upgrade from VisualSVN Server 1.7 and older version. If you run VisualSVN Server service under a dedicated custom account and upgraded from version 1.7 or older, you need to reconfigure the service back to the custom account and manually start the service.

After the upgrade, perform the following steps:

  1. Reconfigure VisualSVN Server service to run under a custom account.
  2. If required, grant this account missing permissions.
  3. Start the service manually
For detailed instructions please consider the KB24: Configuring VisualSVN Server service to run under a dedicated user account article.

1.7; 1.6; 1.5; 1.1; 1.0

[ ]

Reconfigure repository access settings

The step applies to an upgrade from VisualSVN Server 1.1 and older version. If VisualSVN Server is set to use Windows Authentication, repository access settings will be lost during the upgrade from version older than 1.5. You should reconfigure the desired repository access settings with the following steps:

  1. Start VisualSVN Server Manager.
  2. Right-click the Repositories node.
  3. Select Properties.
  4. On the Security tab specify the desired repository access settings.

1.1; 1.0

[ ]

Upgrade format of repositories

The step applies to an upgrade from VisualSVN Server 1.1 and older version. To be able to use new Subversion functionality such as merge tracking, you are requested to upgrade repositories format with the following steps:

  1. Start VisualSVN Server Manager.
  2. Right-click the Repositories node.
  3. Select All Tasks | Upgrade Repositories Format.
  4. Select the repositories to upgrade and click OK.

1.1; 1.0

Last Modified: