Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2003
    Posts
    6

    Angry Unanswered: Connection Broken

    Hi,
    Our developer ran a sp in query analyzer (local), and in the middle got this message:
    ==============================================
    [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
    Server: Msg 11, Level 16, State 1, Line 0
    General network error. Check your network documentation.
    ODBC: Msg 0, Level 16, State 1
    Communication link failure

    Connection Broken
    ==============================================
    OS: Win2k Adv Srv
    SQL 2k sp3

    Thanks for your help!

  2. #2
    Join Date
    May 2002
    Posts
    299

    Re: Connection Broken

    Communication Link Failure mostly occurs if the the underlying network
    connection is inconsistent.

    What is the net-lib your app is using to connect to SQL? What is the frequency of these errors? What is your MDAC version?

    I would suggest capturing a network monitor trace to make sure network packets are not dropped. You want to capture the netmon trace at both the client and the server when the problem happens. Go to www.microsoft.com\data and download the latest mdac version. Also, run dbcc checkdb and/or dbcc dbreindex to ensure your data is in good shape.

    If your network is local and persistent I would also check the hardware, network card, hub or cable. Any of these could generate the error.
    --
    -oj
    http://www.rac4sql.net

  3. #3
    Join Date
    Feb 2003
    Posts
    6

    Re: Connection Broken

    Originally posted by oj_n
    Communication Link Failure mostly occurs if the the underlying network
    connection is inconsistent.

    What is the net-lib your app is using to connect to SQL? What is the frequency of these errors? What is your MDAC version?

    I would suggest capturing a network monitor trace to make sure network packets are not dropped. You want to capture the netmon trace at both the client and the server when the problem happens. Go to www.microsoft.com\data and download the latest mdac version. Also, run dbcc checkdb and/or dbcc dbreindex to ensure your data is in good shape.

    If your network is local and persistent I would also check the hardware, network card, hub or cable. Any of these could generate the error.
    Thanks,
    this process was started in Query Analyzer on the local server. There were a couple insert errors before this (foreign key voilation). I'll check the data. Thanks again.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •