Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

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

like image 552
Ben Lesh Avatar asked Aug 24 '10 14:08

Ben Lesh


People also ask

How to debug ASP net application running on IIS?

To start debugging, select the profile name in the toolbar, such as <project profile name>, IIS Express, or <IIS profile name> in the toolbar, select Start Debugging from the Debug menu, or press F5. The debugger pauses at the breakpoints. If the debugger can't hit the breakpoints, see Troubleshoot debugging.


Video Answer


2 Answers

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

like image 122
Jozef Zelenak Avatar answered Sep 24 '22 10:09

Jozef Zelenak


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

like image 20
Caffreys Avatar answered Sep 26 '22 10:09

Caffreys