QFE Number mismatch

iTeam HelpDesk
iTeam HelpDesk used Ask the Experts™
on
I keep getting Failover Cluster Validations failures and can't seem to figure out what the issue is.  Thank you for your asistance.  Here are the details.  (2) Server 2012 R2 Data Center with (1) MSA 2040 Direct Fiber with 10GB iSCSI Card.  The "Validate Microsoft MPIO-based disks" are failing with this error.

===============================
Node 1
Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
Microsoft DSM 6 3 9600 17401

Getting information about registered device-specific modules (DSMs) from node 2

Node 2
Device-specific module (DSM) Name Major Version Minor Version Product Build QFE Number
Microsoft DSM 6 3 9600 0

For the device-specific module (DSM) named Microsoft DSM, versions do not match between node 1 and node 2
For the device-specific module (DSM) named Microsoft DSM, versions do not match between node 2 and node 1
===============================

The only thing I see different is the QFE number but I cant seem to figure out why.  the mpclaim shows them as both using Microsoft DSM.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018

Commented:
Microsoft-provided in-box providers can be updated via windows update. 6.3.9600 was RTM. One of your nodes has an updated patch and the other is still at RTM. Windows update is your friend here.

Author

Commented:
I have updated everything on both servers already and they both are on 6.3.96 Build 9600.  This did not resolve the issue.
Distinguished Expert 2018

Commented:
17041 isn't RTM. As I recall, that was the May 2014 refresh. Make sure that is installed. Check the update list specifically. Precedence or 3rd party patch management (such as WSUS) can cause an update to not appear, but another node build from refreshed media or built in a NOC before deployment can have different patches.
So I figured out what happened.  When I found that my updates were legit and there were no more available updates from microsoft, I decided to uninstall MPIO and Reinstall and I ran into an issue where I couldn't uninstall it.  So I researched the issue and this is what I found.  Reinstalled MPIO and this resolved the original issue on this question.  So all I can guess is that it was a faulty install on Node 2 for the MPIO.  I don't use 3rd party patch management as this time since this was a new server and had not setup any yet.  All my updates were direct from Microsoft.  Here is the solution I found that resolved the issue.  This was exactly the issue that I was experiencing with my QFE being "0"
http://rlevchenko.com/2013/08/18/fix-cant-re-install-mpio-feature-on-server-2012failed-mpio-cluster-test/

Author

Commented:
I am accepting my own answer becuase the issue was a faulty MPIO install which could only be repaired by a registry fix so I could reinstall the MPIO.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial