question

PisethBen-3120 avatar image
0 Votes"
PisethBen-3120 asked CarrinWu-MSFT commented

Error SQL Mirroring configuration "The server network address "TCP://xxxx:5022" can not be reached or does not exist"

Hello All, I faced an issue while trying to configure SQL mirroring. Here is the message error:

====================================
The server network address "TCP://xxxx:5022" 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.
====================================

Here is the statement that I run set partner on primary, and got the error.

===================================
USE MASTER; GO ALTER DATABASE ADP SET PARTNER = 'TCP://xxxx:5022' GO
===================================

Note: I already run set partner on standby.

Thanks, Piseth

sql-server-general
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, we have not get a reply from you. Did the answers could help you? If there has an answer helped, do "Accept Answer". If it is not work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

0 Votes 0 ·
ErlandSommarskog avatar image
0 Votes"
ErlandSommarskog answered ErlandSommarskog commented

So is the other machine listening on port 5022?

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, the both machines are listening on port 5022.

0 Votes 0 ·

That is good to know.

Tells us what other troubleshooting did you do? Remember, we don't know anything about your environment, so we don't know why you think this should work.

0 Votes 0 ·
CarrinWu-MSFT avatar image
0 Votes"
CarrinWu-MSFT answered CarrinWu-MSFT edited

Hi @PisethBen-3120,

This error happens when the server network endpoint did not respond because the specified server network cannot be reached or it does not exist. You could check the following items once:

  1. Goto services.msc and check the sql server is running under which account. Make sure that sql server and sql server agent services should run with same credentials.

  2. in the mirror database server you should do the same step as step 1. Give the same credentials as in principal server. If that user is not present create a new one on the both servers with same credentials.

  3. Now got principal server and in sql server add the new login under Security-->Login. Give the server roles as Sysadmin and public. Add the same user on the mirror server also.

  4. Now do the mirror in the principal database. You did not get any error there.

Please refer to How to resolve Error: 1418 in sql server while mirroring to get more details.

Best regards,
Carrin


If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Ben-Miller-DBAduck avatar image
0 Votes"
Ben-Miller-DBAduck answered

Make sure of the following 2 things.

Endpoint is started on the server that you want to connect to.
Firewall ports are open between the 2 servers for 5022.

If these are fixed, then we can go from there. Does not exist indicates that it cannot see it, so either the port is wrong on the receiver or the firewall is blocking it.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.