IIS Troubleshooting
26 views | +0 today
Follow
IIS Troubleshooting
IIS Troubleshooting
Curated by iistutorial
Your new post is loading...
Your new post is loading...
Scooped by iistutorial
Scoop.it!

ASP.net Hang in IIS 7.0 - WebTopics - Site Home - MSDN Blogs

ASP.net Hang in IIS 7.0 - WebTopics - Site Home - MSDN Blogs | IIS Troubleshooting | Scoop.it

The behaviour occurs because beginning in IIS7, when an ASP.net application runs in Integrated mode there is a restriction on the number of concurrently executing requests per CPU.  By default, the limit to the number of concurrently executing ASP.net requests is 12.  You can modify this limit by setting the MaxConcurrentRequestsPerCPU registry key atHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727 to a value higher than 12.  NOTE: By default, this registry key does not exist.  You will need to create it manually as a DWORD and give it a value.  The value you should give it depends on your application load and how many concurrent requests are expected. 


For a more detailed explanation of how ASP.net threading works in IIS6 and IIS7, please see:

 

ASP.NET Thread Usage on IIS 7.0 and 6.0

http://blogs.msdn.com/tmarq/archive/2007/07/21/asp-net-thread-usage-on-iis-7-0-and-6-0.aspx

 

AND

 

Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications

http://support.microsoft.com/kb/821268


more...
No comment yet.
Scooped by iistutorial
Scoop.it!

In-Proc Session State Management - WebTopics - Site Home - MSDN Blogs

In-Proc Session State Management - WebTopics - Site Home - MSDN Blogs | IIS Troubleshooting | Scoop.it

A session is defined as the period of time a unique user interacts with a particular web application.

HTTP is a stateless protocol, in the sense that a Web server is concerned only with the current HTTP request for any given Web page. The server retains no knowledge of previous requests.

The stateless nature of HTTP requests presents unique challenges when writing Web applications.

ASP and ASP.NET applications maintain a user’s session using a feature called session state.

In this series we are going to talk in detail about how to troubleshoot ASP.NET session state related issues.

more...
No comment yet.
Scooped by iistutorial
Scoop.it!

Troubleshooting Anonymous authentication failures in IIS - Care, Share and Grow! - Site Home - MSDN Blogs

Troubleshooting Anonymous authentication failures in IIS - Care, Share and Grow! - Site Home - MSDN Blogs | IIS Troubleshooting | Scoop.it
Description around issues related to IIS, ASP.Net and SSL.
more...
No comment yet.
Scooped by iistutorial
Scoop.it!

Caution while xcopying IIS 7.0 config files - WebTopics - Site Home - MSDN Blogs

Caution while xcopying IIS 7.0 config files - WebTopics - Site Home - MSDN Blogs | IIS Troubleshooting | Scoop.it
more...
No comment yet.
Scooped by iistutorial
Scoop.it!

How To View what ASP.NET Requests are doing at runtime on IIS 6.0 - WebTopics - Site Home - MSDN Blogs

How To View what ASP.NET Requests are doing at runtime on IIS 6.0 - WebTopics - Site Home - MSDN Blogs | IIS Troubleshooting | Scoop.it

This is just a quick blog to mention a forgotten tool.   The managed stack explorer can be run on an IIS 6.0 Server running ASP.NET 2.0 to investigate the managed call stacks.  Looking at the call stacks when an ASP.NET application is not responding may help identify what the requests are doing.

Setting up the tool

Download the Managed Stack Explorer from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=80cf81f7-d710-47e3-8b95-5a6555a230c2&displaylang=en

Run the MSI and install to a directory of your choice.  The default location is C:\Program Files\Power Toys for Visual Studio\Managed Stack Explorer

more...
No comment yet.