Issue with Azure File Sync Server Registration

Question

Hello,

The issue concerns the registration of the file server with the Azure File Sync service.

The StorageSyncAgent_WS2016.msi agent was installed on a fully updated Windows Server 2016 file server. It meets the requirements described in the Microsoft documentation here.

The server has been restarted, and a repair of the agent has been performed. However, the error message "Could not load file or assembly 'System.Net.Http, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The specified file could not be found." persists.

The logs do not provide additional information beyond this error message. It seems to be related to a .NET issue, but I cannot find further details on the subject.

Answer 1

Hello @Axel GLEIZES

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

As per my understanding, you're unable to register the Azure File Sync agent in a Windows Server 2016 machine.

Usually, this error may be caused due to some updates missing. Did you check if you have the following ones installed?

• Windows Server 2012 R2: KB5021653
• Windows Server 2016: KB5040562
• Windows Server 2019: KB5005112 and KB5040430

For reference: https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal

Please, feel free to tag me if you have further questions.

Have a great week ahead.

Answer 2

Hi @Axel GLEIZES

Welcome to Microsoft Q&A, thanks for posting your query.
Adding additional information for the above response.

The error "Could not load file or assembly 'System.Net.Http, Version=4.2.0.0" indicates that the missing version of the System.Net.Http assembly requires your application. This issue occurs when an application depends on an outdated .NET Framework version or the necessary assembly dependencies are not properly resolved.

 

• Confirm the server has .NET Framework 4.8 installed, as this is required for the Azure File Sync agent on Windows Server 2016. 
• Fix or Update the ⁠System.Net.Http Assembly might be incorrectly registered. Use the Microsoft Assembly Binding Log Viewer (Fuslogvw.exe) to identify any errors related to missing or incorrect assemblies. Ensure the correct version of System.Net.Http is available by installing it using NuGet or updating your environment to include the required version. https://learn.microsoft.com/en-us/dotnet/framework/tools/fuslogvw-exe-assembly-binding-log-viewer  
• If your application has an App.config or Web.config file, you can add binding redirects to ensure that any requests for older versions of System.Net.Http are redirected to the correct version
• Uninstall the Azure File Sync agent completely, restart the server, and then download and install the latest version of the agent from Microsoft's download page.
• ⁠If the issue persists, locate the System.Net.Http.dll file from a compatible .NET installation or NuGet package and manually place it in the application's directory or the Global Assembly Cache (GAC).
• ⁠Confirm all available Windows updates have been installed, as some updates may include important fixes for .NET Framework and its dependencies.

⁠Additional Troubleshooting:

• Check the Event Viewer under Applications and Services Logs > Microsoft > FileSync for detailed error messages that may provide more details about the issue.
• If the problem remains unresolved, please check the Microsoft documentations for additional guidance.
  Azure Files troubleshooting documentation
  https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal#install-the-azure-file-sync-agent

 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.