Mirroring issue

• saidapurs

  Hall of Fame

  Points: 3477

  More actions

  February 9, 2012 at 2:02 am

  #1444930

  Hi Perry,

  I am using different server for all so Port 5022 is using....

  If i use 2 instance in 1 server mean required Port 5022 & 5023...

  Thanks & Regards

  Satish

• saidapurs

  Hall of Fame

  Points: 3477

  More actions

  February 9, 2012 at 10:09 pm

  #1445371

  Hi Perry,

  Today i tried to install service pack 4 but it's giving error, than i checked Witness server is Win 2003 Standard edition with 32bit & another 2 servers are WIN ENT 2003 with 64 bit....

  Is this server issue or else?? please advice me what shall i do...

  Thanks in advance

  Satish

• saidapurs

  Hall of Fame

  Points: 3477

  More actions

  February 21, 2012 at 11:06 pm

  #1450069

  Hi All,

  I got the solution after seeing error log in Witness server.....

  Error :-

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

  Solution :-

  USE master;

  GO

  CREATE LOGIN [NT AUTHORITY\ANONYMOUS LOGON] FROM WINDOWS;

  GO

  GRANT CONNECT on ENDPOINT::hard_endpoint TO [NT AUTHORITY\ANONYMOUS LOGON]

• Perry Whittle

  SSC Guru

  Points: 234013

  More actions

  February 25, 2012 at 9:16 am

  #1451707

  saidapurs (2/21/2012)

  ---

  Hi All,

  I got the solution after seeing error log in Witness server.....

  Error :-

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

  Solution :-

  USE master;

  GO

  CREATE LOGIN [NT AUTHORITY\ANONYMOUS LOGON] FROM WINDOWS;

  GO

  GRANT CONNECT on ENDPOINT::hard_endpoint TO [NT AUTHORITY\ANONYMOUS LOGON]

  This mirrors what we have been telling you, but you shouldnt be allowing anonymous access. The service account the witnes runs under should be granted login to the sql instances and connect to the mirroring endpoint

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

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

• CDeepak

  Valued Member

  Points: 68

  More actions

  March 14, 2012 at 11:34 am

  #1459397

  Hi dear,

  Please check...

  1. what is your service pack of sql server?? if u r using standard edition without without any service pack than u need to enable the trace flag 1400 (;-T1400) u cam add this in startup parameter.

  2.what is your service account of sql server service if it is different from another then grant permission to connect to endpoints. or u can change service account same as other.

  3.Check port no of end point if u use three different server than u should use same port no like 5022 to listen all the server.

• Lynn Pettis

  SSC Guru

  Points: 442467

  More actions

  March 14, 2012 at 11:40 am

  #1459401

  saidapurs (2/8/2012)

  ---

  Hi Perry,

  All are under same domain...

  I tried from 1st it self....

  I logged in in Primary server & logging primary Database than connect Mirror & witness server through Instance name it is connecting fine (Mean not a port issue).

  Then i tried to configure Mirroring with witness server it's giving error as attached in 1st mail but i am able to configure mirroring without witness...

  Please advice me is it server issue or N/W issue or SQL issue??

  Thanks & Regards

  Satish Saidapur

  You successfully configured the witness from the pricipal server? IIRC that is all you have to do.