SQL SERVER – Fix : Error: 1418 – Microsoft SQL Server – The server network address can not be reached or does not exist. Check the network address name and reissue the command

Error: 1418 – Microsoft SQL Server – The server network address can not be reached or does not exist. Check the network address name and reissue the command

The server network endpoint did not respond because the specified server network address cannot be reached or does not exist.

Fix/Workaround/Solution:

Step 1) Your system Firewall should not block SQL Server port.

Step 2) Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Network Configuration
Enable TCP/IP protocol. Make sure that SQL SERVER port is by Default 1433.

Just to make sure follow one more step which may or may not be necessary.

Step 3) Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Client Configuration
Enable TCP/IP protocol.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

About these ads

110 thoughts on “SQL SERVER – Fix : Error: 1418 – Microsoft SQL Server – The server network address can not be reached or does not exist. Check the network address name and reissue the command

  1. I have setup everything accordingly but still receiing the error. I have this error with database mirroring. The account I use is an domain admin account with full privileges on each server.

    That may have something to do with the VM ware server? all my 3 server involved in the mirroring operation are setup on the same VM server host.

    Any help, I will appreciate

    Like

  2. IMP: By default, some OS like Microsoft Windows XP Service Pack 2 and Windows Vista block all ports.!!so i sueggest to check the ports as well !

    NOte : Corrective action might be required on both partners
    .For example:

    # if this message is raised when you are trying to run SET PARTNER on the principal server instance, the message might imply that you only have to take corrective action on the mirror server instance. However, corrective actions might be required on both partners.

    #After resolving any issues ,
    rerun the ALTER DATABASE database_name SET PARTNER statement on the principal server.

    #Check this ,sys.database_mirroring_endpoints to diagnose the problem .

    I hope will inline your needs
    If you can dispalay a exact error which you encountred will be more helpful to diagnose !!

    Like

  3. This is exact error. I did the configuration set up as per you but still face the same problem. I have seen that the windows firewall services are not enabled in both of principal and Mirror servers.

    “Msg 1418, Level 16, State 1, Line 1
    The server network address “TCP://172.20.52.58:10111″ can not be reached or does not exist. Check the network address name and reissue the command.”

    Like

  4. I get the same 1418 error with my mirroring set up too. I have a domain user for all my services, I use the same account for my endpoints, have given this account full access, have checked tcp port to be 1433 on all three nodes (principal, mirror, witness), and I have granted connect permissions to this account.

    The Server log shows the account logging in and then out. A port monitor shows the listener for the sql service and when the partner is assigned on the mirror, the port monitor shows the attempt of the connection but it shuts down after a few seconds and ultimately fails.

    Like

  5. We tried all the above suggestions but still no luck. Is there anything additional we need to do so that we can enable mirroring? The two servers we are using is SQl server 2005 and both are in the same network. The ports we are using are in listening mode. Is this the right way or do we need to do any changes? Is there any way to test the pinging of the ports so that we can test the communications between to servers

    Like

  6. This is also ’caused when the mirroring endpoints do not have matching encryption methods.

    You can change this by altering your mirroring endpoints on both partners as shown below:

    “ALTER ENDPOINT Mirroring FOR DATA_MIRRORING (ROLE = PARTNER, ENCRYPTION = SUPPORTED)”

    Like

  7. We were using 2 different domain accounts… once we made them the same, and re-started the services, everythiong worked.

    ThomasLL

    Like

  8. Am also facing same error that is ” The Server Network address TCP://mirror:5023 can not be reached or doesnot exist . check the network address name and the ports for the local and remote endpoints are operational (Microsoft sql server error no: 1418) ”

    can any one help please … am waiting for you reply

    Like

  9. Am also facing same error that is The Server Network address TCP://mirror:5023 can not be reached or doesnot exist . check the network address name and the ports for the local and remote endpoints are operational (Microsoft sql server error no: 1418)

    can any one help please … am waiting for you reply

    Like

  10. Msg 1418, Level 16, State 1, Line 1
    The server network address “TCP://OFFICE:5023″ can not be reached or does not exist. I am having this message only establishing connectivity from principal to “mirror”. The other way around (from “mirror” to principle) worked fine.
    alter database dbXXX
    set partner = ‘TCP://OFFICE:5023′
    Any help would be greatly appreciated.

    Thanks,
    Vad

    Like

  11. I solved the problem by changing the way that instead of local system account i used domain user account that had rights on both servers !

    please try in Domain … it’s resolve that problem

    ” TCP://mirror:5023 can not be reached or doesnot exist . check the network address name and the ports for the local and remote endpoints are operational (Microsoft sql server error no: 1418) ”

    now is working fine …… if anybody want doc plz give your email id. i will send the doc step by step.

    Like

  12. Hi sureshhumar
    Plz send the document about step by step that you do
    i do mirroring step by step in sql help and all thing is ok till i want exec the Alter command on principle server that give us 1418 event error Id, i exec this command on mirror server and i don get any error.
    plz send you doc for me maybe this help me, this is my email : negeen_arya@yahoo.com

    Like

  13. Hi, I fixed the problem by adding the Principal Server’s Service Account (Domain account) to the Mirror SQL Server (As SQL Login) with ‘sysdba’ role. Then, this sttm was ran successfully :
    ALTER DATABASE LiteSpeedLocal SET PARTNER = ‘TCP://MirrorServer.Domain.Com:5022′

    Like

  14. I ran into the same thing, here’s how i did it.
    Do the same full backup of your primary and restore to your mirror. Be sure to restore in the “NO RECOVERY” mode. The DB will stay in restore mode. Once that is done, do a “Transaction Log backup” of your primary and then do a Trans restore to your mirror. At this point, you can go through the gui and setup your mirror. If at all possible, use the same domain account for the SQL service on both servers. Hope that helps.

    Like

  15. Sureshhumar,

    I have set domain name for both servers, TCP/IP enabled, andnamed Pipes enabled. I am still getting SQL server , error 1418.

    Could you please send me the document about step by step that you have mentioned.

    Thanks

    Like

  16. Hi Guys!
    I am trying to do the mirroring on two different servers, but i am getting error 1418, tcp & namedpipe also enabled.if i am trying in on two different instance on same server, then it works sucsessfully,

    any one can help me on this

    Like

  17. How about posting the DOC here. As many people that are having the problem whouldn’t it just be easier than having to send it to everyone?

    Like

  18. I’m having the same problem as everyone else. I get the 1418 error, using the same domain id on both servers.
    Please send me your documentation at

    Like

  19. Hallo Sureshhumar,
    send please the doc for the error 1418, this is a katastroph, an Microsoft a debakel.
    Thank you for this script.

    Volker

    Like

  20. Hi Suresh,

    I am facing same mirroring problem using SQL Server 2008 Standard. Can you send your document please? Thanks in advance!

    Kyle

    Like

  21. Hi suresh,

    I need to know if can set Mirroring in two server with :

    Principal Server: SQLSERVER2005 SP3 EE
    Partner: SQLSERVER2008 SP RTM

    you think that I can set mirror in two servers?

    Like

  22. Working solution.

    1. Start MSSQLSERVER Services with Domain user credentials (instead of Local System Account) on principal database Server and Mirror Database Server.

    Note: To switch from “Local System Account” to Domain User credentials do the following (a).

    a) On Windows (XP or Server): Start -> Control Panel -> Administrative tools -> Services. Then right click on SQL Server (MSSQLSERVER). Then click on properties. And then click on tab “Log On”. And then choose radio button “this account”. Then provide the Domain user name and password.

    If you want repeat (a) for all SQLSERVER related Services.

    2. And then try the mirroring process in MS SQL Server Management Studio.

    Like

    • Awesome. Your solution worked for me. I just made sure that all the sql server services of different instances use the same windows login account that I use to log into my computer.

      Like

  23. I had the same issue and my two servers are on the same domain with no local or physical firewalls in between. Nothing to do with ports in my case. It was simply that I had not used the correct Domain accounts. I also ensured the two accounts used were local admin on both boxes (not sure if this is necessary). Worked fine after that. Im mirroring from a cluster by the way. Lets see how it looks in a week.

    Like

  24. I’ve tried all this but still got the error 1418
    Check if your sql user has sysadmin rights under login in SQL Management Console. My account was setup with only public rights. It did work once I added sysadmin rights on the domain user running the SQL service. Hope that helps

    Like

  25. I had the exact same problem. Was already using the same domain account to run SQL Service on both principal and mirror. Already had the firewalls open on both.

    I was able to set partner on mirror with principal as target, but I would get the above mentioned error 1418 when trying to set partner on principal with mirror as target.

    What fixed it for me was adding the SQL service domain account to the local admins group on both the principal and the mirror.

    Thanks.

    Like

  26. Hi Suresh,

    I have the same problem configuring SQL server 2008 R2 mirrroing, can you send me the document ?

    Error: “The server network address “TCP://servername: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)”

    Thanks,
    Laxman

    Like

  27. Seems like some people were able to fix this problem. but, ’till this date nobody was able to post a how to on this page.

    A little how to about 10 lines or so would benefit all feature readers.

    thanks.

    Like

  28. I’ve read every post in this thread, and it is still failing for me.
    – Put both computers in a domain.
    – Put a domain user in the local admin group of both computers.
    – Booted under that domain user.
    – Run all SQL services under that domain user.
    – Created a SQL user in SSMS of that domain user, and granted sysadmin rights.
    – Attempt to configure mirroring; still get error 1418.

    Like

  29. I got the same error when I set a mirroring with certificates between two untrusted domain can you please send the those too.

    Thank you

    Like

  30. HI to all,
    I have configured like,
    -two computers in same domain
    – started all the mssqlserver and agent services(principle and mirror) under same domain account
    created the mssqlserver security logins with sysadmin privs
    followed the backup and steps restore steps properly
    Attempt to configure mirroring; still getting same error 1418.

    Hi suresh,

    Please send database mirror document to my mail id

    thanks,
    J.Raghu

    Like

  31. I used the default accounts in SQL 2012 install which presumably is the network account. Both computers are in the same domain. I then used the two machine accounts on both computers:

    domain\machine1$
    domain\machine2$

    That resolved the error for me.

    Like

  32. If your machines are not in a domain, take a look at this http://blogs.msdn.com/b/suhde/archive/2009/07/13/step-by-step-guide-to-configure-database-mirroring-between-sql-server-instances-in-a-workgroup.aspx it worked just fine for me.

    For this case cenario seems to exist another simpler solution explained here http://www.kendalvandyke.com/2011/12/database-mirroring-in-windows-workgroup.html but i did not manage to put it to work using that solution.

    Best regards :)

    Like

  33. Hi Anyone help me to get solve this issue? 1418 …

    Same domain, full access ( sysadmin) for the domain users who has priv on both servers. fire walls off… END point are set.. still same problem..

    Like

  34. HI everybody, im having the same problem with our nemesis (1418) i have 2 instances in the same machine ( win server 2008) , dns, ports check, firewall check, norecovery mode check……..

    Like

  35. Hi,
    I was trying to set mirror without using domain accounts. So I had Sql server service running on both principal and mirror server(no witness)under administrator account which I had with the same password. Telnet on 5022 on both servers worked fine, but I was getting 1418 error. In that case the problem for sure was with the permissions. I found that I couldn’t login to one of the servers using windows authentication and user: administrator. I created that login and gave it sysadmin server role. I loged in as administrator in sql studio and after that and mirror was established.

    Like

  36. Solution: If your using local accounts
    1. Change Service accounts for MSSQL server from Local System to Administrator Account ( Principalserver\Administrator and Mirrorserver\Administrator)
    2. Restart the Mirroring

    Like

  37. I could fix it by doing the following:
    1- using Domain user has admin right to run both of SQL Service and SQL Agent in (Principal, Witness, and Mirroring) Servers.
    2- Restart all serivices
    3- Drop Current openned EndPoints and recreat them once again using TSQL or SSMS wizard itself.
    4-Check the Encryption box for all servers (Principal, Witness, Mirror)

    Hope this help

    Like

  38. Subhajit
    Hi, everyone,
    After several months searching i today solved the problem. If above all are ok, i mean –
    1) All end points for principal, mirror, witness server instance are listening properly and status is started for all instances.
    2) Same domain account has been created for all instances and sysadmin permission has been given.

    Then last thing to do is :

    3) add NT AUTHORITY\NETWORK SERVICE login account for both mirror, principal and witness server instances and make sure it has sysadmin server role permission. That’s it. This solves my problem. I hope this will solve the problems of many.

    Thank you. :)

    Like

  39. hi,
    I m facing 1418 error in db mirroring
    TCP://mirror:5023 can not be reached or doesnot exist . check the network address name and the ports for the local and remote endpoints are operational (Microsoft sql server error no: 1418)

    can you please send me how to create one login in another instance and the same in another instance…..

    Like

  40. I was having exactly same problem and tried all the steps mentioned above. But this dint work, Since i was using test environment, Added another instance on the same server and still found the same issue for error 1418 for tcp. Looked at the services and my server service and Browser service were using NTAuthority \ network servcie account, changed these to Domain user ( i added the user as sysadmin) and it started working. Hope you will find this helpful.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s