Azure Files Storage Transaction Errors. Looking for insight

Question

Hi All

I am looking for feedback on couple of persistent errors I see in my Azure Files Storage account. It's configured for premium and dedicated to FSLogix profiles for an AVD host pool. See screenshot for details. I have two errors that generate a lot of logs data; clientothererror and treeconnect. My Google Fu is failing me on an answer to these errors.

I don't see any disk or profile errors in any of the session hosts, so it may be nothing but we are about to go live with this setup and need to validate what I am seeing.

Any thoughts?

Answer 1

@Vasco365 Firstly, Apologies for the delay response!

Based on the error message, please refer to this article Storage Analytics logged operations and status messages & Microsoft Q&A thread which gives idea on your issue

ClientOtherError: The "ClientOtherError" is a relatively generic error message that could indicate various issues occurring at the client-side when interacting with Azure Files Storage. This error message might not provide specific details about the underlying problem.

To troubleshoot this error:

• Check if there's any client-side network connectivity issue that might be causing intermittent disruptions.
• Ensure that you're using the correct authentication credentials when accessing the Azure Files Storage.
• Monitor the Azure portal for any associated alerts, status changes, or resource health issues related to your storage account.
• Review the client application logs or event logs for more specific error details.

TreeConnect: The "TreeConnect" error typically pertains to SMB (Server Message Block) protocol-related issues. SMB is the protocol used by Windows operating systems for file and printer sharing. A "TreeConnect" error might indicate that there's an issue with establishing or maintaining a connection to a shared resource (in this case, Azure Files Storage) using the SMB protocol.

To address this error:

• Ensure that your AVD host pool VMs are properly configured to connect to Azure Files Storage using SMB.
• Verify that the SMB version and configuration on your VMs are compatible with Azure Files requirements.
• Check if there are any firewall rules or network configurations that might be blocking or disrupting SMB traffic between your VMs and Azure Files Storage.
• Review the Azure Files Storage configuration to ensure that it's set up correctly for SMB access.

In order to debug this further, you can use Azure storage logging which would log information about every operation performed against your storage account. It will include the HTTP code of every response.

Here is a list of common status codes. Many (not all) 300-400 level HTTP status code will result in ClientOtherError.

File here seems to have similar API's that can result in ClientOtherError when the file is missing.

This may require a deeper investigation, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email toAzCommunity[at]Microsoft[dot]com referencing this thread. Please mention "ATTN subm" in the subject field and subscription ID. Thank you for your cooperation on this matter and look forward to your reply.

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

---

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