FCI SQL instance 2022 unable to start when named pipes is disabled

Hi Siva K

Thanks for using the Q&A platform.

When a Failover Cluster Instance of SQL Server cannot start with named pipes disabled, it’s because the cluster’s SQL server resource depends on named pipes and cannot come online without it.

The cluster network name resource, used by the FCI to establish health and dependencies, expects named pipes to function. Disabling it causes the SQL Server resource to fail its "IsAlive" checks, blocking startup. Find https://mskb.pkisolutions.com/kb/254321?

Keep named pipes enabled on your FCI, even if clients exclusively use TCP/IP over non-default ports; FCIs require named pipes for internal cluster operations.

If your security policy mandates disabling Named Pipes, consider:

• Migrating away from FCI to Always On Availability Groups (AGs), which don’t require Named Pipes. AG Listeners only use TCP/IP
• Or maintaining Named Pipes enabled, but restricting its use via firewall rules or ACLs to internal cluster nodes only.

Find additional documentation: https://learn.microsoft.com/en-us/sql/sql-server/failover-clusters/install/before-installing-failover-clustering?view=sql-server-ver17

If the response was helpful, please feel free to mark it as “Accepted Answer” and consider giving it an upvote. This also benefits others in the community.

Regards,

Obinna.