Discussion Feed

Hi Venu,   Unfortunately despite trying I couldn't get the agent to work on the test server so I've moved it onto a separate standalone machine.   I'm pleased to say it worked fine there - installation went smoothly with no issues.   Just a shame I couldn't get it to work on the build server but thank you for your support in trying to resolve the issue.  If I ever get time to look back at it and resolve it, I'll update this thread.   Thanks, Ben ... View more

Hi Venu,   Thank you for your help so far however I'm still having issues in the setup.   I've checked and my logged-on account does have access to read / edit the registry. From what I understand when running "AppDynamics.Agent.Winston.exe" if administration access isn't available it should prompt for this level of access and request login under an admin level account (see: https://docs.appdynamics.com/display/PRO42/Resolve+.NET+Agent+Installation+and+Configuration+Issues#Resolve.NETAgentInstallationandConfigurationIssues-admin). I've tried running it under admin access as well but the issue persists. Within the registry: There were no entries within " HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\services". Both "COR_PROFILER" and "COR_ENABLE_PROFILING" existed in " HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\Session Manager\Environment".  I've tried removing, adding, setting etc. these with no luck. Gave full permission to read and edit these keys (tried my own individual account to using "Everybody"). After spending some time with no real progress I moved onto your suggested manual configuration of the agent config.xml file - to help reduce other potential issues I've kept it simple with just the following:     <?xml version="1.0" encoding="utf-8"?> <appdynamics-agent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <controller host="127.0.0.1" port="8090" ssl="false"> <application name="MyImageLibrary"/> <account name="customer1" password="1b8bdcd8-6e18-4891-a14b-1a24449d435d"/> </controller> <machine-agent /> <app-agents> <IIS> <automatic/> </IIS> </app-agents> </appdynamics-agent> Please note this is a trial setup by myself so everything is on the one server (controller / agent and DB collectors).  I know this isn't recommended but thought I'd mention it in case it could be the root cause of the issues I'm experiencing?     At this point, the controller detected the agent connection however it never picks up any data load.  All load is coming via IIS where I have setup a dummy SIT and UAT environments with several APPPOOLS each.  The agent is not listed in the "AppDynamics Agents" page either.   To try and resolve this I then reviewed the agent log again where I kept seeing the below warning:   Could not connect to the controller/invalid response from controller, cannot get registration information. From Googling and reading agent installation documentation I then found the following advice:   Give IIS_IUSR access to the agent log folder - my APPPOOLS are running under ApplicationPoolIdentity  (see: https://docs.appdynamics.com/display/PRO42/Resolve+.NET+Agent+Installation+and+Configuration+Issues#Resolve.NETAgentInstallationandConfigurationIssues-admin). Changed the "Log On As" for "AppDynamics.Agent.Coordinator" from Network Service to Local System. These changes resolved the invalid response from controller issue but despite these changes and more (which I've subsequently rolled back), I'm still not getting data coming through the agent into the controller.  I've also reviewed Event Viewer and I'm seeing the following:   .NET Runtime version 4.0.30319.0 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: 'AppDynamics.AgentProfiler'.  HRESULT: 0x8007007e.  Process ID (decimal): 7572.  Message ID: [0x2504].   Again to avoid any issues for now Windows Firewall is completely disabled.  Attached are the latest agent, winston and more log files.   Any thoughts on what is going wrong here?   Thanks, Ben   ... View more