Post reply

Communication link failure but only once per week

  • February 11, 2022 at 9:12 pm

    #3982583

    Hello experts,

    I'm helping to troubleshoot an issue where the following error happens on an AOAG cluster, which disconnects applications from the database:

    SQL State: [08S01]
    SQL Error: [[Microsoft][ODBC Driver 13 for SQL Server]Communication link failure]

    I have seen various posts while Googling this error. The thing is, as far as the customer can tell us, this error happens once per week around the same time (roughly around 1 am).

    I see a reindexing job that *might* be the culprit for the disconnections but am not sure. Also, discussions including TCP Chimney and driver issues don't seem to apply because I figure those issues would cause issues constantly, not just during one timespan.

    Does anyone have advice on how I can troubleshoot further?

    Aside from the reindexing job, I don't see any AG failovers during the times in question, so I don't think that's it.

    And the System event log does not show any correlated server restarts.

    Another idea is to use Wireshark to somehow gather more info. Is that recommended? If so, does anyone have suggestions on how to set up the relevant Wireshark trace to find a possible cause of these disconnects?

    Many thanks for any help.

    -- webrunner

    -------------------
    A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
    Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

  • February 12, 2022 at 10:10 pm

    #3982882

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • February 14, 2022 at 6:51 am

    This was removed by the editor as SPAM

  • February 14, 2022 at 8:18 pm

    #3983556

    Which edition of SQL Server are you using and what are the parameters you're using for the "reindexing job"?

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply