Profiling asp.net on IIS 6
Hi guysEager to try to profile a dot.net application we have written. It's running on Windows2003 Server with IIS6. I'm not able to attach to any process on this box, neither locally or remote. The process box is empty, even though I have several sites running Framwork 4, and others running framwork 2.I don't see a single post regarding this issue, so either people are not using this combination at all, or it's just working out of the box for everyone but me.Moving same kind of setup to a IIS 7 server works fine.What should I look for? The IUSER_<machinename> has read access to the bin folder of dottrace. I'm logged in as a member of admin group.Hope you can help meregardsLars Meldgård
Please sign in to leave a comment.
Hello Lars,
Please check that dotTrace and your IIS application has the same rights level: as far as I remember, IIS is always started "as administrator", so try to launch dotTrace "as administrator" as well.
Please let me know if it doesn't help.
Do you mean the application you're profiling or dotTrace?
This is not enough unfortunately. Please right-click on dotTrace's .exe file (or on dotTrace in Start Menu) and select "Run as administrator".
I mean the dot-trace application. The IIS is runing localsystem, and uses IUSER_<machinename> as impersonation.
In Windows Server 2003 there is no such thing as "Run as Adminsitrator". The UAC was not invented then.
I can right-click and select "run as..." then I can enter administrator account information, but that gives the same result.
Lars
Thanks for your patience! So if the problem is not the rights level, could you please give me more details:
1. what exact version of dotTrace do you have? It's available in Help -> About.
2. please open Windows Event Viewer and check that there're no errors like "failed to load profiler". If there are any, please send me the details.
3. in process explorer for each running (when your app is working) w3wp process view which user owns it and send me the names of this users.
4. get dotTrace's core logs; here's the guide, but please enable also MetaDataGt checkbox after step 6.
Hello Lars, thanks for details! Could you please try the latest release - dotTrace 5.5, published yesterday - I guess the issue was fixed in it.
Hello Lars,
Maybe it would be more convinient to you if we try to organize a kind of remote debug session? We'll connect to your machine and look at dotTrace's behaviour; all the operations we perform will be under your full control.
BTW, do you already have dotTrace license? Because if you don't we'd like to give you one for you help in investigating this issue.
Hello Lars,
Unfortunately I have no access to your email in profile :) So please contact me: alexandra.rudenko@jetbrains.com.
For remote debug we usually need Process explorer (http://technet.microsoft.com/en-us/sysinternals/bb896653) and Process monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645) - Windows tools for easier working with processes; Far manager (http://www.farmanager.com/index.php?l=enhttp://www.farmanager.com/index.php?l=en) - a file manager that helps to browse different types of files with ease; and TeamViewer (http://www.teamviewer.com/ru/index.aspx) for connection. Please install them.
As for time, our developer is in same time zone as you, so what about 19:00 today or tomorrow?