Remote VisualSVN Server Manager is unable to access repositories on a network share

Applies to: VisualSVN Server 2.5 and later

When you connect to a remote VisualSVN Server using VisualSVN Server Manager, you may see the following error messages on the dashboard:

A similar error message may be displayed when you attempt to configure a remote VisualSVN Server to store repositories on a network share:

These error messages usually occur when you connect using VisualSVN Server Manager to a remote server which is configured to store repositories on a network share. The possible causes of these error messages are described below.

Technical background

When you connect to VisualSVN Server using VisualSVN Server Manager, you are authenticated to the server with your current Windows credentials. VisualSVN Server impersonates you and all administrative actions on the remote server are performed on your behalf.

In general, the error messages shown above say that you have insufficient privileges to access a network share where repositories are stored. For further details regarding permissions for repositories root folder stored on a network share please consider the KB22 article.

These particlar error messages usually occur when you connect to a remote VisualSVN Server which is configured to store repositories on a network share. Since all administrative actions are performed on your behalf, additional configuration steps may be required to allow the server to delegate your Windows credentials to a fileserver where repositories are stored (in other words, to the fileserver which hosts a network share where repositories are stored). For further details regarding the credentials delegation please consider the Delegation and Impersonation Microsoft TechNet article.

The following conditions have to be met in order to enable delegation:

• All three involved computers must be in the same domain.
• Computer that runs VisualSVN Server must be trusted for delegation.
• VisualSVN Server administrator's account must not be "sensitive".

Resolution

The particular instructions on how to resolve the issue are given below.

1. Make sure that all three involved computers are in the same domain.
2. Verify that VisualSVN Server computer is trusted for delegation:
   1. Open Active Directory Users and Computers console.
   2. Locate the computer where the VisualSVN Server is installed.
   3. Open the Properties dialog for the computer Delegation tab.
   4. Make sure that Trust computer for delegation to any service (Kerberos only) checkbox is checked.

   For additional information please check the Allow a computer to be trusted for delegation Microsoft TechNet article.

3. Verify that VisualSVN Server administrator's account is not set as "sensitive":
   1. Open Active Directory Users and Computers console.
   2. Locate the VisualSVN Server administrator's account.
   3. Open the Properties dialog and switch to the Account tab.
   4. Make sure that Account is sensitive and cannot be delegated option under Account Options is unchecked.
4. Log off and log in again to the client computer where the VisualSVN Server management console is installed to make sure that changes made in the previous steps have been succesfully propagated. The issue should be resolved and VisualSVN Server administrator could succesfully manage remote VisualSVN Server.