I am having issues accessing AAM. Am using TCS partner instance. Pl help

Regards

Jignesh





 
 Solved!
 
 [Go to Solution.](/t5/adobe-audience-manager-questions/issues-while-accessing-aam/m-p/298153#M1485)
Hi Jignesh.. are you still having the issue? Some of our engineers have been working on this and I understand access should now be fixed!




[View solution in original post](/t5/adobe-audience-manager-questions/issues-while-accessing-aam/m-p/298153#M1485)
hi,

do you have joy package installed with all necessary packages/dependencies ?

try to search for joy\_node or run joy package examples to find out what is going wrong. Well just had TAC look into it. They restarted the management plane which fixed the issue.

The reason we believe was due to insufficient resource in the management plane at the time of the update.

Thanks Sandeep for your help.




[View solution in original post](/t5/general-topics/app-version-mismatch/m-p/45216#M33220) was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . wow.

good idea with the packages. i have compared it with another system. the package “opennms-plugin-protocol-radius” is missing here. (we use radius login)

i installed it and opennms works now.

but in the meantime i have deactivated 5 adapters. i’ll take that back one by one. let’s see what hap… hi yerhu,

i could imagine, that one of the two following scenarios may cause the issue:

you’re using an outdated version of tk-core. check in your configuration: core/core\_api.yml

you’re using a pipelineconfiguration, which is pointing to a local-path and includes a file like python\_interpreter, i… sorry i took so long to respond on this post. i’ve had a busy week! so i found the issue. in my template for endpoints i realized i accidentally set them to provision using the external ip address of my pbx. changed it to internal and this fixed my issues :stuck\_out\_tongue: sorry for the sign-in trouble! we're looking into this issue and working to fix it on our end so you can keep streaming your favorite shows and movies. hang in there, we will be giving updates here as we get them. in the meantime, try streaming your service over different browsers, your mobile device, or your streaming media players. check out our supported devices.
 
we’ll keep you posted.
 
-directvnowcare we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: hi, 
this is really strange behavior. the only option i see is atm to reset your preferences and check if it works again, then. 
options- > preferences -> reset preferences (left corner) 
hope that helps. 
regards 
christoph someone had the same problem before but they miss out the new windows update permissions for the microphone so try going to the settings > privacy and go to the microphone section and try turning on also the "allows apps to use microphone" under the 1st microphone access option for device.. so basically just try to turn both permissions on and see if that works.