Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
06-28-2017
09:31 AM
- edited on
04-27-2023
02:34 PM
by
Claudia.Landiva
The .NET Agent is not able to connect to the Controller, due to an incorrect account name and account access keys in the .NET Agent configuration.
The following error message appears when using an SSL connection (port 8181/443):
Controller communication failed. Details: The remote server returned an error: (401) Unauthorized.
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level.
NOTE: The SSL error is a red herring. The (401) Unauthorized
piece of the message is important.
The following error message appears when using a non-SSL connection (port 8090/80):
Controller communication failed. Details: The remote server returned an error: (401) Unauthorized.
Verify the account credentials in the Controller UI using the following steps (applicable to v4.3):
It doesn't work that way
Looking into this, @Miguel.Pedraza. In the meantime, feel free to amplify.
Claudia Landivar
Community Manager & Editor
Following up, @Miguel.Pedraza — I reached out to our .NET team and they didn't spot an error in the article. It would help if you could offer more detail about what is going wrong for you.
If you've subsequently resolved the issue, please do share the journey and the result!
Best,
Claudia Landivar
Community Manager & Editor
Previous version of this comment was placed before handling via support case. However, the solution may be complicated by, or vary, based on use of Multi-Tenant Controller and/or License Rules.
There are different access keys and names.
If not checked Multi-Tenant Controller and entered correct "Name" (from controller UI>License>Account) and "Access Key" (from controller UI>License>Rules><app>), then result:
Controller communication failed. Details: The remote server returned an error: (401) Unauthorized.
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level.
If entered else incorrectly, error may also be:
Machine agent on host "<host>" is not authorized to report to this Controller. The host is not included in the server scope for license rule ""
Just providing additional clarity for those that may have similar issue, and solution doesn't quite fit!
Hi, @Arby.Davis! I'm not sure I know what you mean. Would you kindly clarify?
Thank you for sharing that clarification! You're right: very useful to the Community at-large.
-Claudia
Hey What should i put in Server(name/IP)?
I am running my application through IIS it's working fine, but it isn't connecting with the controller
I have followed the instruction given in .net agent installation video.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form