Post reply

ConnectionCheckForData Error

  • April 26, 2004 at 3:26 pm

    #84179

    When running a job under SQLAgent we have intermittently received the following message:

    ConnectionCheckForData (CheckforData()). [SQLSTATE 01000] (Message 10054)  General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11).  The step failed.

    The job had been running for two years successfully and has recently (over the last two weeks) begun failing intermittently.  The job is run from the local SQL server.  The step runs a stored procedure and fails after about an hour and a half of running. 

    Our environment is Windows 2000 SP1, SQL server 7.0 Sp3.

  • April 28, 2004 at 12:58 am

    #504441

    I am also having this problem on our new SQL box that is connected to a SAN.  Our CPU hits 100%, the system freezes, then we get the ConnectionCheckForData error.

    I am still experimenting with different settings since this has only just happened, but I see some improvement when I uncheck "Boost SQL Server Priority on Windows" on the Server Properties. 

    I will post back when I find out more.  BTW, I am running Windows 2000 SP4, SQL Server 2000 SP3 and I am running the stored procedure as 'sa' in Query Analyser.

    Regards,

    Angela  

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

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