locked
Azure File Sync Error 0x80C87012 RRS feed

  • Question

  • When setting up Azure File Sync on a clustered file server with Azure Files I got this error: 

    The operation 'Create server endpoint' failed with the following error: The server could not apply the new configuration. Additional information: Operation identifier: 7431d352-6d7a-417b-8c39-66a047433236 Server identifier: e0470a56-9263-491f-97e7-951e6f97370a Error code: 0x80C87012 MgmtServerJobFailed Server error: 0x80C80328

    Looking at the logs (Applications -> Microsoft -> File Sync -> Management -> Operational I saw 

    Server Endpoint creation failed.

    Job ID: 7431d352-6d7a-417b-8c39-66a047433236
    Server Endpoint name: 48850143-02ad-4c1c-b122-6b3ea4d17ae3
    ErrorCode: 0x0x80c80328 - Choose a location that's on a drive formatted with the NTFS file system.

    I am using storage spaces direct on my cluster, which by default uses REFS as a file system. Reformatting to NTFS resolved the problem in case anyone else out there ran into it. 

    (This is a lab environment for a customer implementation I'm working on). 

    Hope this helps someone out there! 


    • Edited by YASWANTH MADI Tuesday, June 18, 2019 4:53 AM Resolved by the customer
    Monday, June 17, 2019 8:59 AM

Answers

  • A server endpoint can be created only on an NTFS volume. ReFs,FAT,FAT32 and other file systems currently not supported by Azure File Sync.

    Adding additional information:  before configuring the Azure file sync you can run the evaluation tool in the server endpoint to confirm the compatibility with the Azure File Sync. You can find here the steps https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning#evaluation-tool

    Glad to know that your issue has resolved. And thanks for sharing the solution, which might be beneficial to other community members reading this thread. 

    Kindly, let us know if you need any further assistance on this.



    • Edited by YASWANTH MADI Tuesday, June 18, 2019 4:53 AM
    • Proposed as answer by YASWANTH MADI Tuesday, June 18, 2019 4:53 AM
    • Marked as answer by D Langmead Friday, July 26, 2019 9:46 AM
    Tuesday, June 18, 2019 4:53 AM

All replies

  • A server endpoint can be created only on an NTFS volume. ReFs,FAT,FAT32 and other file systems currently not supported by Azure File Sync.

    Adding additional information:  before configuring the Azure file sync you can run the evaluation tool in the server endpoint to confirm the compatibility with the Azure File Sync. You can find here the steps https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning#evaluation-tool

    Glad to know that your issue has resolved. And thanks for sharing the solution, which might be beneficial to other community members reading this thread. 

    Kindly, let us know if you need any further assistance on this.



    • Edited by YASWANTH MADI Tuesday, June 18, 2019 4:53 AM
    • Proposed as answer by YASWANTH MADI Tuesday, June 18, 2019 4:53 AM
    • Marked as answer by D Langmead Friday, July 26, 2019 9:46 AM
    Tuesday, June 18, 2019 4:53 AM
  • Just checking in to see if the above answer helped. If this answers your query, do click “Mark as Answer” and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.


    Thursday, June 20, 2019 5:17 AM
  • Is there any update on the issue?

    If the suggested answer helped for your issue, do click on "Mark as Answer" and “Vote as Helpful” on the post that helps you, this can be beneficial to other community members.

    Wednesday, July 24, 2019 2:27 PM