locked
An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') RRS feed

  • Question

  • Hi all,
    we are getting the below error where mirroring is configured in both the nodes in same time fraction of seconds difference.

    Every 12 hours we are getting this error mirroring configured servers.
    please help me to fix this issue.
    Application error-log:
    An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')
    sql error log:
    2015-05-04 18:32:43.06 spid40s Error: 9642, Severity: 16, State: 3.
    2015-05-04 18:32:43.06 spid40s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')
    2015-05-04 18:32:43.37 spid40s Error: 9642, Severity: 16, State: 3.
    2015-05-04 18:32:43.37 spid40s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')

    below error raised in application error log and sql error log along with the above error.

    Error: 17828, Severity: 20, State: 4.
    The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library. [CLIENT: <IP Address>]

    Monday, May 11, 2015 5:49 PM

Answers

  • Error 8474 state:11 is fired by Broker/Mirroring transport when it detects corrupt message preamble (first 16 bytes of every message received from the network). The far-endpoint address gets set only when the connection is in online state (authenticated and validated). Since the far endpoint address is NULL, it means that its happening during the connection handshake phase. This could happen if some other application is trying to use the same endpoint port which we are using for mirroring.
    Then it will be resetting the endpoints. If the endpoint is left off on the principal, then the server will failover.

    The case is similar to you, please refer to: http://social.msdn.microsoft.com/forums/en-US/sqlservicebroker/thread/30859690-6043-40e8-8390-449d73d5be7d/

    Please try to check your endpoint refer to the following article:
    Troubleshoot Database Mirroring: http://technet.microsoft.com/en-us/library/ms189127.aspx .

    • Marked as answer by chinna14 Monday, May 11, 2015 6:19 PM
    Monday, May 11, 2015 6:11 PM

All replies

  • Error 8474 state:11 is fired by Broker/Mirroring transport when it detects corrupt message preamble (first 16 bytes of every message received from the network). The far-endpoint address gets set only when the connection is in online state (authenticated and validated). Since the far endpoint address is NULL, it means that its happening during the connection handshake phase. This could happen if some other application is trying to use the same endpoint port which we are using for mirroring.
    Then it will be resetting the endpoints. If the endpoint is left off on the principal, then the server will failover.

    The case is similar to you, please refer to: http://social.msdn.microsoft.com/forums/en-US/sqlservicebroker/thread/30859690-6043-40e8-8390-449d73d5be7d/

    Please try to check your endpoint refer to the following article:
    Troubleshoot Database Mirroring: http://technet.microsoft.com/en-us/library/ms189127.aspx .

    • Marked as answer by chinna14 Monday, May 11, 2015 6:19 PM
    Monday, May 11, 2015 6:11 PM
  • hi

    nodes also connecting fine and end-points also online state.

    but why we are getting this error every 12 hours where mirroring or always configured server.

    we are using 5022 port no in all the server.

    Monday, May 11, 2015 6:23 PM
  • https://blog.sqlauthority.com/2019/05/04/sql-server-error-9642-an-error-occurred-in-a-service-broker-database-mirroring-transport-connection-endpoint/
    Wednesday, March 18, 2020 9:14 PM
  • When the issue is reoccuring every 12 hours I would take a look at the monitoring tools. There might be a scan on the network on this port. Mayby take a talk with the network admins to find out if they are scanning on this port.

    Niels Grove-Rasmussen (http://sqladm.blogspot.com/)

    Monday, May 25, 2020 6:54 AM