Thanks Cody, but I believe the developer is missing my point.
The "old" ASP.NET applications offer out-of-the-box transformations for XML conifguration files but not for JSON files. This means the target AppDynamics controller name cannot be changed for build configurations as part of the MSbuild process, e.g. UAT or PROD build profiles. I've attached two screenshots showing the issue created by the latest 4.4 release.
Note, if this was a .net core project then it wouldn't be a problem as they do support JSON config transformations.
As far as I'm aware the fact the target deployment is Azure makes zero difference.
For now the client has rolled back to version 4.3 of the nuget package where AppDynamics still use the supported XML transformations. T here will come a time when they'll need to upgrade to the latest version resulting in them adding additional process to transform JSON files though.
Thanks again, Ben.
... View more
A client of ours today upgraded their Azure agent nuget version to 4.4 which removed the previous AppDynamics XML configuration file into a JSON file. Just out of curiosity I'm wondering why this approach has been taken?
Reason for asking is that as far as I'm aware, out of the box within ASP.NET (note, this is not a .net core project) JSON configuration files do not support transformation as they would with say a "web.config" or "app.config" file. Please do let me know if I'm wrong though.
If I'm right, AppDynamics customers not using CI CD processes won't necessarily be expecting this configuration shift leaving them confused.
Also, your latest 4.4 documentation for the Azure app service has the wrong configuration paths:
From testing it they go into ~/"AppDynamics/AppDynamicsConfig.json".
... View more
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.
... View more
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">
<account name="customer1" password="1b8bdcd8-6e18-4891-a14b-1a24449d435d"/>
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?
... View more
I'm getting up to speed with AppDynamics 4.3 trial self-hosted install on a Windows Server 2016 server.
The controller installs fine and is accessible, however when I install the agent it then fires off "AppDynamics Agent Configuration" which then, unfortunately, triggers a message box stating "requested registry access is not allowed". I've checked your documentation and tried running as admin etc. but without luck.
I've attached the install log file.
Any help would be appreciated.
... View more
Unfortunately it appears to have gone down again, albeit it looks to be a different issue?
I've uploaded the last agent log the customer sent to me (before the issue was resolved late yesterday).
If you could please check to see if all is OK at the backend, I'll also check with the client to see if they're aware and to see if they've made any other changes.
... View more
We have a client trialing AppDynamics and currently we're not able to see database lists or executed SQL statements etc. The client has sent us the DB logs from AppDynamics where we can see various errors similar to the below:
[Event-Uploader-Scheduler-2] 18 Jul 2017 14:41:07,799 WARN DBMeasurementUploader - Fail to upload Query Stats Measurements: com.singularity.ee.rest.ResponseReadException: Error in controller in processing binary request Write Query Stats - null at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:65) at com.singularity.ee.rest.controller.request.dbmon.WriteQueryStatsRequest.<init>(WriteQueryStatsRequest.java:30) at com.singularity.ee.agent.dbagent.task.reporter.DBMeasurementUploader.uploadrQueryStats(DBMeasurementUploader.java:100) at com.singularity.ee.agent.dbagent.task.reporter.DBMeasurementUploader.run(DBMeasurementUploader.java:117) at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335) at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236) at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694) at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726) at java.lang.Thread.run(Unknown Source)
The client is question is using your SaaS platform and from looking at other similar support tickets I believe we may need your help to get this up and running correctly? Unfortunately the customer has 10 days left in their trial period so time is tight.
Please let me know what we need to do to resolve this.
... View more