Post reply

Database Mirroring Issue

  • October 17, 2017 at 6:13 am

    #402600

    Hello Team,
    I have a database which was mirroring currectly to DR successfully until the principal database crashed due to fried motherboard.
    MotherBoard has been replaced but mirroring has been difficult since then. the usual error i have been getting is 

    Msg 1418, Level 16, State 1, Line 1
    The server network address "TCP://FQDNDBNAME:xxxx" 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.

    I have followed all the options in https://www.sqlservercentral.com/Forums/Topic654643-146-1.aspx

    Please, can someone assist

  • October 17, 2017 at 6:23 am

    #1963995

    seyiisq - Tuesday, October 17, 2017 6:13 AM

    Hello Team,
    I have a database which was mirroring currectly to DR successfully until the principal database crashed due to fried motherboard.
    MotherBoard has been replaced but mirroring has been difficult since then. the usual error i have been getting is 

    Msg 1418, Level 16, State 1, Line 1
    The server network address "TCP://FQDNDBNAME:xxxx" 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.

    I have followed all the options in https://www.sqlservercentral.com/Forums/Topic654643-146-1.aspx

    Please, can someone assist

    Can you telnet to port 5022 from the source to destination server?

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

  • October 17, 2017 at 7:22 am

    #1964008

    Thanks SSChampion,
    The port i am using is not 5022. However, i cannot telnet to it. But i can telnet to the right port that was use to configure the end points

  • October 17, 2017 at 7:28 am

    #1964010

    seyiisq - Tuesday, October 17, 2017 7:22 AM

    Thanks SSChampion,
    The port i am using is not 5022. However, i cannot telnet to it. But i can telnet to the right port that was use to configure the end points

    ok great, that's a good start.
    Assuming you've checked that endpoints are in fact started, can you connect to the sql instance from primary to DR at all?
    You could also test if mirroring can be established using the IP address and not FQDN.

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle

  • October 17, 2017 at 7:46 am

    #1964014

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database dbname set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:46 am

    #1964015

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database DBNAME set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:46 am

    #1964016

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database dbname set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:46 am

    #1964017

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database DBNAM set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:46 am

    #1964018

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database dbname set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:46 am

    #1964019

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database DBNAME set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:47 am

    #1964020

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database dbname set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:47 am

    #1964021

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database DBName set partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 7:47 am

    #1964022

    Thanks for your response.Yes, the end point are started and I can connect to the DR instance from Primarymirror_endpoint_namelogin_name permission_name permission_state endpoint_stateMirroring DomainName\username CONNECT GRANT STARTEDFrom DR alter database DBNAMEset partner offALTER DATABASE DBNAME SET PARTNER = 'TCP://PrimaryIP:5xxx'; GOFrom Primary ALTER DATABASE DBNAME SET PARTNER = 'TCP://DRIP:5xxx'; GOI got same error as Msg 1418, Level 16, State 1, Line 6The server network address "TCP://DRIP:5xxx" 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.

  • October 17, 2017 at 8:18 am

    #1964031

    Thanks for your response.

    Yes, the end point are started and I can connect to the DR instance from Primary

    mirror_endpoint_name login_name permission_name permission_state endpoint_state
    Mirroring DomainName\username CONNECT GRANT STARTED

    From DR

    alter database DBNAME set partner off

    ALTER DATABASE DBNAME
    SET PARTNER = 'TCP://PrimaryIP:5xxx';
    GO

    From Primary

    ALTER DATABASE DBNAME
    SET PARTNER = 'TCP://DRIP:5xxx';
    GO

    I got same error as

    Msg 1418, Level 16, State 1, Line 6
    The server network address "TCP://DRIP:5xxx" 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.
    ------------------------------

  • October 17, 2017 at 8:56 am

    #1964041

    I found this error in the DR log 

    2017-10-17 15:26:52.92 Logon   Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed). State 67.'. [CLIENT: PRIMARY IP]

    I also, realize that the Process ID of the MSSQL server is different from the Process IP i got when i did a netstat

    C:\Users\sqlmirror>netstat -aon | findstr 1433
    TCP  0.0.0.0:1433     0.0.0.0:0     LISTENING   7512
    TCP  [::]:1433      [::]:0      LISTENING   7512


    So Netstat is seeing pid 7512 while config manager is seeing 7364 as attached. Could this be the cause
    I have also confirmed that the issue is not login issue as i can login using the credential attached to the end points

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply