SQL Server Journey with SQL Authority

http://blog.sqlauthority.com/2010/01/11/the-server-network-address-tcpsqlserver5023-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-microso/

 

 

While doing SQL Mirroring, we receive the following as the most common error:

The server network address “TCP://SQLServer:5023″ cannot 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)

The solution to the above problem is very simple and as follows.

Fix/WorkAround/Solution: Try all the suggestions one by one.

Suggestion 1: Make sure that on Mirror Server the database is restored with NO RECOVERY option (This is the most common problem).

Suggestion 2: Make sure that from Principal the latest LOG backup is restored to mirror server. (Attempt this one more time even though the full backup has been restored recently).

Suggestion 3: Check if you can telnet to your ports using command TELNET ServerName Ports like “telnet SQLServerName 5023″.

Suggestion 4: Make sure your firewall is turned off.

Suggestion 5: Verify that the endpoints are started on the partners by using the state or state_desc column the of the sys.database_mirroring_endpoints catalog view. You can start end point by executing an ALTER ENDPOINT statement.

Suggestion 6: Try the following command as one of the last options.

GRANT CONNECT ON ENDPOINT::Mirroring TO ALL

Suggestion 7: Delete the end points and recreate them.

If any of above solutions does not fix your problem, do leave comment here. Based on the comment, I will update this article with additional suggestions.

Please note that some of the above suggestions can be security threat to your system. Please use them responsibly and review your system with security expert in your company.

Reference: Pinal Dave (http://blog.SQLAuthority.com), Many thanks to Solid Quality Mentors (http://www.solidq.com) for their valuable suggestions.

these are really helpful and pretty good solutions, I remember one of the case right now, if your both SQL Servers are not in one domain rather than both are in same workgroup and this error comes up and doesn’t resolve with any of the above suggestions, you should go for mirroring with certificate.

Disable the firewall services by going to Run > services.msc (hit ‘Enter’) and disabling/stopping windows Firewall.

I have a principal and mirror, in 2005. I set up the mirror site in recovery mode. I keep seeing references about restoring the log file to the mirror, after the database is restored in recovery mode. I cannot do that in MS, and it would probably fail in t-sql. Also, I have endpoints on both databases. When I do a set partner, on the mirror it says it is already set up for mirroring. It says the endpoint is started.

SELECT role_desc, state_desc FROM sys.database_mirroring_endpoints says partner and started for both.

SELECT type_desc, port FROM sys.tcp_endpoints says
DATABASE_MIRRORING and 5022 form both

There is no firewall involved, the telnet works both ways. I am at a lose. Can you suggest something else.
The sql service service is set to local. Should I change it, and if so, to what. Also, both accounts are local, not domain accounts. Any light you could shed on this would
be appreciated.