locked
SQL Mirroring issues-2014- ENDPOINT or any other areas? RRS feed

  • Question

  • Opted to SQL Mirroring as HA solution because of the application to vendor support limitations. Current set up is 2008 R2 with mirroring as HA. Upgrading to 2014 and I have attempted to build mirroring between small databases first in 2014 set up. It's a failure with 1418 error. Both servers service accounts are same windows domain accounts and it has SA access. Restore DB FULL backup and Tran log back with with No Recovery option.

    I have did the same setup in 2008 R2 for multiple times.

    When I tried to DELETE the existed end points I got the below message. I was able to remove endpoint from mirror server.

    Any inputs will be greatly appreciated.

    When I tried to DELETE or CREATE endpoint at principal server I'm getting below error messages

    DROP ENDPOINT Mirroring 

    Msg 9644, Level 16, State 19, Line 17

    An error occurred in the service broker message dispatcher. Error: 41180, State: 20.

    When I tried to create a new endpoint with diff name I have received below error

    TITLE: Microsoft SQL Server
    ------------------------------

    SQL Server cannot create the mirroring endpoint, 'Mirroring_New'.

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

    Create failed for Endpoint 'Mirroring_New'.  (Microsoft.SqlServer.Smo)

    ------------------------------

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    An error occurred in the service broker message dispatcher. Error: 41180, State: 20. (Microsoft SQL Server, Error: 9644)


    ------------------------------



    • Edited by Kpvuppala Sunday, October 15, 2017 4:03 AM
    Sunday, October 15, 2017 3:52 AM

Answers

  • Restarting SQL services helped to create new endpoints.

    Thanks 

    • Marked as answer by Kpvuppala Thursday, October 26, 2017 4:42 PM
    Thursday, October 26, 2017 4:42 PM

All replies

  • Please check the owner of the DB , Change it to a valid login.
    Sunday, October 15, 2017 9:46 AM
  • Restarting SQL services helped to create new endpoints.

    Thanks 

    • Marked as answer by Kpvuppala Thursday, October 26, 2017 4:42 PM
    Thursday, October 26, 2017 4:42 PM