Communication Link failure

  • scorpianprince

    SSC Eights!

    Points: 908

    Hi all,

    can anyone tell me about the error that i am getting in the error log and what can be the cause of this error and what can be done to resolve this error :-

    Date 1/18/2011 2:14:32 PM

    Log SQL Agent (Current - 1/18/2011 2:14:00 PM)

    Message

    [298] SQLServer Error: 16389, Communication link failure [SQLSTATE 08S01]

    NEVER NEVER EVER GIVE UP;-)

  • Adiga

    One Orange Chip

    Points: 27224

    These errors are usually logged in the Agent Log or by the application when the SQL Server instance low on memory or the underlying storage is having some issues. You may find the below links useful.

    http://sqlblog.com/blogs/merrill_aldrich/archive/2010/06/22/long-i-os-and-tcp-timeouts-are-not-a-sql-server-problem-except-when-they-are.aspx

    http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/1536b610-e548-40c1-b9d0-1be3ad19a823

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • scorpianprince

    SSC Eights!

    Points: 908

    Thanks for the Reply. The Links are really helpful

    About my findings:-

    The main reason after our analysis is coming out to be the I/O latch and the avg cpu utilisation of the server is 40% and most of the time the SQL server is waiting to read from the disk drive.

    Also the Db files are actively/continuously scanned by the Antivirus

    So can you suggest what can be done

    Also today i have the following error can you help me why this came

    Date 1/19/2011 12:37:15 PM

    Log SQL Agent (Current - 1/19/2011 12:40:00 PM)

    Message

    [298] SQLServer Error: 121, TCP Provider: The semaphore timeout period has expired. [SQLSTATE 08S01]

    Should i go to the network team for the connectivity issue or the storage team to check the storage as it is taking time to read from the SAN Drives.

    NEVER NEVER EVER GIVE UP;-)

  • Adiga

    One Orange Chip

    Points: 27224

    Please involve the storage team to check for any issues with the storage or if any of the drivers need to be updated.

    Also inform the Windows Administrators to configure the Antivirus software to exclude the database files.

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • Supriya Garde

    Grasshopper

    Points: 17

    Hi Pradeep,

    I'm facing with similar issue, in Agent server getting "Communication Link Failure" error in Event viewer.

    Per your recommendation, I checked and SQL Server Instance is not low on space.

    Second thing you said to check if underlying storage has any issue. What exactly I Can tell my storage team to check.

     

    • This reply was modified 2 months, 1 week ago by  Supriya Garde.

Viewing 5 posts - 1 through 5 (of 5 total)

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