The underlying connection was closed: The connection was clo

Can you tell us more briefly where you're seeing this.

1).The .NET HTTP implementation tries to keep the connection alive as long as possible in order to avoid the overhead of creating a new connection. If the server decides to close the connection without notifying the client you may see this error. In general, you need to catch these exceptions in your application and create a new connection as necessary. The client proxy code is not really related other than by the fact that it uses the .NET HTTP implementation.

2).There is a server-side connection timeout in ASP.NET that you can configure, and it may be causing this problem.

3) in some cases the sql server may be having the scheduled restart.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

ManiKumar Duppalapudi8y ago
Can you tell us more briefly where you're seeing this.

1).The .NET HTTP implementation tries to keep the connection alive as long as possible in order to avoid the overhead of creating a new connection. If the server decides to close the connection without notifying the client you may see this error. In general, you need to catch these exceptions in your application and create a new connection as necessary. The client proxy code is not really related other than by the fact that it uses the .NET HTTP implementation.

2).There is a server-side connection timeout in ASP.NET that you can configure, and it may be causing this problem.

3) in some cases the sql server may be having the scheduled restart.