CLR Profiler v2 & ASP.NET: doesn't work

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Russ Bishop - 15 Nov 2003 19:21 GMT

The profiler just sits forever at "Waiting for ASP.NET worker process to
start".

I have verified it places the environment registry vars in their correct
place. However when I navigate to my ASP.NET app and aspnet_wp.exe starts up
the profiler doesn't seem to recognize that or connect with it.

IISAdmin & W3svc are running as local system.

Anything else to check?

-- russ

Reply to this Message

xxrj43 - 17 Nov 2003 10:46 GMT

I have it working fine for me.

Except that when trying to profile a swedish publishing module (EPI-Server),
it starts as normal (i.e. the "Waiting for asp.net to start" disappears),
but the site doesn't come up - and I have changed the timeouts so it would
keep going for 45 minutes before I get Application Unavailable - but I still
get Application Unavailable...

Perhaps I need to give it several more hours to launch the application in
question :> - although I did turn off the profiling during the attempted
startup..

My other gripe is that the Histogram by Age throws a FormatException. anyone
else got that working? If you do, what FW are you running it on?

Cheers.

> The profiler just sits forever at "Waiting for ASP.NET worker process to
> start".
[quoted text clipped - 8 lines]
>
> -- russ

Reply to this Message

Jerry Negrelli - 17 Nov 2003 20:33 GMT

Have you tried modifying your master machine.config file
to include <processModel ... userName="SYSTEM"> instead
of <processModel ... userName="machine"> ?

JER

>-----Original Message-----
>I have it working fine for me.
[quoted text clipped - 29 lines]
>
>.

Reply to this Message

Russ Bishop - 18 Nov 2003 01:58 GMT

Yes I tried that and it did not help.

-- russ

> Have you tried modifying your master machine.config file
> to include <processModel ... userName="SYSTEM"> instead
[quoted text clipped - 47 lines]
> >
> >.

Reply to this Message

Peter Sollich [MSFT] - 21 Nov 2003 17:58 GMT

Russ,

are you using the latest version we made available?
There's a link to it on
http://gotdotnet.com/team/clr/about_clr_performance.aspx.

The reason I'm asking is that we fixed a hang bug in this
version, and it might just be your problem as well.

If that doesn't help, I can only suggest attaching a
debugger and trying to find out where it hangs.

This posting is provided "AS IS" with no warranties, and
confers no rights.

Please do not send e-mail directly to this alias. This
alias is for newsgroup purposes only.

Thanks
Peter

>-----Original Message-----
>Yes I tried that and it did not help.
[quoted text clipped - 54 lines]
>
>.

Reply to this Message

Peter Sollich [MSFT] - 19 Nov 2003 13:39 GMT

Weird - I wouldn't know what causes your site to hang.
Have you tried to attach a debugger to the ASP.NET worker
process to see where it's hanging? There is one hang bug
we fixed recently, so it might be worthwhile to try the
new version of CLRProfiler (there's a link to the
download at
http://gotdotnet.com/team/clr/about_clr_performance.aspx).

About the format exception in AgeHistogram.cs - we just
noticed this. Only seems to happen on non-US versions of
the CLR. You should be able to fix this in the source
code by replacing the call to Double.Parse(rb.Text) in
AgeHistogram.cs by Convert.ToDouble(rb.Text,
CultureInfo.InvariantCulture).

This posting is provided "AS IS" with no warranties, and
confers no rights.

Please do not send e-mail directly to this alias. This
alias is for newsgroup purposes only.

Thanks
Peter

>-----Original Message-----
>I have it working fine for me.
[quoted text clipped - 29 lines]
>
>.

Reply to this Message

CLR Profiler v2 & ASP.NET: doesn't work

Free Magazines