locked
Mirroring error RRS feed

  • Question

  • Dear all,

    I'm trying to set up mirroring and I get the following error, I have run the following to check if the ports are able to open cmd-> telnet servername 5022 but the issue is still there. Would you please let me know what else I can try please?

    The server network address "TCP://servername.test.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. (.Net SqlClient Data Provider)

    Friday, December 6, 2013 12:05 PM

Answers

  • check the below

    1. principle and mirror servers are started with same user namep
    2. ping <mirrored server IP>
    3. check that port is not blocked by firewall
    4. check that port is not blocked by anti virus

    check the link for more info on this error

    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/


    Ramesh Babu Vavilla MCTS,MSBI

    • Proposed as answer by Sofiya Li Tuesday, December 10, 2013 2:37 AM
    • Marked as answer by Sofiya Li Monday, December 16, 2013 8:52 AM
    Friday, December 6, 2013 12:12 PM
  • Dear all,

    I'm trying to set up mirroring and I get the following error, I have run the following to check if the ports are able to open cmd-> telnet servername 5022 but the issue is still there. Would you please let me know what else I can try please?

    The server network address "TCP://servername.test.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. (.Net SqlClient Data Provider)

    Hello,

    There can be many reasons for this error.This can also come when SQL server service account is different on both principal and mirror.In my case was so.When i changed it to same it worked.

    Please read this doc carefully and follow all steps to remove the error

    http://technet.microsoft.com/en-us/library/ms189127.aspx

    Hope this helps


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    • Proposed as answer by Sofiya Li Tuesday, December 10, 2013 2:37 AM
    • Marked as answer by Sofiya Li Monday, December 16, 2013 8:52 AM
    Friday, December 6, 2013 12:25 PM

All replies

  • check the below

    1. principle and mirror servers are started with same user namep
    2. ping <mirrored server IP>
    3. check that port is not blocked by firewall
    4. check that port is not blocked by anti virus

    check the link for more info on this error

    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/


    Ramesh Babu Vavilla MCTS,MSBI

    • Proposed as answer by Sofiya Li Tuesday, December 10, 2013 2:37 AM
    • Marked as answer by Sofiya Li Monday, December 16, 2013 8:52 AM
    Friday, December 6, 2013 12:12 PM
  • Dear all,

    I'm trying to set up mirroring and I get the following error, I have run the following to check if the ports are able to open cmd-> telnet servername 5022 but the issue is still there. Would you please let me know what else I can try please?

    The server network address "TCP://servername.test.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. (.Net SqlClient Data Provider)

    Hello,

    There can be many reasons for this error.This can also come when SQL server service account is different on both principal and mirror.In my case was so.When i changed it to same it worked.

    Please read this doc carefully and follow all steps to remove the error

    http://technet.microsoft.com/en-us/library/ms189127.aspx

    Hope this helps


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    • Proposed as answer by Sofiya Li Tuesday, December 10, 2013 2:37 AM
    • Marked as answer by Sofiya Li Monday, December 16, 2013 8:52 AM
    Friday, December 6, 2013 12:25 PM
  • To complete the answers,If your sql server instances run under different domain account, don't forget to GRANR the CONNECT authorization on the MIRRORING endpoint to the SQL service account of both instances on the corrisponding server

    http://technet.microsoft.com/en-us/library/ms187811(v=sql.105).aspx

    Regards.

    Tuesday, December 10, 2013 2:44 PM