Comments on: SQL SERVER – The server network address “TCP://SQLServer:5023″ 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) 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/ Personal Notes of Pinal Dave Wed, 22 May 2013 19:03:49 +0000 hourly 1 http://wordpress.com/ By: SANA 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/#comment-471360 Wed, 08 May 2013 11:49:42 +0000 http://blog.sqlauthority.com/?p=7727#comment-471360 Hi Pinal,

I have performed all your 7 step, you mentioned in this post however i am still getting below error message.

- I am performing mirroring without Witness Server.
- without Domain
- 5022 Port used on both Sides
- With no service account

TITLE: Database Properties
——————————

An error occurred while starting mirroring.

——————————
ADDITIONAL INFORMATION:

Alter failed for Database ‘TESTDB’. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.3000.0+((SQL11_PCU_Main).121019-1325+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476

——————————

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

——————————

The server network address “TCP://WIN-KJTSN3JJT52: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. (Microsoft SQL Server, Error: 1418)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.3000&EvtSrc=MSSQLServer&EvtID=1418&LinkId=20476

——————————
BUTTONS:

OK
——————————

Optimistic response anticipated.

Regards,
Rigel Networks

]]> By: Kala 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/#comment-467965 Thu, 02 May 2013 20:55:56 +0000 http://blog.sqlauthority.com/?p=7727#comment-467965 My solution was… to remove duplicate endpoints. My starting situation was:
- instances server1\ABC and server2\ABC both with endpoints on port N, mirroring not enabled, but endpoints enabled
- new instances server1\XYZ and server2\XYZ with new endpoints, also on port N, also enabled – I was able to point server2\XYZ (mirror) to server1\XYZ (principal), but when trying reverse, it failed.
I checked about 20 things, including telnet, but then found that endpoints on ABC instances were already enabled – I just had to drop them to make mirror for XYZ work. (ABC will be decommissioned anyway – if that’s not the case for you, just use a different port)
Good luck!

]]> By: Anthony Stephens 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/#comment-464598 Fri, 26 Apr 2013 21:41:27 +0000 http://blog.sqlauthority.com/?p=7727#comment-464598 My solution was even more straight forward (kicking myself as I type) you must use the service account that the sql database engine us running under for database mirroring “Service Account” configuration page. I was using a service account that was created and dedicated for database mirroring with local admin permission on both servers and a member of the sysadmin group on both servers. I’m not sure why that wouldn’t work because this dedicated account was setup with permission to access the endpoint. Interesting.

Anyway changed the credentials to the service account that the database engine was using and all was well.

]]> By: KV 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/#comment-437330 Thu, 14 Mar 2013 17:31:48 +0000 http://blog.sqlauthority.com/?p=7727#comment-437330 Hello,
After struggling with the issue for several days, I was able to fix it as follows:
The key piece seemed to be that when you create an AWS instance, it automatically creates a DNS for the instance that looks like this IP-xxyyzzaa where xx,yy,zz,aa are the hex values for the ip v4 address when you do an ipconfig on the machine. So, on the primary, mirror and witness I changed the computer name to match the scheme. To verify that it worked, I did an nslookup IP-xxyyzzaa. It should return back the ip address of the machine and also the name IP-xxyyzzaa.ec2.internal. In the Configure Security Wizard, I used the name IP-xxyyzzaa.ec2.internal to connect to each machine. At the end of it Start Mittoring worked like a charm. To make sure that this was not a fluke, I repeated the procedure on 3 new machines and it worked without a hitch.

One thing to keep in mind is that it is good to have an elastic ip tied to these machines so the ip address does not change. Right now I do not have Elastic ip tied to these, so I will have to reconfigure mirroring when that happens.

Hope this helps. Please post questions, comments as you see fit. I will be checking back periodically.

Thanks
KV

]]> By: KV 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/#comment-437322 Thu, 14 Mar 2013 17:12:57 +0000 http://blog.sqlauthority.com/?p=7727#comment-437322 We did try the security groups with the help of ops but that did not end up fixing it. I have detailed below how I finally fixed it. Hopefully it will add t othe knowledge base.

Thanks Pinal and everyone else. This is a valuable resource.

]]> By: Moin 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/#comment-434794 Sun, 10 Mar 2013 08:16:57 +0000 http://blog.sqlauthority.com/?p=7727#comment-434794 Hello ,

I am getting same error message , I m trying to configure in workgroup environment , I tried with certificate but still getting same error

Thanks
Moin

]]> By: Crougar 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/#comment-433218 Thu, 07 Mar 2013 05:27:39 +0000 http://blog.sqlauthority.com/?p=7727#comment-433218 Right, if with dummy dbs on both principal & mirror with no data in them fails to get mirror setup – it has be to do with network.
You may want to open up security groups in AWS EC2 instances for 2way comms between all 3 instances – allow all tcp,all udp,all icmp comms between principal-mirror,principal-witness,mirror-witness if not then least 5022,5023 if using those alone.
Use both internal IP and elastic IP in SG configuration and test.

]]> By: Mayank 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/#comment-432952 Wed, 06 Mar 2013 16:17:06 +0000 http://blog.sqlauthority.com/?p=7727#comment-432952 In my case, SQL Service pack were different in both the servers. When that was taken care of, Mirroring worked like a charm.

]]> By: KV 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/#comment-432266 Tue, 05 Mar 2013 15:58:25 +0000 http://blog.sqlauthority.com/?p=7727#comment-432266 Thanks, Crougar, for your response
I tried it and it still fails. I think it might be a SecurityGroup issue.
Trying that.

]]> By: Crougar 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/#comment-431929 Tue, 05 Mar 2013 05:57:55 +0000 http://blog.sqlauthority.com/?p=7727#comment-431929 KV,
Suggest you try steps 1&2 again given above by Mr Pinal creating a dummy ‘Test’ SQL database on principal server instance. Backup full & backup transaction log of this dummy db (without data like tables, stored procedures etc so size will be very small of both backups) to rule out full backup & trans log backup related issues with setp. Certainly, most common problem in mirroring setup between 2 servers!

If setup still fails then this is network related issue so focus on suggestion 3 onwards given by Mr Pinal.

]]> By: KV 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/#comment-431664 Mon, 04 Mar 2013 19:54:54 +0000 http://blog.sqlauthority.com/?p=7727#comment-431664 Hello All,
I have got to the end of this post and still do not have a resolution. Here is my setup.3 Servers on AWS EC2 without a domain (one of them is a witness)
I have tried every thing that people have suggested here. Always end up with the 1418 error. The services are running on the same local account on both servers. The account has sysadmin access to the SQL server.
I have been at it not for about 4 days now. I ‘accidentally’ go it to work once ad had to expand the root drive on the servers. Now, it has stopped working.

I would appreciate any additional things I can try short of re-installing the SQL server. :-)

Thanks in advance.
KV

]]> By: dinn11 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/#comment-416205 Fri, 01 Feb 2013 09:47:04 +0000 http://blog.sqlauthority.com/?p=7727#comment-416205 My principal and mirror SQL server were running in AWS EC2 cloud (virtual environment similar to VMWARE) – we have a domain setup in there. I was getting same FQDN error. I resolved it by trying to running SQL Server services on both principal and mirror servers using a domain account (for test I used my own domain account) and then specifying the same in Mirroring Configuration step where it asks for accounts on both servers if domain account account is setup. Try it and let me know.

]]> By: SQL SERVER – Weekly Series – Memory Lane – #011 « 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/#comment-406705 Sat, 12 Jan 2013 01:31:11 +0000 http://blog.sqlauthority.com/?p=7727#comment-406705 [...] The server network address “TCP://SQLServer:5023″ can not be reached or does not exist. Check th… [...]

]]> By: Jeremy 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/#comment-383482 Thu, 29 Nov 2012 19:21:36 +0000 http://blog.sqlauthority.com/?p=7727#comment-383482 For all of you poor saps who got all the way down here and it’s STILL not working…I was in your boat. The fact of the matter was, Sql never started listening on my configured endpoint on the mirror partner.
Facts:
1. I tried multiple ports.
2. I turned OFF all firewalls.
3. I could NOT Telnet to my EndPoint port from any other machine – but COULD telnet to the Primary and Witness EndPoints from the problem machine.
4. Other machines COULD telnet to the default SQL 1433 port on the problem machine.

The Primary DB simply could NOT see it’s mirror partner’s EndPoint port – so I could *never* complete the setup.

The sad fact was, that after 7 hours of exhausting every possibility I could think of from hardware, to software – I gave up and UNINSTALLED and REINSTALLED Sql Server on the problem machine. The EndPoint started listening on the first try. Problem solved.

The takeway? Sql Server got itself munged up pretty well and wouldn’t start listening on any configured endpoint ports. I may never know why. And FYI – a SQl Repair didn’t fix it. It needed the nuclear option.

…Hope no one else gets to this point – but, it happens. And this fixed it.

]]> By: Uncle Bob 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/#comment-368887 Sun, 04 Nov 2012 01:57:16 +0000 http://blog.sqlauthority.com/?p=7727#comment-368887 At last I made it. The error 1418 disappeared. My configuration: two SQL servers without domain. This is my solution:
1. Create the same user account (e.g. SQL_mirr) with the same password and with standard priviledges on both Windows servers
2. In the system firewall allow communication via ports 1433 and 5022 (default SQL mirroring) on both servers
3. Set the SQL_mirr account as “Log on” at service MSSQLSERVER properties
4. Add SQL_mirr account with sysadmin priviledges on both MS SQL servers
The rest as standard: backup database with transactional log from principal server, restore backups to mirror server with RESTORE WITH NORECOVERY option and set mirroring via wizard or TransactSQL. It works with IP, FQDN, without FQDN in TCP://partner_server_address:5022 syntax.
Good luck! :)

]]> By: DAve 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/#comment-361948 Fri, 19 Oct 2012 10:15:26 +0000 http://blog.sqlauthority.com/?p=7727#comment-361948 Awesome! the sysadmin comment for the service accoutn ssolved my problem! thankyou!

]]> By: kyaw kyaw oo 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/#comment-361137 Wed, 17 Oct 2012 12:55:24 +0000 http://blog.sqlauthority.com/?p=7727#comment-361137 VV,

If you could telnet to 5022 port : telnet ipaddress 5022 is to confirm the firewall is not blocking. Tony is posted and it is the solution for error 1456 – if the DNS is not translated the host name properly.
Please edit the host file from witness server, and put ip address + host name for Principle, Mirror. That’s it !
Try from command line : ipconfig /flushdns

]]> By: vv 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/#comment-361131 Wed, 17 Oct 2012 12:29:24 +0000 http://blog.sqlauthority.com/?p=7727#comment-361131 Hi,
I tried all the options. First of all my firewall is off in Primary, mirroring and witness SQL server machines. Still I am getting the error that TCP://servicename:port is not acceible.

]]> By: kyaw kyaw oo 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/#comment-360413 Mon, 15 Oct 2012 18:10:47 +0000 http://blog.sqlauthority.com/?p=7727#comment-360413 I am stuck with error 1456 and I finally realize and found out after looking the post by Tony. The DNS-entries are not updated the changes of host name or IP address.
By running gpupdate on DNS server and the others SQL Servers (Principle, Mirror and Witness) could solve the problem without editing the hosts file.

]]> By: Bhola 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/#comment-358756 Thu, 11 Oct 2012 11:55:51 +0000 http://blog.sqlauthority.com/?p=7727#comment-358756 1. Check Firwall of System should not block SQL Server port.

2. SQL Server Configuration Manager –> Service and Application –> SQL Server 2005 Configuration Manager –> Network Configuration–>Enable TCP/IP protocol. Make sure that SQL SERVER port is by Default 1433.

3.SQL Server Configuration Manager –> Service and Application –> SQL Server 2005 Configuration Manager –> Client Configuration–Enable TCP/IP protocol.

]]> By: Sampath 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/#comment-357770 Tue, 09 Oct 2012 07:30:23 +0000 http://blog.sqlauthority.com/?p=7727#comment-357770 Sir,

Since 48 hrs I was struggling with 1418 Error. Tried all possibilities; but no luck. Please help me out.

]]> By: chetanschetan 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/#comment-357177 Mon, 08 Oct 2012 04:48:37 +0000 http://blog.sqlauthority.com/?p=7727#comment-357177 dear sir i am having one quiery
I am having two SQL servers 2008 at 2 diff location and connected with Lease line , my quiery is that if i make mirror using both server and suppose my lease line got dissconnected i want to use bot servers from their own location’s means server A will be used only by users who seat at loction A and server B database will used BY only location B users
is it possible means in mirrion one detabase is inaccessable it wnat to use both database in lease line failure condition

please help me to solve this issue

]]> By: wqweto 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/#comment-356586 Sat, 06 Oct 2012 19:55:27 +0000 http://blog.sqlauthority.com/?p=7727#comment-356586 Suggestion 7 can help if endpoints on both servers are using different ecryptions. If not specified, manually created endpoints use ENCRYPTION = DISABLED. Management studio creates endpoints with REQUIRE RC4 by default.

So script both endpoints in SSMS (drop+create) and compare ENCRYPTION option. Set both to DISABLED and apply.

]]> By: carla abanes (@carlingdoodling) 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/#comment-355407 Wed, 03 Oct 2012 09:21:51 +0000 http://blog.sqlauthority.com/?p=7727#comment-355407 thanks much for your post!! i solved my issue with your suggestion number 1!

]]> By: Dan Carvin 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/#comment-351913 Fri, 21 Sep 2012 18:37:55 +0000 http://blog.sqlauthority.com/?p=7727#comment-351913 I’m setting up mirroring on my home network for practice & MS Exam preparation. I am mirroring from a Server2008 VM on another computer to an Evaluation edition instance on Windows 7. There is no Active Directory domain. What seemed to work for me (after following clues in the SQL Error Log) was to add the SQL service accounts to Logins on the Servers themselves. I didn’t think you needed to do this.

]]>