FIX: "SODA File Server Clone failed. Error=0x80070057" error when a failover of the virtual machines starts on a Windows Server 2012-based Hyper-V failover cluster

Applies to: Windows Server 2012 StandardWindows Server 2012 Standard

Symptoms


Assume that you deploy a Windows Server 2012-based Hyper-V failover cluster that is based on a Scale-Out File Server cluster. When a failover of the virtual machines starts, the Vmms.exe process tries to access the file share or to unregister the virtual machines. In this situation, the Vmms.exe process stops responding. Moreover, virtual machines are left in a running-critical state on one or multiple Hyper-V host nodes and are unusable.

Additionally, the following event is logged in the System log:

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: date
Event ID: 1603
Task Category: File Server Resource
Level: Error
Keywords:
User: SYSTEM
Computer: computer_name
Description:
SODA File Server Clone failed. Error=0x80070057.

Cause


This problem occurs when a Scale-Out File Server clone resource tries to add Server Message Block (SMB) shares before the Distributed Network Name clone resource has added the network name to the SMB server name list. This causes the SMB shares not to be created as expected.

Resolution


This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.



Restart requirement

You may have to restart the computer after you apply this hotfix. 

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.