Hi all,
Can anyone provide any information on the following errors logged within /opt/AppDynamics/Controller/logs/server.log
[#|2015-03-05T17:24:28.269+0000|SEVERE|glassfish3.1.2|com.appdynamics.AGENT.AGENT_CONFIGURATION|_ThreadID=65;_ThreadName=Thread-6;|Failed handling transaction config request. The agent type [DOT_NET_APP_AGENT] is not compatible with the agent type [null] specified for the [Service Tier] tier. Is your agent attempting to register to the wrong tier?|#]
[#|2015-03-05T17:24:48.944+0000|SEVERE|glassfish3.1.2|com.appdynamics.AGENT.AGENT_CONFIGURATION|_ThreadID=222;_ThreadName=Thread-6;|Failed handling transaction config request. The agent type [DOT_NET_APP_AGENT] is not compatible with the agent type [null] specified for the [Service Tier] tier. Is your agent attempting to register to the wrong tier?|#]
I had assumed that these were being generated due to remnants of a failed attempt to monitor Windows services a few months back but the changes we'd made to the config.xml configuration files on the target hosts have already been rolled-back.
While everything appears to be working fine, we're keen to isolate the root cause as to why these are being generated
Regards,
Hi Paul,
We see error could have raised when user trying to associate .NET agent node under tier "Service Tier" in an application in controller UI where "Service Tier" is not .NET tier type, refer screenshots to create tier of particular type, and re-running .net agent association for new tier of type .net should resolve the error, let us know if that informaiton heps: