Ask a questionAsk a question
 

Proposed AnswerGeneral network error

  • Wednesday, November 04, 2009 7:59 PMabhinavd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    We are getting the following error while we access SQL SERVER 2005 database.

    Error : Setting of text failed : E_FAIL

    HRESULT: 0X80004005

    SQLSTATE: 08S01

    Native Error: 11

    Error state: 1

    Severity: 16

    Source:  Microsoft OLE DB Provider for SQL Server

    Error message: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

    For some time the SQL SERVER is not accessible(for few seconds) from client location during this period when the error occurs.


    Please someone help me out on this issue.

All Replies

  • Wednesday, November 04, 2009 8:04 PMPhil BrammerMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    I would have the network staff at the client location investigate their network and its settings.  It sounds like there may be a connectivity issue, caused by any number of issues.
    Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer
    • Proposed As Answer bySQLUSA Saturday, November 14, 2009 6:46 PM
    •  
  • Wednesday, November 04, 2009 8:16 PMSuhas V Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Abhinav 

    Can you please refer below article,

    http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx

    -------------------------------------------------------------------------------------
    Thanks, Suhas V
  • Wednesday, November 04, 2009 8:16 PMChirag_Shah Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    This is a generic error saying your client has trouble connecting your server.

     

    This error can be cause of myriad of reasons it could be your NIC card Or your anti virus software or sometime Active Directory stuff.

     

    Are you using Windows Authentication or SQL authentication?  If you are using Windows authentication then try using SQL authentication and see it works (at least it will eliminate active directory stuff)