Share via

SQL Server Mirroring connection broke

Muhd 0 Reputation points
2024-03-10T11:46:36.5633333+00:00

I has setup a mirroring environment in my 2 Sql Server. For a past few month I just noticed the the mirroring connection got broke. Currently my primary server state (Principal, disconnected) and my DR server state (In recovery).

Based on the log file i see got this message for a few times:
An error occurred in a Service Broker/Database Mirroring transport connection endpoint<c/> Unknown,Error: 8474<c/> State: 11. (Near endpoint role: Target<c/> far endpoint address: '')
Unknown,Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.

So my connection is why DR server state is (In recovery) not (Mirror, Disconnected/In recovery)? And how can I fix my mirroring connection back?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,363 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 107.2K Reputation points
    2024-03-10T12:08:31.65+00:00

    I'm inclined to say that the error message suggest that there was a network problem, so that bytes were lost or distorterd in transport.

    Mirroeing is an old technology, and has been deprecated. What version of SQL Server are you running? What does "SELECT @@version" return?

  2. LiHongMSFT-4306 25,651 Reputation points
    2024-03-11T02:44:58.6433333+00:00

    Hi @Muhd

    Check if this workaround work:

    Perform a nslookup of the CLIENT IP Address that is listed in the error message and find out what computer it is that is connecting.  Then you need to check that machine and determine what specifically is connecting to the SQL Server.  You might get more infromation from doing a SQL Trace for the Errors and Warnings Event Class and have the ClientProcessID column in the trace data. 

    When the error spikes, you might get the PID for the process that is connecting from that 10.26.32.96 machine, and then you can find that process in Task Manager on that machine by adding the PID to the data displayed (View -> Select Columns).

    Error: 17836, Severity: 20, State: 1

    Best regards,

    Cosmog Hong

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments