During cluster verification you can receive the following message:
Validate Microsoft-based MPIO disks – Failed
The main reason is that you have nodes with different MPIO driver version.
QFE Number is not the same on every nodes.
If you check driver properties (use device manager) you can verify this QFE
QFE version depends on OS patch level (installed SP , hotfixes or updates). In my case, I have the same patch level on every nodes. So , I decided to re-install mpio feature on every nodes (remove-windowsfeature). After succesfull uninstallation and server restart I couldn’t get MPIO back because of “ The request to add or remove features on the specified server failed. Installation of one or more roles,role services, or features failed. Error:0x800f0922″ .
Install-WindowsFeature uses DISM utility and has the same log files for troubleshooting. They are located in %systemroot%\Logs\DISM and %systemroot%\Logs\CBS. In logs I found some interesting strings:
“The device instance cannot be created because it already exists”
NICE! I understood that Install-WindowsFeature couldn’t delete this key and create some new ones. So, resolution is DELETE ROOT\MPIO and re-run Install-WindowsFeature. EASY AS PIE !? regedit.exe -> HKLM:\System\ControlSet001\Enum\MPIO -> right click -> delete = failure!
Of course, you cannot just delete these keys. I would recommend PSTools by Mark Russinovich (PSExec tool). This tool is able to enable “GOD MODE” for your registry :).
.\psexec.exe -i -d -s c:\windows\regedit.exe
That’s all! Problem has gone away!
6 thoughts on “Fix: Can’t re-install MPIO feature on Server 2012/Failed MPIO cluster test”
-Go into windows update within the control panel
-Enable updating for other microsoft products as well as receive recommended updates in the same way as critical updates
-check for new updates and apply outstanding microsoft related patches. This will bring QFE versions up to the latest revision
This removes the need to hack around in the registry.
Ian Kelso, you are right! But..
1) I had the same patch level
“QFE version depends on OS patch level (installed SP , hotfixes or updates). In my case, I have the same patch level on every nodes.”
2) only uninstallation solved problem.
Anyway, thanks for your comment!
Thanks a lot for this detailed information, it really helps me .
Thank you !!
I was wondering – What’s the potential impact of having different DSM versions?
well, the main point is having the same nodes in your cluster on all levels (patch, updates and etc.) even if you use 3rd party DSM..the version must be the same on every node. diff. DSM version = standalone hosts or diff.clusters