You have to create a custom health rule based on the specific eventid, and then create a Policy to trigger an alert. Just make sure to use Type as the name of extension. You can try using custom event type = "WindowsEventLogMonitor", this needs to be the name of the extension, as provided in the extension.xml file.  Also the event properties exposed are  eventid eventsource machinename ... View more

Hello Vijay, Looks like profiler is not yet hooked in and therefore app agent dlls have not been injected into process. do a restart of agent coordinator service followed by an IISreset and apply enough load on these w3wp.exe(so that agents can hook in) Check environment variables and dlls loaded via process explorer tool.  If the agent still doesn't come up, then try the below approach and let us know the output. Download Microsoft's Process Explorer tool to perform the following steps and provide details -  Then launch Process Explorer as an Administrator. Then Go To View -> Lower Pane View -> DLLs. Select a couple of the "w3wp" processes corresponding to your IIS applications which are configured to be instrumented by the .NET agent and it will load all the DLLs loaded in the process in the lower pane. Please provide this screenshot. Then right-click on those "w3wp.exe" processes and select "Properties". Go to the ".NET Assemblies" tab and provide us the screenshot. Then, go to the "Environment" tab and provide us the screenshot. Then follow the same steps for parent "svchost.exe" process of these w3wp.exe and provide the same set of screenshots for it too. I am attaching the screenshot for your reference.  Also, could you please check the values for the following environment variables at the system level environment variables. COR_ENABLE_PROFILING = 1 COR_PROFILER = AppDynamics.AgentProfiler InternalAppDynamicsAgent_ProfilerProcesses = w3wp ... View more

BadImageFormatException is something we have seen recently and our Devs are currently working on the fix. The fix will be coming very soon. The root cause is a race condition when making IL transformations, which introduces nulls in the transformed IL. This issue we're seeing is caused by a race condition where the agent injects multiple methods into the application for tracking business transactions.  One of the methods injected is calling another method where the method signature exists but the method body doesn't yet.  This results in the BadImageFormatException you're seeing.  Meanwhile, we have a workaround configuration to work around this issue without losing visibility. This workaround requires the following changes: Edit the config.xml to add the following xml element within the <app-agents> element. <profiler> <full-no-dependency-mode enabled="false" /> </profiler> Save the Config.xml file. Restart the AppDynamics.Agent.Coordinator service. Restart the instrumented process (the application pool in this case). So our recommendation is to make the configuration change above, which will resolve the issue you're seeing now without having to wait for a new agent version.  Once the new agent version comes out we recommend upgrading to that version(4.5.18) and then removing the config above from the configuration file.  ... View more

Hi Sasidhar, From the shared error "The remote server returned an error: (407) Proxy Authentication Required", looks like there is any proxy configured on the Machine level or instrumented application level or network level and your proxy needs credentials. Could you please verify and configure proxy in the config.xml  for the communication between Agent and controller. You can find more information related to this in Proxy Element section link below  https://docs.appdynamics.com/display/PRO45/.NET+Agent+Configuration+Properties For example -  <controller host="mycontroller.example.com"> <application name="MyDotNetApplicaition"/> <proxy host="myproxy.example.com"port="3128"enabled="true"> <authentication enabled="true"user_name="MyProxyUser"password="password"domain="mydomain.com"/> </proxy> </controller> After configuring the proxy configuration. You would need to restart the Agent coordinator service and then restart the IIS/instrumented application services. After that apply the load and then check the behavior. Thanks Satyam ... View more