AppD Archive

.NET Agent not connecting to controller: 1992 dllhost 1 10 Warn RegistrationChanne

CommunityUser
Splunk Employee
Splunk Employee

I am getting this error on the AgentLog after installing and configuring the .NET agent

 

1992 dllhost 1 10 Warn RegistrationChannel Could not connect to the controller/invalid response from controller, cannot get registration information

 

The controller is running, I can telnet from the agent machine to the controller machine and I have a JAVA agent working fine (displaying on the controller console).

 

Please advise.

0 Karma

Venu_Babu_Thang
Communicator

Hi,

Thanks for sharing the logs. From the logs, we noticed that there are few proxy authentication failure messages. Can you please check and confirm that, is there any proxy configured on the machine(on the AppDynamics Agent is installed machine) and that proxy requires any authentication?

If you notice any proxy on the agent machine and if it "does not require any authentication" then please run the AppDynamics agent configuration wizard and  on "Controller Configuration" tab, tick the "Use proxy" check box and provide the proxy details then click on "Test Controller connection" button and finish the wizard.

If the "proxy requires any authentication", you would need manually edit the config.xml and need to add the below section for proxy authentication details. This would require reset of AppDynamics Agent CoOrdinator service and IIS.

<proxy host="myproxy.mycompany.com" port="3128" enabled="true">
<authentication enabled="true" user_name="MyProxyUser" password="password" domain="mydomain.com"/>
</proxy>
 
Sample Controller Configuration with Proxy Authentication enabled
 
In this example the agent accesses the controller through the proxy "myproxy.mycompany.com" using proxy authentication. The App Agent for .NET uses the credentials "MyProxyUser@mydomain.com" with password "password" to access the proxy server.
 
 
 
<controller host="mycontroller.mycompany.com">
  <application name="MyDotNetApplicaition" />
  <proxy host="myproxy.mycompany.com" port="3128" enabled="true">
     <authentication enabled="true" user_name="MyProxyUser" password="password" domain="mydomain.com"/>
  </proxy>
</controller>

 

Please let us know if you still face any issues or need any help.

Thanks,

Venu.

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...