Post reply

A fatal error occurred while reading the input stream from the network

  • July 24, 2011 at 8:39 pm

    #244795

    Hi,

    We SQL Server 2005 x64 with SP3. We have 2 GB RAM and it's development server.

    We are moving 100 GB data from one database to other database on the same instance.

    The process terminated and noticed the below error in the error log at the time the process got terminated

    Error: 4014, Severity: 20, State: 2.

    A fatal error occurred while reading the input stream from the network. The session will be terminated.

    I went through the below links :

    http://support.microsoft.com/kb/942861

    http://www.sql-server-performance.com/forum/threads/fatal-error.1420/

    Link one says, tcp chimney should be disabled. In our environment, on SQL Servers, tcp chimney is disabled already ---ruled out

    Link two says, memory is getting paged out. But I did not see any memory errors or memory dumps in error log. How to make sure that the process was terminated because of memory paging?

    And the error says that the Session will be terminated. How to find out which session got terminated?

    Please advice

    Thanks

  • July 25, 2011 at 6:25 pm

    #1358206

    Could you please shed some light on this?

    Thanks

  • July 27, 2011 at 3:11 pm

    #1359702

    gmamata7 (7/24/2011)

    Link two says, memory is getting paged out. But I did not see any memory errors or memory dumps in error log. How to make sure that the process was terminated because of memory paging?

    Try to use perfmon to figure out if you are having memory problems when copying the data. I think that you have indeed memory problems 2GB is not that much. Just to be sure run perfmon.



    My blog

  • July 27, 2011 at 3:32 pm

    #1359715

    if you are running this process from a remote machine using SSIS TCP chimney needs to be disabled on that machine as well.

    ---------------------------------------------------------------------

  • November 5, 2014 at 2:31 am

    #1756681

    we have experienced this error a week ago. our network team, security team and database team search every thing. At the end of the researching we have detected the error resource.

    It is the IPS device. Ask your security team is there any signature on IPS device.

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

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