Azure File Sync - Server endpoint errors

G. Jongeneel 0 Reputation points
2024-03-26T19:27:23.7766667+00:00

Since March, 14th there are errors within Azure File Sync. Sync sessions fail to finish. It shows two errors for Upload health and Download health. Both show:

Error code: 0x80C86053

Issue: Namespace tiering cannot run in the current state of the system.

We tried all kinds of troubleshooting, but no solution so far. May be it is related to the 17.2 version of the agent? Please support.

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,697 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. G. Jongeneel 0 Reputation points
    2024-03-27T11:51:39.3333333+00:00

    Hi @KarishmaTiwari-MSFT ,

    Yes, AZ PowerShell has been installed and these are the settings on the specific storage account:
    User's image

    However, it still shows as Unhealthy and with the same errors.

  2. KarishmaTiwari-MSFT 18,527 Reputation points Microsoft Employee
    2024-04-22T16:41:20.4266667+00:00

    G. Jongeneel
    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

    Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

    Issue: Azure File Sync - Server endpoint errors
    Error code: 0x80C86053

    Issue: Namespace tiering cannot run in the current state of the system.

    Solution: Customer shared - "I reinstalled the agent and used the following procedure:

    1. Delete all server endpoints in the sync group.
    2. Delete the cloud endpoint.
    3. Delete the sync group.
    4. If cloud tiering was enabled on a server endpoint, delete the orphaned tiered files on the server by performing the steps documented in the Tiered files are not accessible on the server after deleting a server endpoint section.
    5. Recreate the sync group.

    Then I had to add the (public) IP address of the on-prem file server to the firewall of the storage account to allow the sync. The problem is solved (or repaired) now."

    If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.

    0 comments