Agent Activate button missing in Configuration Tool
I'm using Dynatrace 4.1.0.2974. In the DynaTrace Client, I can see my Collector listed under System Information. In the Agent Configuration tool, the Agent is also showing up; however in the Agents Overview in the DynaTrace Client, it is not. Do I need to Activate the Agent specifically or the checkbox next to it indicates that the Agent is active and should then show up in Agents Overview?
Please let me know if anyone has any pointers?
thanks for your time.
-Rohit
Hi Rohit
Just to double check. You are talking about the .NET Agent Configuration tool - correct?
If you have configured your agent in that tool you need to make sure to start or restart your application after you have made these changes. If you configure your agent and the .NET Application is already running there is no way for us to inject the agent on-the-fly. It gets loaded during startup. So - make sure that
a) all configuration elements for your agent in the .NET Config Tool are correct, e.g: correct collector name, port, ...
b) restart your .net application. If it is an ASP.NET Application you have to recycle the application pool. Also - for ASP.NET Apps it might be necessary to do an IISRESET after your initial installation of the agent. And - last but not least for ASP.NET: make sure that you at least hit the web application once with your browser. IIS only starts the ASP.NET Process when there is at least on requests
Andi
Thanks Andi for your reply.
Yes, I’m restarting the application after I have made changes in the Agent Configuration tool (Start-> Programs-> Dynatrace 4.1.0-> Agent Configuration for .NET).
When you say .Net Agent Configuration tool are you referring to this ? If yes then you are right and it does lists my .NET process (with status - ready for operation) however I’m not seeing the Agent under “Agents Overview” in the Client resulting in no sessions being recorded for the application. The Application is a winforms application so no asp.net processes involved.
Hi Rohit
Seems we are both talking about the same .net configuration tool 
If your .NET Application is actually an ASP.NET Web Application hosted by IIS you may need to restart iis (iisreset) or restart the server in order for our agent to be correctly loaded.
Please also have a look at the troubleshooting guide: TroubleShooting Guide - Installation Problems
Andi
Hi Andi, I'm not able to see the guide, I get "You cannot view this page due to inherited restrictions".
The issue I have is that the Agent is picking up my application (as evident in the configuration tool where it displays my application with a status - "Ready for Operation") but the Agent does not showing up in the Agents Overview in the Client hence doesnt record anything. Also I dont see any Logs on the client machine for Agent. I have verified that the user has read/write permissions to the log directory/file as set in the Agent configuration tool.
seems I gave you a wrong link. check this one: KB-256 dynaTrace .NET Agent not working
You want to make sure the following things work
a) the global environment variables are set correctly - COR_PROFILER and COR_ENABLEPROFILING
b) there is no other tool installed that overrides these env-variables of dynaTrace - I typically check with a tool like Process Explorer whether the env-variables for the w3wp.exe processes are the same as for the systema and not overwritten by somebody else
c) make sure you have configured the correct host:port information - otherwise our .net agent wont be able to connnec to the dynaTrace Collector
if you still have problems after checking these settings I recommend contacting our support team or enablement services to have a closer look at your environment. I am sure it is then just a simple step that is missing
Andi
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 