Link to home
Start Free TrialLog in
Avatar of iTeam HelpDesk
iTeam HelpDesk

asked on

QFE Number mismatch

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.
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

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.
Avatar of iTeam HelpDesk
iTeam HelpDesk

ASKER

I have updated everything on both servers already and they both are on 6.3.96 Build 9600.  This did not resolve the issue.
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.
ASKER CERTIFIED SOLUTION
Avatar of iTeam HelpDesk
iTeam HelpDesk

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.