arcserve-KB : WARNING: SQL Server instance uses different ports on Master() hosts.

Last Update: 2015-12-15 22:08:08 UTC

XOSOFT Replication: 12.0, 12.5
Last Modified Date:    03/10/2010
Document ID:    TEC509844
Tech Document
Title:  WARNING: SQL Server instance uses different ports on Master( ) hosts.


After creating a new CA XOsoft High Availability for MS SQL scenario you encounter an error indicating that the ports on the Master don't match the ports on the Replica server. This error is referencing the TCP/IP ports assigned to the IP's in the SQL Server Configuration Manager. The clients and applications connecting to the MS SQL instance are configured to initiate the connection using a specific protocol. In this case, those configured to connect using the TCP/IP protocol will connect to the Master on the TCP port that is assigned to the SQL instance on the Master. The MS SQL instance on the Replica will need to be assigned the same port number in order to be able to listen to incoming connection requests by users when a switchover occurs and the Replica becomes the active server.


The Replica instance of MS SQL will need to be assigned the same port as the Master instance of MS SQL. The users and applications will already be configured to use the port which is currently assigned to the active production server, which is typically the Master server.

  1. Logon to the Replica server.

  2. Open SQL Server Configuration Manager.

  3. Select SQL Server Network Configuration.

  4. Select the Protocols for MSSQLSERVER (Or the Specific SQL instance you're trying to replicate).

  5. 'Right-Click' the TCP/IP Protocol and select PROPERTIES.

  6. Select the IP Addresses Tab.

  7. Remove the zero (0) from the TCP Dynamic Ports field from all the appropriate interfaces, including the IPALL field.

  8. Assign the same port as the Master in the TCP Port field on all the appropriate interfaces which is assigned to your SQL instance.

    Figure 1

  9. Select Apply and OK.

  10. You will need to stop and restart the MSSQL Services to enable the changes.

  11. Restart the CA XOsoft scenario. The error should now no longer occur.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request