SQL SERVER – Rule Windows Server 2003 FILESTREAM Hotfix Check failed on Windows 2012 R2 Cluster

For my upcoming training, I was trying to deploy SQL Server 2008 R2 Cluster in my client’s lab machines. I encountered a strange error and I was clueless. Let us learn about Rule Windows Server 2003 FILESTREAM Hotfix Check failed on Windows 2012 R2 Cluster.

I tried below:

1. Ran cluster validation- it was all green
2. I even download the patch mentioned, but as expected, it was only for the 2003 OS.

I looked into the setup logs and found below

2013-02-04 10:51:05 Slp: Initializing rule : Windows Server 2003 FILESTREAM Hotfix Check
2016-09-06 10:51:05 SQLEngine: –FilestreamRequiredClusterPatchFacet: Engine_FilestreamRequiredHotfixesCheck: Version: 5.2.3790.4083
2016-09-06 10:51:05 SQLEngine: –FilestreamRequiredClusterPatchFacet: Engine_FilestreamRequiredHotfixesCheck: C:\Windows\system32\Drivers\Clusdisk.sys version : 6.2.9200.16384
2016-09-06 10:51:05 SQLEngine: –FilestreamRequiredClusterPatchFacet: Engine_FilestreamRequiredHotfixesCheck: C:\Windows\Cluster\Clusres.dll version : 6.2.9200.16384
2016-09-06 10:51:05 Slp: C:\Windows\system32\W03a2409.dll
2016-09-06 10:51:05 Slp: Rule initialization failed – hence the rule result is assigned as Failed
2016-09-06 10:51:05 Slp: Send result to channel : RulesEngineNotificationChannel

Later I came across Using SQL Server in Windows 8 and later versions of Windows operating system. It pointed me to the direction where it mentioned that we should do a slipstream of the media.

SOLUTION/WORKAROUND

I did a slipstreaming of SQL Server 2008 R2 media using KB How to update or slipstream an installation of SQL Server 2008. Once I slipstreamed the media, I was able to install 2 nodes SQL Server failover cluster.

Have you seen any such incorrect messages with SQL Server?

Reference: Pinal Dave (http://blog.sqlauthority.com)

First appeared on SQL SERVER – Rule Windows Server 2003 FILESTREAM Hotfix Check failed on Windows 2012 R2 Cluster