ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU or Hang

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU

molotov — Fri, 02 May 2008 21:12:31 GMT

>> The default installation location for the package is C:\Program Files\IIS Resources\DebugDiag <<

In the install I just completed, it was C:\Program Files\DebugDiag\.

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU

Tom — Fri, 02 May 2008 21:24:44 GMT

Molotov,

Very true. IIS Resources was used with DebugDiag 1.0. So what you list is the correct folder for 1.1

Interesting Finds: 2008.05.03

gOODiDEA.NET — Sat, 03 May 2008 08:05:35 GMT

.NET Microformat.net - a .net based flexible Microformat Parser Remote Desktop Client Wrapper For RDP

Interesting Finds: 2008.05.03

gOODiDEA — Sat, 03 May 2008 08:06:22 GMT

.NETMicroformat.net-a.netbasedflexibleMicroformatParserRemoteDesktopClientWrapperFor...

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU

Sean — Mon, 05 May 2008 19:05:02 GMT

I'm installing a new widows XP Pro system and only see the inetinfo and the dllhost processes. What I wamt to see is the aspnet_wp process but don't. What is the circumstances necessary to see that file?

Thanks!

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU

Sean — Mon, 05 May 2008 19:37:09 GMT

The problem was in the machine.config. This post helped me:

So your machine is WINXP sp2 /IIS5.

Currently, I'd suggest you first try changing your ASP.NET's running

process's Account from default machine\aspnet to the LOCALSYSTEM to as to

make sure whether this is a permission problem of the asp.net process

idenitity. To change the process identity, you can follow the below steps:

1. locate the machine.config file under your .NET framework 2.0's intalling

folder like:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG

2. Open the machine.config file and find the <processModel> element, by

default it is configured as:

, we need to change it to below:

so as to let the ASP.NET worker process running under the local system

account(which has the most powerful permission and privileges on local

system...)

3. Restart IIS through "iisreset" command

Then, test your asp.net 2.0 applicaiton again to see whether it can

works......

Also, this is just for testing only, generally we do not recommend asp.net

process running under local system account. Also, the machine.config's

<processModel> element is used for IIS5 isolate model. For IIS6/win2k3

server, it by default use applicaiton pool model which is different from

this.

Anyway, please have a try to see whether it works and feel free to post

here if there're anything unclear...

Thanks,

Steven Cheng

Microsoft Online Support

Weeking recap of ASP.NET Debugging blog

Useful IIS/ASP.NET Information provided by Microsoft Support Teams — Tue, 06 May 2008 17:57:44 GMT

Here are last weeks updates to the ASP.NET Debugging blog: Code Gallery and CodePlex, how are they different

ANSWER: POP QUIZ: Troubleshoot a Hang

ASP.NET Debugging — Thu, 08 May 2008 20:26:47 GMT

We got some really good answers to this quiz.  I am going to give my answer but it isn’t the only

ASP.NET Tips: What to gather to troubleshoot

ASP.NET Debugging — Wed, 21 May 2008 18:39:16 GMT

So now that I am done with all the individual posts, I thought I would wrap them all together. 

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU or Hang

bmassicotte — Sun, 13 Jul 2008 18:21:29 GMT

If your just looking to see what file is executing and what app pool it is under use IISPeek. It will tell you all this is a few seconds. Google it to find it on the net.

Just a thought.. It worked for us.

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU or Hang

Codex73 — Wed, 30 Jul 2008 19:15:58 GMT

IISPeek will only work on Windows 2003 or Windows 2008 Servers.

re: ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU or Hang

bmassicotte — Tue, 05 Aug 2008 04:20:45 GMT

Yes, it only works with those and Vista. (but who is using Vista for a web server...) Sorry for not clarifying earlier. If you are using one of the supported platforms, IISPeek will do all the manual gathering for you. If not, it can't help.

Best of luck!