Database mirroring error

  • Hi,

    I'm receiving the following error when trying to set up mirroring on a database.

    Database Mirroring login attempt by user 'domain\user.' failed with error: 'Connection handshake failed. The login 'domain\user' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: nn.nn.nn.nn]

    The account domain\user was accidentally deleted in AD and recreated. It runs the sql service. We have tried creating new end points, granting connect permissions for the domain\user account. We can see the boxes talking to each other but the mirroring still fails. Any suggestions would be appreciated.

  • philip.nash (10/21/2011)


    Hi,

    I'm receiving the following error when trying to set up mirroring on a database.

    Database Mirroring login attempt by user 'domain\user.' failed with error: 'Connection handshake failed. The login 'domain\user' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: nn.nn.nn.nn]

    The account domain\user was accidentally deleted in AD and recreated. It runs the sql service. We have tried creating new end points, granting connect permissions for the domain\user account. We can see the boxes talking to each other but the mirroring still fails. Any suggestions would be appreciated.

    go into sql server config manager and re enter the acccount details for the sql server services. The fact the account was deleted and re created doesnt mean it has the same SID.

    Once the account details have been re entered for the service, create the logins and endpoints in sql server and then grant connect to the endpoint

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Hi Perry,

    Thanks, for the information. I deleted and then recreated end points, login etc used the new login and associated it with new endpoints and it all worked successfully.

    Once again many thanks,

    Phil

  • philip.nash (11/8/2011)


    Hi Perry,

    Thanks, for the information. I deleted and then recreated end points, login etc used the new login and associated it with new endpoints and it all worked successfully.

    Once again many thanks,

    Phil

    😉

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • The database mirroring already setup and was running fine earlier.

    Now suddenly the database status showing as principal server (Principal, Disconnected) and Mirror server (Mirror, Disconnected, In recovery).

    I know that Service accounts(SQL and agent) need to be the same on both boxes.

    observed on Principal server sql server services running on NT service\MSSQLSERVER account and Mirror server sql server services running on Domain account).

    but here they configured as one domain account(i.e,its not related to service accounts)

    i have started and stop the endpoint it didn't help for me and then i have Deleted and re-create the database mirroring endpoints on both servers.

    Now im getting the below error message.:

    Message

    Database Mirroring login attempt by user '.' failed with error: 'Connection handshake failed. The login does not have CONNECT permission on the endpoint. State 84.'.

    Same error on principal and mirror but accounts are different.

    I need to do reconfigure the mirroring (it wil work) or becase all the partners should run under the same domain accounts(i need to chane the accounts on Both prinicpal and mirror server)

    Please let us know your suggestions on this.

    Thanks in advance!!

    Thanks & Regards,

    DBA

    SQL server DBA

  • see your question here

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 6 posts - 1 through 5 (of 5 total)

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