Splunk AppDynamics

Error message in log "could not connect to the controller"

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I'm facing one issue in configuring .net application agent with controller after downloading it from wizard. 

I'm getting this error message

"Warn RegistrationChannel Could not connect to the controller/invalid response from controller, cannot get registration information"

Things I tried

1. telnet command failed

2. config.xml file are correct

Please suggest me on how to proceed further. 

Labels (1)
0 Karma

Raunak_Mohanty
Builder

Hi ,

Since telnet is not working it could very well be the issue untill unless telnet is disabled at Controller server.

Can you confirm if you are able to open the Controller UI on the server where Agent is installed ?

Can you verify if you able to Test Controller Connection at AppDynamics Agent Configuration Tool ?

Are there any proxy configured on this server ?

Can you send the Agent logs located at C:\ProgramData\AppDynamics\

Thanks,

Raunak

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

First of all let me tell you that I'm using a Saas version only. 

I checked Controller connection in the agent configuration setup. 
please find the snapshot below. 

0 Karma

Raunak_Mohanty
Builder

Hi,

  Thanks that clarrifies why telnet does not work. Can you send me private message with logs folder attached ? This will help us investigate the issue

Can you confirm if you have <defaultProxy> element defined in web.config ?

Thanks,

Raunak

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hi,



As discussed in the forum, may I know the web.config which you are
mentioning is same as config.xml?
which is available under "C:\Programdata\AppDynamics\DotNetAgent\Config"..
If that is so then the is not specified.

Please let me know how to proceed further.
0 Karma

Mohammed_Rayan
Contributor

jjchristine,

You need to have the connectivity between the controller and the agent in order for the registration to succeed and you have confirmed that the telnet failed,so please check internally if firewall or something in your network is not blocking the communication.

Hope this helps

Regards,

Mohammed Rayan

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...