The server network address can not be reached or does not exist

Thursday, April 03, 2008 2:23 PM

0

Hi all



    When i am trying to configure Mirroring .i am getting the below error.

The server network address "TCP://RDEEPA:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)

. TCP/IP and Name pipe connection is enabled in both principle and mirror server configuration.

I post the complete error message below ,which is in red

TITLE: Database Properties
------------------------------

An error occurred while starting mirroring.

------------------------------
ADDITIONAL INFORMATION:

Alter failed for Database 'success'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&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://RDEEPA:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)

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

------------------------------
BUTTONS:

OK
------------------------------
- Reply
- Quote

All Replies

Thursday, April 03, 2008 3:04 PM

Moderator

1

Did you restore the Full backup and 1 tran log backup in mirror server using the With Norecovery clause ? If you did that and still face this error then I would suggest you to try using different port number other than 5022. Refer the below links,
http://msdn2.microsoft.com/en-us/library/ms189127.aspx
http://msdn2.microsoft.com/en-us/library/aa337361.aspx

- Deepak
- Reply
- Quote

Friday, April 04, 2008 4:56 AM

Moderator

ganeshkuppuswamy wrote:

The server network address "TCP://RDEEPA:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)

Hi,

While configuring mirroring you need to provide the server name in FQDN format (i.e computer.constono.com or use ipaddress) and make sure whether you have created correct alias of mirror server in the principal and vise vera.

You can refer the below link to configure db mirroring.

Database Mirroring

Saturday, April 05, 2008 8:45 AM

did u solve the error. If yes then i request u to share your results.

Infact i face the same problem

regards

cmrhema

Saturday, April 05, 2008 10:50 AM

Moderator

Hema,

Did you try using different port number while creating endpoint. May be the existing ports would have been in use and hence the error.

- Deepak

Monday, April 07, 2008 12:48 PM

Deepak

I tried with diferent Port number also but I am getting the same error . I working on fixing those issue. After finishing i will post the answer.

Tuesday, April 08, 2008 5:16 AM

can you show your code ?

Maybe the port was block, use telnet command to confirm.

Or the server does not have permission to connect the port.

Proposed As Answer by Carlos U Wednesday, February 11, 2009 9:27 PM

Wednesday, February 11, 2009 9:27 PM

i had this error, to fix it i removed the EndPoint in both server and started the process from the begging and everything works fine. TCP and name pipes must be available in both servers.

Proposed As Answer by Carlos U Wednesday, February 11, 2009 9:28 PM

Thursday, February 12, 2009 9:11 AM

With such errors there are several different possibilites that can cause the problem, depending on your environment and configuration. I've posted a list of a number of different things you should check here:

http://blogs.msdn.com/grahamk/archive/2008/12/08/database-mirroring-error-1418-troubleshooter.aspx

Graham Kent [MSFT]
SQL Server Support Escalation Engineer
http://blogs.msdn.com/grahamk

All postings are provided "AS IS" with no warranties, and confers no rights

Friday, February 27, 2009 6:43 PM

Here is the answer

I checked my networking configuration. I check my firewall settings. I pinged one server from the other and vice versa. I used telnet to connect to the endpoint port from one server to the other. All seemed fine, so I was a little frustrated. After reviewing all my steps and re-checking the documentation, I figured it out: I had not use the required "WITH NORECOVERY" option when restoring the database on the mirror. Once I did that, everything worked!

Amazing how an error message can point you the wrong way...

http://blogs.technet.com/josebda/archive/2007/06/11/misleading-error-1418-message-in-sql-server-database-mirroring.aspx

Tuesday, April 07, 2009 9:17 AM

Hi,
I have the same problem with SQL Server SP3.
1. I disabled the firewall.
2. I pinged one server from the other and works.
3. The port are opened, I can connect to one server from the other with telnet command.
4. I restored the database with the "WITH NORECOVERY" option
5. I tried with diferent ports
5b) TCP and named pipe are enabled in both servers.
6. The command from the mirror server is:

ALTER DATABASE BD



    SET PARTNER = 



    'TCP://MAINSERVER:7022'



GO

and this command works perfectly! The problem is execute the command from the principal server:

ALTER DATABASE BD



    SET PARTNER = 



    'TCP://MIRRORSERVER:7022'



GO

   This commands return the same error:
   Msg 1418, Level 16, State 1, Line 1
   The server network address "TCP://MIRRORSERVER:7022" 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.

Did someone found the solution?

Thanks

Tuesday, June 09, 2009 7:01 PM

Hi,

I have the same problem. However beginning over and over again and using other ports did not solve this unfortunately.

Here is the SQL I used to setup the mirroring.

* Principal DB
CREATE ENDPOINT [MirroringEndpoint]
    AUTHORIZATION [DOMAIN\administrator]
    STATE=STARTED
    AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
    FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)

BACKUP DATABASE TEST
    TO DISK = 'C:\full-backup.bak'
    WITH FORMAT

BACKUP LOG TEST
    TO DISK = 'C:\log.bak'

ALTER DATABASE TEST SET PARTNER ='tcp://sql2.domain.local:5022';

* Mirroring DB
CREATE ENDPOINT [MirroringEndpoint]
    AUTHORIZATION [DOMAIN\administrator]
    STATE=STARTED
    AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
    FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)

RESTORE DATABASE TEST
    FROM DISK = 'C:\full-backup.bak'
    WITH NORECOVERY

RESTORE LOG TEST
    FROM DISK = 'C:\log.bak'
    WITH FILE=1, NORECOVERY

ALTER DATABASE TEST SET PARTNER ='tcp://sql1.domain.local:5022';

The last statement on the principal server gives me the following error :

Msg 1418, Level 16, State 1, Line 1
The server network address "tcp://sql2.domain.local: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.

From the principal server I'm able to ping the mirror server and can establish a telnet connection. When the statement gets executed even netstat gives me the following output :

TCP    0.0.0.0:5022           0.0.0.0:0              LISTENING       1244 [sqlservr.exe]
...
TCP    10.1.1.140:5022       10.1.1.110:1223       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1226       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1216       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1218       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1225       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1222       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1221       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1224       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1219       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1220       TIME_WAIT       0

Is it normal so many ports get opened?

Any help would be greatly appreciated (as this drives me crazy :-( )

Proposed As Answer by bert_verhaeghe Monday, June 15, 2009 12:00 PM

Monday, June 15, 2009 12:04 PM

Hi,

I have the same problem. However beginning over and over again and using other ports did not solve this unfortunately.

Here is the SQL I used to setup the mirroring.

* Principal DB
CREATE ENDPOINT [MirroringEndpoint]
    AUTHORIZATION [DOMAIN\administrator]
    STATE=STARTED
    AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
    FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)

BACKUP DATABASE TEST
    TO DISK = 'C:\full-backup.bak'
    WITH FORMAT

BACKUP LOG TEST
    TO DISK = 'C:\log.bak'

ALTER DATABASE TEST SET PARTNER ='tcp://sql2.domain.local:5022';

* Mirroring DB
CREATE ENDPOINT [MirroringEndpoint]
    AUTHORIZATION [DOMAIN\administrator]
    STATE=STARTED
    AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
    FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)

RESTORE DATABASE TEST
    FROM DISK = 'C:\full-backup.bak'
    WITH NORECOVERY

RESTORE LOG TEST
    FROM DISK = 'C:\log.bak'
    WITH FILE=1, NORECOVERY

ALTER DATABASE TEST SET PARTNER ='tcp://sql1.domain.local:5022';

The last statement on the principal server gives me the following error :

Msg 1418, Level 16, State 1, Line 1
The server network address "tcp://sql2.domain.local: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.

From the principal server I'm able to ping the mirror server and can establish a telnet connection. When the statement gets executed even netstat gives me the following output :

TCP    0.0.0.0:5022           0.0.0.0:0              LISTENING       1244 [sqlservr.exe]
...
TCP    10.1.1.140:5022       10.1.1.110:1223       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1226       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1216       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1218       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1225       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1222       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1221       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1224       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1219       TIME_WAIT       0
TCP    10.1.1.140:5022       10.1.1.110:1220       TIME_WAIT       0

Is it normal so many ports get opened?

Any help would be greatly appreciated (as this drives me crazy :-( )

Found the problem eventually. The mirroring ran as the NT_AUTORITY user instead of DOMAIN\administrator.

Friday, July 31, 2009 5:35 AM

I am having the same issue and I can't figure it out.
Would you mind sharing how you changed the mirroring to run as Domain\administrator instead of NT_AUTHORITY?
Can you also specify how to check which user it is running under?

Wednesday, May 05, 2010 1:26 PM

The SQL Server and SQL Server Agent windows services must be changed....

Monday, February 07, 2011 7:02 AM

Also getting same error.

"SQLSERVER DBA" "INDIA"

Wednesday, March 23, 2011 3:24 PM

I was having this same problem. Retoresing the database with the NORECOVERY clause to the mirror server resolved the issue for me.

Thanks for the help.

Andrew

Wednesday, March 23, 2011 4:10 PM

Please check the account which using endpoints does it have enough permissions to communicate principal , mirror and witness servers?

Can you able to telnet on port 5022 between above three servers? more likely service account permission issues

Wednesday, September 28, 2011 2:41 AM

I had the same problem. When I restored to the secondary with no recovery and then ran the mirror wizard from the primary it said it couldn't connect to the database on the secondary.

Wednesday, September 28, 2011 1:11 PM

Moderator

Hi,

If you want to setup database mirroring using Windows Authentication mode, you need to add each other server's service account as a login, and grant it with CONNECT permission on the mirroring endpoints. For more information, see the following Books Online documentation: http://technet.microsoft.com/en-us/library/ms175883.aspx.

If you are using built-in Windows account such as LocalSystem or Network Service, please use computer account instead. For more information, see my blog post: http://ifcsong.wordpress.com/2011/05/23/configuring-sql-server-service-account-security-for-network-resources-access/.

Best Regards
Alex Feng

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Tuesday, January 08, 2013 7:20 AM

Thank you Alex Feng