AppD Archive

Deep Link Failed: Location(AD_HOME) does not exist. - Linux x64

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Everytime that I login in appdynamics controller (http://localhost:8090/Controller) I get this messege "Deep Link Failed: Location(AD_HOME) does not exist." and the page stay in loading for a long time before show something, after that everything works fine, apparently.

If I open other brownser tab and login again happens the same.

So, anyone know how can I solve this problem? Because it takes some minutes util everything works fine.

Thanks,

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

We are having the same issue right now, after upgrading the controller from 4.0 to 4.1, again Linux x64

I have a ticket raised, and will let you know what the outcome is.

Regards,

Bill

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

We are receiving the same on a trial license we are standing up for PoC testing in our lab.

Edit:   We do eventually get the regular landing page, and then everything works fine.    It is about a 60-90 second delay.

SUSE Linux Enterprise Server 11 (x86_64)

VERSION = 11

PATCHLEVEL = 1

 

Running controller version 4.1.0.4  

 

Jason

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I got the following in a message from another comunity member, and it has resolved the issue for us. I would suggest you back everything up first, before you try it:


-------------------
Go to your <hostname>:8090/controller/admin.jsp

once logged in go to the accounts settings (in my case customer1)

Edit and find the block that starts with End User Monitoring (EUM)

blank out all the text boxes and make sure that the drop down lists are set to Not Set

save it

log out and log back in to the normal controller interface.
-------------------

Hope that helps?

My worry, when I tried it, was that it would break EUM. However, once you restart the Controller, the information you blanked gets re-populated, yet the error doesn't return.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

This worked for me an fixed the problem.

Thank you!

 A further note on this.  If you had Splunk Integration setup and you did an upgrade to 4.1 I had an extra set of Splunk integration parameters added.  I had to remove these from the list on the same page noted above.   It was right above the EUEM section.

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 ...