I recently had a problem where I could not delete and remove a server endpoint under a cloud endpoint in Azure File Sync. The provisioning for server endpoint failed and canceled.
The error I had is the following:
- Server job with command name NewServerEndpointWithDatePolicy and id 3897b10c-ba4f-4dd1-888d-795863076042 failed with -2134376427.
When this sort of thing happens in Azure File Sync, you suspect that there’s a problem with the storagesync filter, which you can investigate using fltmc.exe. I am running the latest release of the sync agent (at the time of this writing it’s version 4.1). However, I was able to set up sync groups with the same registered server and different sync path without any issue.
So what is the difference for this particular sync group?
After a bit of investigation, I found out that I have another server endpoint was already using that path (e.g. Sync group A with server endpoint X and path D:\App\Export, and Sync group B with the same server endpoint and path D:\App). In this case, the path is overlapping between the two sync groups.
To delete the server endpoint that’s in the provisioning canceled state, right-click the server endpoint as shown in the following screenshot and select delete. Then type the name of the server endpoint to confirm, and finally click Delete.
When the server endpoint is deleted, you can go ahead and remove the overlap between the path and then add it again.
Hope this helps someone out there!
Thank you for reading my blog.
If you have any questions or feedback, please leave a comment.