> ## Content Index
> Fetch the complete content index at: https://blog.tsd.digital/llms.txt
> Use this file to discover other available public pages before exploring further.

# The remote host closed the connection. The error code is 0x80072746
- URL: https://blog.tsd.digital/the-remote-host-closed-the-connection-the-error-code-is-0x80072746/
- Published: 2008-11-05T14:03:40.000Z
- Updated: 2008-11-05T14:03:40.000Z
- Author: Tim Gaunt
- Tags: ASP.Net, C#, Web Development, .Net, #Import 2025-04-01 05:37

We've just moved a couple of our sites onto a new server and have intermittently started to receive the error "The remote host closed the connection. The error code is 0x80072746.", usually around the same time as "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.".

As the infrastructure hadn't changed we were able to rule out network issues, hardware issues (it was an upgrade) and nothing had changed on the code level so we put it down to the new backup routine.

On a little Googling, I found a few sites that were pointing to (among other things) the Request length and Executiuon time which got me thinking, in this particular site there is a lot of data being sent/retrieved and it could be maxing out the request. After a little more digging I found [this article from Microsoft about the httpRuntime Element](http://msdn.microsoft.com/en-us/library/e1f13641%28VS.80%29.aspx?ref=blog.tsd.digital) and I quote

> This time-out applies only if the debug attribute in the compilation element is False. To help to prevent shutting down the application while you are debugging, do not set this time-out to a large value.

Although I didn't recall making any changes to the site, when updating the database configuration settings, I did change the compilation element to false. So far increasing the executionTimeout value appears to have fixed the issue.