An SNI call failed ... RRS feed

  • Question

  • We have an application that use SQL server 2005 . The databses on the server are mirrored. Also we have witness. During a test we failovered from principal to mirrored server. Our application gets error message during 5 minutes. The errors were that sql connection has timeout.
    Also on mirrored server in event viewer I found next errors:
    • An SNI call failed during a Service Broker/Database Mirroring transport operation. SNI error '10065(error not found)'.
      You can find this error in sys.message, where message_id=8471
    • An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8471, State: 2. (Near endpoint role: Initiator, far endpoint address: '')
    • The mirroring connection to "TCP://primary_srv:5022" has timed out for database "Application_database" after 10 seconds without a response. Check the service and network connections.
    • Database mirroring connection error 2 'Connection attempt failed with error: '10060(error not found)'.' for 'TCP://primary_srv:5022'.
    • Database mirroring connection error 4 '64(error not found)' for 'TCP://primary_srv.posprod.supersol.co.il:5022'.
      last 2 errors can be found in sys.message, where message_id=1474
    Our computers is windows 2003, SQL2005 sp2 with fotfix of audust. Also few ours before this test .Net3 was installed on those computers.

    Any advises? Some help & ideas. What does this errors means?

    Thursday, October 18, 2007 2:12 PM

All replies


    Did the failover work? Could you fail back?
    Thursday, October 18, 2007 3:41 PM
  • Yes, we can failover back. All 3 servers are in a same domain. And they use windows authentication for conversation between themselfs .
    Saturday, October 20, 2007 2:52 PM