none
Error 0xe8 (232). Pipe is being closed

    Question

  • Recently, we have had an error we couldn't find out what was it related to. The error had happened twice until now. The fact is that suddenly the sever rejects all the connections, and looking that the default trace we find the next error:

    Network error code 0xe8 occurred

    while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 19581 ms, enqueued 0 ms, network writes 1 ms, network reads 1 ms, establishing SSL 1 ms, negotiating SSPI 0 ms, validating login 19577 ms. [CLIENT: <local machine>]

    We cound't find anything else in the windows logs or the sql server logs.

    Tuesday, July 13, 2010 11:11 PM

Answers

  • http://www.pc-library.com/errors/error-code/232-0xE8/  makes this comment: " Most of the causes are related to connection loss, lack of available memory, or problems with the hardware or software in the network connection."

    This may require your network folks to examine the network infrastructure.  Since it is timing based, the problem will be sporadic.  Also check your network and SQL Server for other errors in that time period. 

    You mentioned that the server rejects all connections, which suggests that the server logs should have a hint somewhere.

    FWIW,
    RLF

     

    Wednesday, July 14, 2010 6:16 PM