locked
Mirroring Problem using Certificates ( between LAN and DMZ ) RRS feed

  • Question

  • Hello Guys,

    Here it is my scenario;

    My principal server in LAN and my mirror server in DMZ and Iam using certificates both partners (I dont use witness server).

    I did not use wizard.I have just Setting Up Database Mirroring Using Certificates (Transact-SQL)

    (http://msdn2.microsoft.com/en-us/library/ms191140.aspx)

    Iam sure all steps are ok!(I mean ports,certificates,users,logins,endpoints,GRANT CONNECT ON ENDPOINT,SP1....)

    But I am still getting error  Principal Server;

    Database mirroring connection error 4 'An error occurred while receiving data: '64(error not found)'.' for 'TCP://195.xx.yy.zz:5022'.

    Also,Mirror Database status  changed (Restoring---->In Recovery)

    I tried many tests but I did not succeed.Do you have any ideas in this case or any experince in database mirroring using certificates.

    Many thanks for your reply...

    Regards..

    Tarkan G.

     

    Monday, November 20, 2006 4:12 PM

All replies

  • Can you monitor the mirror server for the Profiler events 'Security Audit/Audit: Broker Login' and 'Broker/Broker: Connection'? They should tell you why the mirror is closing the connection (which is why you're seeing the error 64 on the principal).

    HTH,
    ~ Remus

    Tuesday, November 21, 2006 12:45 AM
  • Hello,

    When I monitor the mirror server profiler,I found just  user error message;

    "The update job for the database mirroring monitor already exists.  To change the update period, use sys.sp_dbmmonitorchangemonitoring"

    no more error...

    Regards..

    Tarkan G.

    GTA

     

     

    Tuesday, November 21, 2006 9:27 AM
  • I get the same error.
    Tuesday, November 21, 2006 2:28 PM
  • Dear  SQL SERVER 2005 Gurus,

    I need your help in this case.I am waiting your valuable reply.

    Regards..

    Tarkan G.

    GTA

    Thursday, November 23, 2006 7:57 AM
  • Well, I'm still waiting the reply to my question. If you set up the partner name correctly, then you must see the events I requested. If you don't see them, then you probably did not correctly set up the profiler trace or you're not even attampting to establish a connection.

    HTH,
    ~ Remus

    Monday, November 27, 2006 8:17 PM
  • Hello Remus,

    Iam sorry my late answer.Here it is trace results;

    Principal Server Side:

    Audit Login:--- network protocol:LPC set quoted_identifier on set arithabort off set numeric_roundabort off set ansi_warnings on set a

     

    Mirror Server Side:

    Broker Connection :An error occurred while receiving data: '64(error not found)'.

     

     

    Regards..

    Tarkan G.

    GTA

    Thursday, November 30, 2006 2:24 PM
  • According to this log, the Principal never establishes nor accepts a connection with the mirror, since it never traces an event. Considering that the connections is always initiated by the principal (when running ALTER DATABASE ... SET PARTNER = '...') and the mirror accepts this connection, yet the mirror does close a connection, I must conclude that you did not set up the profiler correctly on the principal side.

    HTH,
    ~ Remus

    Friday, December 1, 2006 1:56 AM