Unable to Add an SOFS Storage on the System Centre 2012 R2 Virtual Machine Manager Server


The set up in this case was that we had a two node Windows Storage Server 2012 R2 based Scale Out File Server Cluster.

When we were trying to add this SOFS Storage in VMM using the "Add Storage Devices Wizard" we were getting the following error at the stage "Discover and import storage device information":

Storage discovery of provider {0869e333-12f6-44c7-b6b7-7139530a18c9} for user usramdom\svc.vmm failed from 101VMM01.magnetek.com with error code 46010.

Specify valid provider, port and user credentials for storage discovery. ID: 26101.

As we do on most of the VMM cases , we collected the VMM Debug ETL tracing in this case as well using the steps mentioned in the article below:



After collecting the VMM logs, we analysed the trace logs and saw the errors below:


569 [0]053C.139C::‎2016‎-‎01‎-‎28 11:04:23.065 [Microsoft-VirtualMachineManager-Debug]4,4,SCXStorageService.cs,1578,Found provider TargetServer = , Name = Storage Spaces Management Provider, Type = 1, ObjectId = {1}\\101VMM01\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageProvider.ObjectId="{0869e333-12f6-44c7-b6b7-7139530a18c9}", URI = , UniqueId = {0869e333-12f6-44c7-b6b7-7139530a18c9}:101VMM01,{00000000-0000-0000-0000-000000000000}

580 [0]053C.139C::‎2016‎-‎01‎-‎28 11:04:24.174 [Microsoft-VirtualMachineManager-Debug]4,4,WsmanAPIWrapper.cs,2436,WinRM: URL: [http://101vmm01.magnetek.com:5985], Verb: [INVOKE], Method: [Discover], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/windows/storage/MSFT_StorageProvider?ObjectId={1}\\101VMM01\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageProvider.ObjectId="{0869e333-12f6-44c7-b6b7-7139530a18c9}"],{00000000-0000-0000-0000-000000000000}

1051 [0]053C.139C::‎2016‎-‎01‎-‎28 11:04:27.252 [Microsoft-VirtualMachineManager-Debug]4,4,SCXStorageService.cs,1984,SCX SMIS operation on provider {1}\\101VMM01\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageProvider. ObjectId="{0869e333-12f6-44c7-b6b7-7139530a18c9}" failed with CIMStatusCode CIMStatusCodeDescription from ErrorSource of ErrorSourceFormat and ErrorType with Message MessageArguments MessageID OtherErrorSourceFormat OtherErrorType PerceivedSeverity ProbableCause ProbableCauseDescription RecommendedActions OwningEntity ,{00000000-0000-0000-0000-000000000000}


Then I did some more research on the above Errors and found out that this type of issue can occur if there was an SOFS storage added earlier to the VMM server and was later removed, but it leaves some Registry entries behind, which causes this issue.

We had to look for ConnectionSubsystems Registry keys on the VMM server under the location below:




And there we found out that we had some entries from your Old SOFS cluster which was earlier added to VMM but then later removed from there. But these registry entries were still hanging in there due to some reason.We took the complete Backup of the Registry on VMM. Then we deleted the stale entries of the Old SOFS Cluster from the above Registry Key and then we rebooted the VMM server.

After that when we tried to add the new SOFS Storage on the VMM server, we could add it successfully now.

So, as you can see, the main issue here was the stale Storage registry entries which were still sticking there in the Registry due to some reason.



Nitin Singh

Support Escalation Engineer

Microsoft Security and Manageability Division