locked
Issues with Application and SQL server RRS feed

  • General discussion

  • Hi,

    From last couple of weeks, we are receiving the following errors on our applications hosted on IIS. 

    [Win32Exception: The specified network name is no longer available] [SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)] at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

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

    [Win32Exception: The semaphore timeout period has expired] [SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)] at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

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

    SQL becomes unresponsive (not able to open Management studio or open with DAC account), and this results in application hang. Only thing we can do at that time is to reset SQL server and everything is normal again.

    I have been checking with network providers to see if this can be related to network issues, but they are saying this is a memory pressure on SQL server.

    Could you please shed some light on this and provide some information on the causes of the issue so that we can investigate further?

    Regards,

    Saikrishna


    • Edited by Saikrishna Desaraju Thursday, October 13, 2016 8:09 AM
    • Moved by Bob Beauchemin Thursday, October 13, 2016 4:40 PM Moved to forum for client-side SqlClient for best results
    Thursday, October 13, 2016 8:07 AM