locked
Getting error when setting up mirroring RRS feed

  • Question

  • Getting error setting up an endpoint. I have already taken backup of principle and restored to mirror with no recovery and also did the same with transaction log. I have set up the end points too and when I actually configure the mirroring i am getting an error on the endpoints. 

    For SQL Server 2012, what are the recommended ports for principle. witness, mirror. I am using 7022, 7023, and 7024


    • Edited by Gorkhali Monday, November 11, 2013 1:05 AM
    Monday, November 11, 2013 1:02 AM

Answers

  • Hi,

    The EndPoints should be as below if you are using Port 7022. Please note that the domain account user for authorization should be same for both the end points.

    For e.g considering the below ip addresses for Principal and Mirror server:

    Principal: 190.165.10.20

    Mirror: 190.165.10.30

    To check whether the Ports are open from both sides, execute the below cmd command after the creation of the endpoints:

    On Principal server execute the below:

    Telnet 190.165.10.30 7022

    On Mirror server execute the below:

    Telnet 190.165.10.20 7022

    CREATE ENDPOINT [ME_Principal]
     AUTHORIZATION [your domain account]
     STATE=STARTED
     AS TCP (LISTENER_PORT = 7023, LISTENER_IP = ALL)
     FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
    , ENCRYPTION = REQUIRED ALGORITHM RC4)
    GO

    CREATE ENDPOINT [ME_Mirror]
     AUTHORIZATION [your domain account]
     STATE=STARTED
     AS TCP (LISTENER_PORT = 7023, LISTENER_IP = ALL)
     FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
    , ENCRYPTION = REQUIRED ALGORITHM RC4)
    GO


    Thanks and Regards Alankar Chakravorty MCITP Database Administrator SQL Server 2008 MCITP Database Administrator SQL Server 2005

    • Marked as answer by Sofiya Li Thursday, November 21, 2013 9:56 AM
    Wednesday, November 13, 2013 11:59 PM
  • Hi Gorkhali

    Try assigning Connect privileges to each SQL Service account to the other instance's endpoint (even if they are the same). This will fix your problem.


    Regards,
    Mark Broadbent.

    Contact me through (twitter|blog|SQLCloud)

    Please click "Propose As Answer" if a post solves your problem
    or "Vote As Helpful" if a post has been useful to you
    Watch my sessions at the PASS Summit 2012 and SQLBits

    • Marked as answer by Sofiya Li Thursday, November 21, 2013 9:56 AM
    Saturday, November 16, 2013 7:14 PM

All replies

  • What is exactly error message  you are getting from?

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Monday, November 11, 2013 6:37 AM
  • by default 5022 is the port used for Database mirroring,buy you can use 7022,7023,7024 port without any problem,

    check the below

    1. did you add the following ports in exception in firewall
    2. check the FQDN(FUlly Qualified Domain Name)
    3. try by replacing the Server Name with its IP Address

    Ramesh Babu Vavilla MCTS,MSBI

    • Proposed as answer by Sofiya Li Tuesday, November 12, 2013 9:13 AM
    Monday, November 11, 2013 6:40 AM
  • what is that error message plz?

    Also try the below one to see something can help

    Troubleshoot Database Mirroring Configuration (SQL Server)
    http://technet.microsoft.com/en-us/library/ms189127.aspx


    Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

    Monday, November 11, 2013 5:26 PM
  • Hi,

    The EndPoints should be as below if you are using Port 7022. Please note that the domain account user for authorization should be same for both the end points.

    For e.g considering the below ip addresses for Principal and Mirror server:

    Principal: 190.165.10.20

    Mirror: 190.165.10.30

    To check whether the Ports are open from both sides, execute the below cmd command after the creation of the endpoints:

    On Principal server execute the below:

    Telnet 190.165.10.30 7022

    On Mirror server execute the below:

    Telnet 190.165.10.20 7022

    CREATE ENDPOINT [ME_Principal]
     AUTHORIZATION [your domain account]
     STATE=STARTED
     AS TCP (LISTENER_PORT = 7023, LISTENER_IP = ALL)
     FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
    , ENCRYPTION = REQUIRED ALGORITHM RC4)
    GO

    CREATE ENDPOINT [ME_Mirror]
     AUTHORIZATION [your domain account]
     STATE=STARTED
     AS TCP (LISTENER_PORT = 7023, LISTENER_IP = ALL)
     FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
    , ENCRYPTION = REQUIRED ALGORITHM RC4)
    GO


    Thanks and Regards Alankar Chakravorty MCITP Database Administrator SQL Server 2008 MCITP Database Administrator SQL Server 2005

    • Marked as answer by Sofiya Li Thursday, November 21, 2013 9:56 AM
    Wednesday, November 13, 2013 11:59 PM
  • Hi Gorkhali

    Try assigning Connect privileges to each SQL Service account to the other instance's endpoint (even if they are the same). This will fix your problem.


    Regards,
    Mark Broadbent.

    Contact me through (twitter|blog|SQLCloud)

    Please click "Propose As Answer" if a post solves your problem
    or "Vote As Helpful" if a post has been useful to you
    Watch my sessions at the PASS Summit 2012 and SQLBits

    • Marked as answer by Sofiya Li Thursday, November 21, 2013 9:56 AM
    Saturday, November 16, 2013 7:14 PM