How to Fix Browser Hang caused by IIS Request Aborted Error

Learn how to troubleshoot and resolve the IIS request aborted error that causes the browser to hang when accessing a website hosted on IIS 10.

If you are hosting a website on IIS 10, you may encounter the IIS request aborted error that prevents the website from loading properly. This error occurs when the server cancels the request before it is completed, usually due to a timeout or a configuration issue.

In this article, we will explain what causes this error, how to diagnose it, and how to fix it.

Causes of IIS Request Aborted Error

There are several possible causes of the IIS request aborted error, such as:

• The request takes too long to process and exceeds the default timeout limit of 110 seconds.
• The web.config file is corrupted, missing, or contains invalid settings that prevent the website from starting or running correctly.
• The application pool that hosts the website is stopped, recycled, or has reached its maximum number of concurrent requests.
• The network connection between the client and the server is interrupted or unstable.

How to Diagnose IIS Request Aborted Error

To diagnose the IIS request aborted error, you can use the following steps:

• Check the IIS logs for any errors or warnings related to the request. You can find the IIS logs in the %SystemDrive%\inetpub\logs\LogFiles folder by default.
• Enable Failed Request Tracing to capture detailed information about the request and the error. You can enable this feature in the IIS Manager under the website’s configuration.
• Use a network monitoring tool such as Fiddler or Wireshark to inspect the HTTP traffic between the client and the server. You can see the status code, headers, and body of the request and the response.

How to Fix IIS Request Aborted Error

Depending on the cause of the error, you can try the following solutions:

Solution 1: Increase the timeout limit for the request

You can do this by modifying the executionTimeout attribute of the httpRuntime element in the web.config file. For example, to set the timeout to 300 seconds, you can use the following code:

<system.web>
  <httpRuntime executionTimeout="300" />
</system.web>

Solution 2: Repair or replace the web.config file

You can use the IIS Manager to export and import the web.config file from another working website, or use a backup copy of the web.config file. You can also use the Configuration Editor in the IIS Manager to edit the web.config file and fix any errors or invalid settings.

Solution 3: Restart or recycle the application pool

You can do this by using the IIS Manager under the Application Pools node. Right-click on the application pool that hosts the website and select Recycle or Stop and Start.

Solution 4: Check and improve the network connection

You can use the ping and tracert commands to test the connectivity and latency between the client and the server. You can also check the firewall and proxy settings to ensure that they are not blocking or interfering with the request.

Frequently Asked Questions (FAQs)

Quesion: What is IIS?

Answer; IIS stands for Internet Information Services, which is a web server software that runs on Windows servers. IIS can host websites, web applications, web services, and other web-related components.

Question: What is the ASP.NET Core Module?

Answer: The ASP.NET Core Module is a native IIS module that enables IIS to host ASP.NET Core applications. The ASP.NET Core Module handles the communication between IIS and the ASP.NET Core app, and provides configuration settings for the app in the web.config file.

Question: How can I access the IIS Manager?

Answer: You can access the IIS Manager by using the following steps:

1. On the Windows server, open the Start menu and type IIS.
2. Select Internet Information Services (IIS) Manager from the search results.
3. Alternatively, you can open the Run dialog box by pressing Windows + R keys, and type inetmgr and press Enter.

Summary

In this article, we have learned how to fix the IIS request aborted error that causes the browser to hang when accessing a website hosted on IIS 10. We have explained the possible causes, diagnosis, and solutions for this error. We hope this article has helped you resolve the issue and improve your website performance.

Disclaimer: This article is for informational purposes only and does not constitute professional advice. The author and the publisher are not liable for any damages or losses that may result from the use of the information or solutions provided in this article. Always consult a qualified IT professional before making any changes to your IIS configuration or web.config file.