Share via

Unable to provision a network drive as Server Endpoint in Azure File Sync

Tushar Tarkas 26 Reputation points
2022-12-21T11:49:52.793+00:00

I've provisioned Azure Files and have multiple shares in there. I want to sync the data in Azure Files to remote Windows Server. I've registered Azure Files & the Windows Server in Azure File Sync Service. When I tested synchronization for one of the shares with a local folder on the Windows server, it worked as expected.

However, I want to sync data from Azure Files to a drive which is a network drive mapped to the Windows Server. For such a folder, the addition of server endpoint fails with error mentioned below. Additional information for both the network drive & Windows Server is that they are in a separate AD domain.

Validating input
Preparing Azure file share
Creating Server Endpoint
Creating Azure file share snapshot
Granting server access
Updating sync configuration
Enabling sync
The operation 'Create server endpoint' failed with the following error: The server could not apply the new configuration. Additional information: Operation identifier: 89d314ef-3b4a-4862-9362-bc332033a145 Server identifier: 24845fe7-3258-4f3d-99ce-443d7c975c9f Error code: 0x80C87012 MgmtServerJobFailed Server error: 0x80070002

Can you please suggest how to get this working.

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,425 questions
Azure Storage
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,543 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
3,202 questions
0 comments
Accepted answer
  1. Sumarigo-MSFT 47,471 Reputation points Microsoft Employee Moderator
    2022-12-27T04:27:14.597+00:00

    @Tushar Tarkas Adding more information to the above response!

    Based on the error message Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2147024894 or 0x80070002)
    This error occurs if the server endpoint path specified is not valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync does not support mapped drives as a server endpoint path.

    You may also refer here How to add a server endpoint and also check that you have the latest Azure File sync agent

    Additional information :Troubleshoot Azure File Sync

    This error code occurs if the server is offline or doesn't have network connectivity.

    Please let us know if you have any further queries. I’m happy to assist you further.

    ----------

    Please do not forget to 274157-accept-answer.png and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    2 people found this answer helpful.

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. TP 125.9K Reputation points Volunteer Moderator
    2022-12-22T13:37:27.6+00:00

    Hi,

    Short Answer: Only local paths are supported for server endpoints.

    Some key points:

    • You mentioned you want to sync with a mapped network drive. I'm assuming you mapped a drive while you were logged on to the server, and then entered that drive letter and path when attempting to create the server endpoint. For example, you had G: mapped to a share on a different server, and entered G:\Data when creating the endpoint. In this example, G: only exists in the context of your user session, running under your user account. It doesn't exist as far as the file sync service is concerned, which is running in different session (0) under SYSTEM account, which is why you received a file not found error (0x80070002)
    • Continuing the example. Let's say G: drive somehow did exist in the context of the file sync service, maybe not as G: but as a UNC path (\server\share). The service wouldn't have permission to connect to the share, since it is running under SYSTEM.
    • The file sync service uses the change journal, and this can only be accessed for local volumes

    -TP

    2 people found this answer helpful.
    0 comments
  2. JimmySalian-2011 42,511 Reputation points
    2022-12-21T12:21:53.55+00:00

    Hi,

    I will suggest you to go through the deployment process of the Azure File Share and Sync to configure as per the required documents - file-sync-planning

    file-sync-deployment-guide

    Also check the troubleshooting guide over here file-sync-troubleshoot

    Hope this helps.
    JS

    ==
    Please Accept the answer if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.
    0 comments
  3. Luke Murray 11,436 Reputation points MVP Volunteer Moderator
    2022-12-22T05:26:56.897+00:00

    I believe only local folders are allowed through Azure File Sync - not mapped drives (although I have never tried it).

    You could potentially get away with using a mapped drive - by using a Symbolic link - https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

    But be wary of the complexity this adds to troubleshooting.

    1 person found this answer helpful.
    0 comments
  4. Tushar Tarkas 26 Reputation points
    2022-12-21T13:01:20.987+00:00

    Thanks Jimmy for quick response. Basically, are mapped drives supported as Server End Point folders?

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.