Failed to change listening port of SQL Server 2014 Failover Cluster

Want to check anyone had successfully changed the listening port of SQL Server 2014 Failover Cluster?

I used following steps but kept failing to startup SQL Server cluster again:

1. Use Get-ClusterResource -Name "SQLCLSTNM" | Remove-ClusterCheckpoint -CryptoCheckpoint

2. Change port number through SQL Server Configuration Manager on each node

3. Use Get-ClusterResource -Name "SQLCLSTNM" | Add-ClusterCheckpoint -CryptoCheckpointName "Microsoft Enhanced Cryptographic Provider v1.0" -CryptoCheckpointType 1 -CryptoCheckpointKey "......"

I even tried to stop the SQL Server cluster role before I tried step 1. The SQL Server cluster always stopped after several minutes waiting for SQL Server service come online. During the startup, I have checked SQL Server service status. It was actually already started. After several minutes, SQL Server failover cluster role will fail. And the SQL Server service was also terminated without any message in the ERROR log, not even any informational message.

The cluster runs perfectly fine once I revert it back to use 1433 port.

This is a three nodes cluster, SQL Server 2014 SP1 running on Windows Server 2012 R2, cross two different subnets.

May 18th, 2015 1:56am

1) which port you are using?

2) specific port iis open through firewall ?

3) telnet serverip portnumber => check

refer

http://blogs.msdn.com/b/sqlblog/archive/2009/07/17/how-to-configure-sql-server-to-listen-on-different-ports-on-different-ip-addresses.aspx


query :- 

USE master
GO
xp_readerrorlog 0, 1, N'Server is listening on' 
GO
CMD:-   netstat -ano | findstr *PID*

Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 2:19am

Hi Chen Liang,

Could you please check that if there are error messages in cluster log when SQL Server cluster fails to start? You can go to a command prompt and type 'cluster log /g', it will generate a cluster.log file in the c:\windows\cluster\reports folder. For more details about cluster  log, please review this blog.

Also please check that if you get the same issue as described in the following blog, if so, please configure an alias on each possible owner node and check if SQL Server cluster starts successfully.

Consideration for changing the default port of default SQL instance on Multi-subnet Failover Cluster
http://www.sqlserverfaq.net/2015/01/17/consideration-for-changing-the-default-port-of-default-sql-instance-on-multi-subnet-failover-cluster/

Thanks,
Lydia Zhang

If you have any feedback on our support, please click here.

May 18th, 2015 3:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics