none
SQL error logged in Windows event log: Error 4014, Severity, 20, State, 13. MSG: A fatal error occurred...

    Question

  • SQL error logged in Windows event log: Error 4014, Severity, 20, State, 13. MSG: A fatal error occurred while reading the input streamfrom the network. The session will be terminated, Input error 121, Output error 0. This error causes approx 10-15 users problems - When error occurs users are not able to access Citrix Desktop Published Apps until their Citrix session is reset...

    I will also check to see if a dump file was generated...

    Microsoft SQL Server 2008 Standard
    Microsoft Windows Server 2008 Standard

    Regards,
    Derek.

     

    Friday, May 13, 2011 4:16 PM

Answers

  • Hi Derek,

    It looks like a network error. The error indicates that SQL has started reading a message from client which potentially spans multiple TDS packets. And the error is as expected - state 13 means exactly that a read failed after we attempted to read the remainder of a partially read packet .You could use the connectivity ring buffer to find out which client triggered the 4014 error:
    SELECT * FROM sys.dm_os_ring_buffers where ring_buffer_type='RING_BUFFER_CONNECTIVITY'
    What you can also do though is to enable trace flag 7827 (DBCC TRACEON(7827, -1)) and all connection closures will be recorded into the ring buffer. As soon as you experience the 4014, query the ring buffer again and seek for a nearby record of the connection closure which shows the error 64 in the input and is indicated as killed or other abnormal flag in the TdsDisconnectFlags.
    Here is a similar connection posted.

     


    Best Regards,
    Peja

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Peja Tao Wednesday, May 18, 2011 9:16 AM
    • Marked as answer by Peja Tao Monday, May 23, 2011 3:35 PM
    Tuesday, May 17, 2011 2:12 AM
    • Proposed as answer by Peja Tao Wednesday, May 18, 2011 9:17 AM
    • Marked as answer by Peja Tao Monday, May 23, 2011 3:35 PM
    Friday, May 13, 2011 5:48 PM

All replies

    • Proposed as answer by Peja Tao Wednesday, May 18, 2011 9:17 AM
    • Marked as answer by Peja Tao Monday, May 23, 2011 3:35 PM
    Friday, May 13, 2011 5:48 PM
  • SQL error logged in Windows event log: Error 4014, Severity, 20, State, 13. MSG: A fatal error occurred while reading the input streamfrom the network. The session will be terminated, Input error 121, Output error 0. This error causes approx 10-15 users problems - When error occurs users are not able to access Citrix Desktop Published Apps until their Citrix session is reset...

    I will also check to see if a dump file was generated...

    Microsoft SQL Server 2008 Standard
    Microsoft Windows Server 2008 Standard

    Regards,
    Derek.

     


    Do you also see some other errors like IO requests pending for more then 15 secs or Latch timeouts etc....there is a KB article for this error as well .
    Abhay Chaudhary OCP 9i, MCTS/MCITP (SQL Server 2005, 2008, 2005 BI) ms-abhay.blogspot.com/
    Saturday, May 14, 2011 4:04 PM
  • Hi Derek,

    It looks like a network error. The error indicates that SQL has started reading a message from client which potentially spans multiple TDS packets. And the error is as expected - state 13 means exactly that a read failed after we attempted to read the remainder of a partially read packet .You could use the connectivity ring buffer to find out which client triggered the 4014 error:
    SELECT * FROM sys.dm_os_ring_buffers where ring_buffer_type='RING_BUFFER_CONNECTIVITY'
    What you can also do though is to enable trace flag 7827 (DBCC TRACEON(7827, -1)) and all connection closures will be recorded into the ring buffer. As soon as you experience the 4014, query the ring buffer again and seek for a nearby record of the connection closure which shows the error 64 in the input and is indicated as killed or other abnormal flag in the TdsDisconnectFlags.
    Here is a similar connection posted.

     


    Best Regards,
    Peja

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Peja Tao Wednesday, May 18, 2011 9:16 AM
    • Marked as answer by Peja Tao Monday, May 23, 2011 3:35 PM
    Tuesday, May 17, 2011 2:12 AM
  • Thank you folks for your time and in-put on this.

    Regards,

    Derek.

     

    Wednesday, May 18, 2011 9:12 AM