After upgrading my SMB3 based file server from Windows 2012 to Windows 2012 R2 I missed that the file server was now in an Unknown status in VMM within the Fabric pane, Storage, File Server section. While the file server continued to function correctly, I was unable to add any other file shares on the server due to an error refreshing the Windows file server storage.

The errors which were occurring were: Error (26571): Cannot refresh the Windows file server storage provider hyperv02.cloud.pvt because the storage provider has atleast one file server that has not been successfully created yet.
Reads storage provider error.jpg

Restarting the job was the recommended action but that did not resolve the issue. In the VMM 2012 R2 release notes I found the following information: (available at http://technet.microsoft.com/en-us/library/dn303329.aspx).

File servers under management will go into an unknown state after upgrade

Description: After upgrading from VMM in System Center 2012 SP1 to VMM in System Center 2012 R2, existing file servers under management will go into an Unknown state. Refreshing the Windows file server storage provider that is hosting the file server will fail, and an error message "Cannot refresh the Windows file server storage provider <name> because the storage provider has at least one file server that has not been successfully created yet" will be displayed.

Workaround: Remove and then re-add the Windows file server storage provider hosting the file server. Lastly, re-add the file shares under VMM management.

 

Detailed resolution steps:

Based upon the release notes I verified that my SMB3 file server was in an Unknown state as shown below. The screenshot below shows that the file server is in an Unknown status.

In my environment, the file server was in use for my virtuals so I shut down all non-required virtuals and migrated any remaining ones to local storage just in case the removal of the file server caused issues. Additionally, I took a screenshot of the current file shares (shown above) to make sure that they were re-added correctly.

To remove the windows file server storage, open the Fabric pane, Storage, Providers section. Right-click on the provider and choose remove.

The successfully completed task (Removes Storage Provider) is shown below from the Jobs pane.

Once the provider was removed, the file server was removed also as shown below.

To re-add the file server open the Fabric pane, storage, providers and Add Storage Devices. Go through the wizard and add the original file server.

In the wizard there is a step to select shares to place under management by VMM. The screenshot below shows that each of my originally managed shares were listed (virtuals, VirtualShare1, VirtualShare2, DeduplicatedVirtualDrive) and the new share was also available (TieredStorage).

After successfully re-adding the file server and the file shares, they were working as expected and shown below (I missed one which I later added which was the "Virtuals" item shown below as No for managed, but was able to change the properties of that share to Yes for managed).

Summary: I had been concerned that implementing this workaround to change my file server from an unknown state to ok was going to cause significant interruptions in my environment but the change was very straightforward and was implemented without any issues in my lab environment.