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)
pinaldave
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
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 !!
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.”
Hi I want to add one thing here that I don’t have administrator rights in the mirror server m\c. Would this really matter?
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.
I have the above problems too….
After try and error and some readings, i fix the problem……
Hope this help everyone:
http://alan328.com/SQL2005_Database_Mirroring_Tutorial.aspx
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
Thanks Alen328 That worked fine.
Above mentioned SQL settings are there by default (after installed SQL 2005).
I am having the same problem for SQL 2005 mirroring.
am getting error
the database principal does not exists
during the system copy of SAP
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)”
We were using 2 different domain accounts… once we made them the same, and re-started the services, everythiong worked.
ThomasLL
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
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
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
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.
Hi,
I saw you fix the DB mirroring TCP port problem by using domain user. Could you send me the detail document? Will your solution work if this is a home PC without domain?
Regards,
Marco
HI
I can get the problem. Plz send me the mirroring document
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
hi
please send the documet about step by step that you do
this is my emai
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′
please send me step by step thaaaaaaaaaaanks
can you send me a step-by-step instruction to fix the error 1418.
thanks.
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.
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