Browse is not available when connected to VisualSVN Server remotely

There are various types of tasks in which VisualSVN Server prompts the administrator to specify a path to a file or a folder. For instance, when you restore a backup, the Restore Repository wizard prompts you to specify a path to the backup file. If you are managing the server locally, usually you click the Browse button and then select the path using the standard Windows Select Folder dialog box.

However, when you are connected to a VisualSVN Server instance using Remote Server Administration, you get the following error after clicking Browse:

Browse is not available when you are connected to the server remotely

The following sections describe how to specify a path in such cases and the permissions required for a remote VisualSVN Server instance to access it.

How to specify a path during remote connection

If you are connected to the server remotely, you can specify a path to a file or folder in one of the following formats:

  • If the target file or folder is stored locally on a remote computer, specify a local absolute path (in the context of the remote server) such as D:\MyFolder\.
  • If the desired file or folder is stored on a network share, specify a UNC path such as \\hostname.example.com\myshare\.
Note
If you are connected to the server remotely and the target file (or folder) is stored locally on your workstation, you cannot specify a path to that file. In that case, you should either copy the contents to the remote VisualSVN Server computer and access it by its local absolute path or make it available over the network and access it using the UNC path.

Permissions required to access a path during remote connection

When you are managing a server using VisualSVN Server Manager, the server uses impersonation to access files and folders on your behalf. Therefore, when you manage VisualSVN Server running on a remote computer and specify a path (for example, to import a repository) your account should have all the necessary permissions to access this path, because the operation will be performed under your current credentials.

See also

KB25: Configuring Remote Administration
KB22: Storing repositories on a network share

Last Modified: