I have a SQL 2017 Principal, Mirror and Witness that I'm trying to set up for high-availability. I've created certificates specifying port 7024 because the customer is running in a Workgroup and not a Domain. I keep getting the attached error when trying to start mirroring. I've tried specifying 7024 as the TCP port in the SQL Configuration Manager. Is there something I'm missing? Does the port for the Mirroring endpoint need to be different from the Principal? I've tried searching here for the same error but I'm getting mixed information about this.

enter image description here

The error message shown is:

The server network address "TCP://kb-versiosql1:7024" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)

closed as unclear what you're asking by Philᵀᴹ, Marco, Vérace, hot2use, McNets Jun 24 '18 at 19:41

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • does kb-versiosql1 resolve? – Philᵀᴹ Jun 18 '18 at 14:45
  • Yes but only because there's an entry in the Windows hosts file. All machines are visible across the network using either IPs or hostnames. – CymanSez Jun 18 '18 at 14:52
  • use Test-NetConnection docs.microsoft.com/en-us/powershell/module/nettcpip/… – Kin Shah Jun 18 '18 at 14:55
  • The port numbers can be the same if they are unused by any other application and these are different servers. Can you run a telnet on each participating server of the database mirroring to make sure you can talk to each server via that port. Also since you are using SQL 2017 hopefully enterprise, did you know SQL v.NEXT has the AG feature which does not require an underlying cluster? Database mirroring has been deprecated and soon no longer supported by Microsoft. – samosql Jun 18 '18 at 14:57
  • Yes, I'm aware of AG but unfortunately this cluster is running SQL Standard. I'll give telnet a try. – CymanSez Jun 18 '18 at 15:02

Thanks to everyone who commented! Your suggestions were all extremely helpful. I was able to re-trace my steps and did the following:

  • Made sure certificates were created for both partners, AND Witness authorized using the correct logins and '.cer' files.
    • Allowed CONNECT permission on login for remote mirroring endpoint.

This is not directly an answer to your question, but it might be something of interest to you. There are Basic Availability Groups in SQL Server 2016 and 2017 Standard Edition - a limited AG feature that may be suitable for some mirroring situations (see limitations).

Basic Availability Groups

  • Thanks, Blażej. Unfortunately we have 3 databases that need to be mirrored, which exceeds the limitation of Basic AG. – CymanSez Jun 20 '18 at 0:53

Not the answer you're looking for? Browse other questions tagged or ask your own question.