Can't profile ASP.NET in IIS 6 when not in IIS 5 isolation
Brian Donahue
Posts: 6,590 Bronze 1
Hello,
Thanks for your post. Yes, the statement is true, but there are some minor glitches. One is that Profiler is still getting the information about which user is running ASP .net from the machine.config file, just like in IIS 5. Since Profiler can only profile one process at a time, web gardens aren't really supported. I think that still works okay, it will just profile only one w3wp.exe.
So if you use a named user in your app pool that the web application is running in (other than the NETWORK Service account), you may have a problem.
What happens, exactly, when you profile your IIS6 application? That may help us pinpoint the problem.
Thanks for your post. Yes, the statement is true, but there are some minor glitches. One is that Profiler is still getting the information about which user is running ASP .net from the machine.config file, just like in IIS 5. Since Profiler can only profile one process at a time, web gardens aren't really supported. I think that still works okay, it will just profile only one w3wp.exe.
So if you use a named user in your app pool that the web application is running in (other than the NETWORK Service account), you may have a problem.
What happens, exactly, when you profile your IIS6 application? That may help us pinpoint the problem.
Comments
The last time that I saw this happening was in Profiler 2.0. There was a rather interesting bug in IIS that caused IE to load http://www.example.com rather than the specified web page. Whatever had caused this to happen has been worked around in version 2.5, so this should not happen any more.
Please update your software if you are experiencing this problem.