How do I use CLR Profiler to debug an ASP.Net app running on IIS 7.5?

5.1k views Asked by At

I am having memory leak issues with my ASP.Net application. I've tried WinDbg, which IMO displays mostly useless information, and I'm currently trying to get the CLR profiler to work.

My problem is everytime I try to "Profile ASP.NET" It just flashes two consoles up so fast I can't read them, then the title bar of the CLR Profiler says "Starting IIS. Error 2 occurred."

  • IIS 7.5
  • Windows Server 2008 R2 Enterprise

Other things to know:

I did try running the CLR Profiler as administrator.

I really need to identify the source of my memory leak, any help would be appreciated.

EDIT:

I've already seen this: http://msdn.microsoft.com/en-us/library/ff650691.aspx

3

There are 3 answers

0
Caffreys On

Same issue here, the above post helped - I resolved it by running CLRProfiler as 'Administrator'

0
nairdo On

I've had this problem when using an old, incorrect version of the CLR Profiler (not for use with .NET 4). Make sure you're using the right version of the CLR Profiler for the .net environment you're in:

0
Jozef Zelenak On

I've had the same issue. I stoped IIS explicitly myself. Than I was able