This article describes the process of upgrading your VisualSVN Server to the current version and possible issues the one can encounter in some specific cases. For each case, workaround instructions are given.
Generally, the upgrade process is painless and consists of the following steps:
- Download the latest version from the download page.
- Run the installation package.
- Follow the installation wizard steps.
It is not recommended to uninstall the previous version before the upgrade as custom server parameters such as port numbers will be lost.
Upgrading from version 2.0.x
The upgrade from version 2.0.x is smooth and painless. There are no known issues. Just run the installation package and follow the installation wizard steps. For better security and usability, consider to enable Integrated Windows Authentication that is new for VisualSVN Server 2.1. Detailed instructions on how to configure Integrated Windows Authentication are given in KB43.
Possible issues while upgrading from version 1.7.x or earlier
Since version 2.0, system built-in Network Service account is used to run VisualSVN Server service (this account has minimal privileges on the computer that provides better security). So if you are upgrading from version 1.7.x or earlier, the current account used to run VisualSVN Server service will be automatically switched to the Network Service account.
In some specific cases, this account switch could result in installation failure (possible causes are described below). If you decided to upgrade your old VisualSVN Server to the current version, check whether your case relates to one of the listed below and follow the corresponding instructions.
Cause 1. Repositories folder is stored on a network share.
By default, VisualSVN Server stores repositories in a single folder on the local disk (C:\Repositories). If your repositories are stored remotely on a network share, before running the installation make sure that all the required permissions on this folder are assigned to the Network Service account. See KB22 for details on configuring VisualSVN Server to store repositories on a network share.
Cause 2. Network Service account does not have permissions for installation folder parent folders.
For some technical reasons, it is required that Network Service account should have read access permissions for 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 (see KB37 for the full list of required permissions):
- C:\Program Files\VisualSVN Server\
- C:\Program Files\
- C:\
The upgrade process will fail if your VisualSVN Server is installed to a non-default location (D:\Applications\VisualSVN Server, for example) or your computer is configured with non-standard security settings. In this case you are requested to configure permissions for the above mentioned folders manually.
Cause 3. VisualSVN Server service is configured to run under custom account.
This is a known issue of VisualSVN Server versions prior to 2.0 that VisualSVN Server service custom settings are switched back to their defaults during the upgrade. This issue was fixed in VisualSVN Server 2.0, but if you are using the earlier version and have configured a dedicated account to run VisualSVN Server service, the account will be switched to the Network Service account.
To avoid access issues during the upgrade process in this case, perform the installation without starting VisualSVN Server service:
- Download the latest version from the download page.
- Run the installation package using the following command:
VisualSVN-Server-2.0.7.msi NO_START_SERVICE
If NO_START_SERVICE key is specified, VisualSVN Server service will not be started during the upgrade.
- Follow the installation wizard steps.
- After the installation, reconfigure VisualSVN Server service to run under custom account.
- If required, grant this account missing permissions (see KB24 for details on configuring VisualSVN Server service to run under custom account).
Upgrading from version 1.1 or earlier
If you are using VisualSVN Server 1.1 or earlier, besides checking the cases described above, perform the following actions after the upgrade:
- Upgrade repositories to Subversion 1.6 format.
- Reconfigure desired repository access settings if Windows authentication is used.
Upgrading repositories format
To be able to use new Subversion functionality such as merge tracking, you are requested to upgrade repositories format with the following steps:
- Start VisualSVN Server Manager.
- Right-click the Repositories node.
- Select All Tasks > Upgrade Repositories Format.
- Select the repositories to upgrade and click OK.
Reconfiguring repository access settings
If Windows Authentication is used, repository access settings will be lost during the upgrade from versions prior to 1.5. This is a known issue that was fixed in version 1.5. You are requested to reconfigure the desired repository access settings with the following steps:
- Start VisualSVN Server Manager.
- Right-click the Repositories node.
- Select Properties.
- On the Security tab specify the desired repository access settings.
