KB: Assigning NetApp Storage to a Hyper-V Cluster fails with Error 26184 in System Center 2012 Virtual Machine Manager

KB: Assigning NetApp Storage to a Hyper-V Cluster fails with Error 26184 in System Center 2012 Virtual Machine Manager

  • Comments 1
  • Likes

imageHere’s a new Knowledge Base article we published. This one talks about an issue where an Operations Manager AD Replication Monitor generates an "Invalid Script Parameter Configuration" error message.



You are able to successfully add NetApp storage to System Center 2012 Virtual Machine Manager (VMM) and create the LUN’s but when trying to assign the available storage to a Hyper-V cluster, the job fails with the error below:

Error (20400)
1 parallel subtasks failed during execution.

Error (26184)
The Storage Group existing for <Cluster Name> doesn’t match storage group setting at array <Storage>.
Recommended Action - Make sure storage group setting set at storage array matches storage groups created for cluster.

Trace Details:

1131,02:32:21.151 05-16-2012,0x0638,0x08A4,19,ParallelSubtaskContainer.cs,135,0x00000000,Microsoft.VirtualManager.Utils.CarmineException: The Storage Group existing for <Cluster Name>doesn't match storage group setting at array <SAN01>.

Make sure storage group setting set at storage array matches storage groups created for cluster.

Server stack trace:
at Microsoft.VirtualManager.Engine.ImageLibrary.StrgLun.Unmask(List`1 strgLuns; String groupName; List`1 initiators; List`1 targets)
at Microsoft.VirtualManager.Engine.Adhc.MaskingHelper.Unmask(List`1 strgLuns)
at Microsoft.VirtualManager.Engine.Adhc.RegisterStorageLunToClusterSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run() 01166 at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.OnAsyncChildStart(ISubtask childToRun)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md; Object[] args; Object server; Int32 methodPtr; Boolean fExecuteInContext; Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg; IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg; Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed; MessageData& msgData)
at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.RunSubtaskDelegate.EndInvoke(IAsyncResult result)
at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.ProcessCompletedSubtaskNoLock(AsyncSubtaskHandle subtaskHandle) at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.ProcessCompletedSubtask(Guid subtaskId)
at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.WaitForSubtaskCompletion(Guid asyncSubtaskId)
at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainer.RunSubtaskScheduler()

*** Carmine error was: StorageGroupSettingNotValidForHostOrCluster (26184)
*** CLUSTER NAME** <SAN01> **,{00000000-0000-0000-0000-000000000000},1,
1132,02:32:21.151 05-16-2012,0x0638,0x08A4,9,HostClusterTask.cs,503,0x00000000,error when setting cluster,{00000000-0000-0000-0000-000000000000},1,
1133,02:32:21.151 05-16-2012,0x0638,0x08A4,9,HostClusterTask.cs,503,0x00000000,Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskException: 1 parallel subtasks failed during execution.
at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.ThrowParallelSubtaskExceptionIfRequired()
at Microsoft.VirtualManager.Engine.TaskRepository.ParallelSubtaskContainerBase.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.Adhc.SetHostClusterTask.ExecuteStorageSubtasks()
at Microsoft.VirtualManager.Engine.Adhc.SetHostClusterTask.RunSubtask()
** Carmine error was: ParallelSubtaskContainerChildrenFailed (20400)
*** 1 **,{00000000-0000-0000-0000-000000000000},1,

1134,02:32:21.151 05-16-2012,0x0638,0x08A4,19,Task.cs,270,0x00000000,Task failed error ParallelSubtaskContainerChildrenFailed (20400) with exception Microsoft.VirtualManager.Utils.CarmineException: 1 parallel subtasks failed during execution.
at Microsoft.VirtualManager.Engine.Adhc.SetHostClusterTask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
*** Carmine error was: ParallelSubtaskContainerChildrenFailed (20400)
*** 1 **,{37b08eb1-13d7-4be4-aa5e-d26cefb35b73},1,


This can occur if there is more than one Storage initiator group assigned per Cluster node.


To resolve this issue follow the steps below:

1. Reduce the Storage initiator groups to one per cluster node in NetApp storage.
2. To get the changes reflected in the VMM server, we need to Remove and re-add the storage device in the VMM console.
3. In the VMM console, from the Fabric pane, remove the storage device.
4. Verify the Storage removal job completed successfully.
5. On the Home tab, in the Add group, click Add Resources and then click Storage Devices. The Add Storage Devices Wizard starts.
6. Provided the required details and add the storage device.

Now you need to configure the storage classification and storage pools again. After that you should be able to assign the available to storage to a Hyper-V cluster in the VMM console.

More Information

Configuring Storage Overview: http://technet.microsoft.com/en-us/library/gg610600.aspx


For the most current version of this article please see the following:

2725377 - Assigning NetApp Storage to a Hyper-V Cluster fails with Error 26184 in System Center 2012 Virtual Machine Manager

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I am seeing this same issue with a Server 2012 R2 iSCSI target server connected via SMI-S WMI to VMM. Any ideas how to resolve it?