Post reply

Communication link failure

  • April 24, 2006 at 6:05 pm

    #111921

    In SQL 2000 ; complex query using linked server fails with

    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).

    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

     

    The query works unless it has has Select * or Select distinct -other simple queries work fine.

    Both servers involved are at current patch level on SQL Server and Windows 2003 Server.

  • April 25, 2006 at 5:50 am

    #633974

    Sometimes when you have 'creative' SQL and you find a 'feature' (ie a bug) that causes the server to AV, this message may pop up. Check the serverlogs for any crashes and/or AV stackdumps. If you find any, then the immediate problem is 'solved' - your query crashes.

    What may cause it, if this is the case, is impossible to speculate about without seeing the actual statement.

    /Kenneth

  • April 26, 2006 at 8:43 am

    #634322

    I've had this problem in the past and at random times in QA and .Net(C#).

    It seems to have been avoided by turning off Named Pipes (by using the Client Network Utility) and using TCP/IP connections instead.

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

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