Product: dynatrace 5.5
Issue:
This is a POC load 360 project. We installed dT 5.5. Customer has IIS running on windows 2003. When we installed the dT agent to two of the VM where IIS is running, the w3wp.exe does not show up in the .Net configuration tool on that VM.
Then we installed .net configuration tool 5.0 and 4.2 on the same VM, both tools can see the w3wp.exe.
we already installed the dT server, collector, analysis server 5.5 in the environment, and but we need the .Net agent installed to use those, but seems 5.5 has challenge to identify the w3wp. Is this a known problem? How we can fix it quickly? If not, we may use 5.0 for this POC project.
Thanks
Dong
Answer by Reynaldo B. ·
Yes, I was instrumenting a .NET Application.
Here are the key points that resolved the issue. We opened a case and here is the fix - hopefully the Debug rights gets annotated somewhere in the documentation.
Answer by Reynaldo B. ·
Hi,
Does anyone have the fix for this? The w3wp processes will only show when I check off "Include non-.Net Processes" and when you select the w3wp process you would like to monitor, the Next button is grayed out.
Thanks,
Rey
Are you sure that the w3wp.exe hosts a .NET Application? w3wp is the IIS Worker Thread - so - it can basically host any type of web application. It could be ASP.NET but might be traditional ASP or just static pages.
The .NET Config Tool checks on whether w3wp.exe loads the .NET Runtime. If that is not the case then you wont see it under the list of .NET Processes. So - please verify if the w3wp.exe is really hosting a .NET - based Application. Also - make sure that the application is fully initialized. IIS is only loading the .NET Runtime if you at least had one request to a page that is served by ASP.NET. Easiest is to open your browser and browse to your webpage and then try to hit pages that e.G: end with aspx
Andi
Answer by Kevin J. ·
Dong-
This is a bit strange, but here are a couple of things you can try to still get the w3wp processes instrumented with the 5.5 agent. One, when you open up the list of running processes in the .Net config tool, check the box that says "Include non-.Net Processes" and see if they show up then. Two, you can manually browse to the file location of the w3wp.exe process to add an agent, and then add in the "-ap" argument to specify the app pool. You can get the -ap info by looking at the w3wp process info in Task Manager.
HTH,
Kevin
JANUARY 15, 3:00 PM GMT / 10:00 AM ET