When trying to create a slave repository, you may receive the following error message:
This error indicates that the version of VisualSVN Server instance hosting the master VDFS service is outdated and is not compatible with the slave VDFS service.
In order to resolve the issue, it is recommended to upgrade all VisualSVN Server instances in the multisite environment to the same version. Read the article KB95: Upgrading to VisualSVN Server 3.5 instructions for upgrading to the latest version of VisualSVN Server.
In order to workaround the issue, it is possible to switch the slave VDFS service to the backward compatibility mode. However, in such case not all VDFS features are going to be available until both VisualSVN Server instances are at the most up-to-date or at least compatible version.
Follow these steps, in order to switch the slave VDFS service to backward compatibility mode:
Add the following registry value (string) on the slave VisualSVN
Server computer (assuming that the master computer has
VisualSVN Server 3.4 installed):
for a 32-bit operating system:
[HKEY_LOCAL_MACHINE\SOFTWARE\VisualSVN\VisualSVN Server] "VdfsProtocolVersion"="3.4"
for a 64-bit operating system:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VisualSVN\VisualSVN Server] "VdfsProtocolVersion"="3.4"
- for a 32-bit operating system:
- Restart the VisualSVN Server services on the slave server.
- specify "VdfsProtocolVersion"="3.4" if the master VisualSVN Server version is 3.4.x or 3.3.x,
- VDFS protocol versions "3.0" and "3.2" are not supported in VisualSVN Server 3.5. You must upgrade VisualSVN Server 3.0 and 3.2 instances to newer VisualSVN Server version. Read the article KB95: Upgrading to VisualSVN Server 3.5 for instructions for upgrading to the latest version of VisualSVN Server.
See alsoKB96: Upgrading to VisualSVN Server 3.5 in a multisite environment
KB95: Upgrading to VisualSVN Server 3.5