Applies to: VisualSVN Server 5.0 and later
You may see the following message when attempting to view the list of repositories in the web interface:
This server either has no repositories or you don't have permissions to access them.
The message can be displayed in the following two cases:
- No repositories are hosted on this VisualSVN Server instance yet.
- Your user account does not have the required permissions to access any repositories on this VisualSVN Server instance.
You need to contact the administrator of this VisualSVN Server instance to resolve these issues.
Information for the administrator
The possible reasons why a user may see the empty list of repositories are stated above. Follow the steps described below to resolve these issues.
Checking whether any repositories are hosted on the server
To check whether your VisualSVN Server hosts any repositories, open the VisualSVN Server Manager console and click the Repositories item in the left-hand pane. This will display the list of hosted repositories in the main pane to the right. If there are no repositories listed in the main pane, it means that no repositories are hosted on the server yet. You can add a repository that you want to host onto the server as described in Getting Started | Adding Repositories.
Checking and configuring access permissions for the user
To make a repository visible to a user in the repository list in the web interface, access permissions for the repository need to be configured in one of the following two ways.
Option 1: granting access to the root folder of the repository
Make sure that the user has Read Only or Read/Write access to the root folder of the desired repository. For information about access permissions, see Getting Started | Configuring User Permissions.
Option 2: without granting access to the root folder of the repository
If you do not want to give the user at least read level access to the root folder of the desired repository, then instead:
- The user needs to have Read Only or Read/Write access to a subfolder or file inside this repository. For information about access permissions, see Getting Started | Configuring User Permissions.
- Also, the option called Implicit list folder permission for parents of readable paths needs to be enabled for this repository, as described in Configuring implicit list folder permission.