cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Deepanshu.Grover
AppDynamics Team (Retired)

When upgrading or installing the 4.4 version of the Events Service, use the Enterprise Console. Instructions for installation can be found here.

 

Users who try to manually install the 4.4 Events Service without the Enterprise Console will see the following error message in the logs:

 

 

[2017-11-03T12:43:50,768+01:00] [ERROR] [main] [c.a.common.framework.AbstractApp] Severe error occurred while starting application [events-service-api-store]. Shutdown procedure will commence soon
com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) Error in custom provider, java.lang.IllegalArgumentException: Service key not provided in any source.
at com.appdynamics.analytics.client.module.ServiceKeyProviderModule.provideServiceKey(ServiceKeyProviderModule.java:47)
at com.appdynamics.analytics.client.module.ServiceKeyProviderModule.provideServiceKey(ServiceKeyProviderModule.java:47)
while locating com.appdynamics.analytics.client.module.ServiceKey
for parameter 4 at com.appdynamics.analytics.processor.slm.resource.SlmResourceModule.createSlmConfigService(SlmResourceModule.java:53)
at com.appdynamics.analytics.processor.slm.resource.SlmResourceModule.createSlmConfigService(SlmResourceModule.java:53)
at com.appdynamics.analytics.processor.slm.resource.SlmResourceModule.createSlmConfigService(SlmResourceModule.java:53)
while locating com.appdynamics.analytics.processor.slm.service.performance.SlmPerfConfigService
for parameter 1 at com.appdynamics.analytics.processor.slm.resource.SlmResourceModule.onStart(SlmResourceModule.java:106)
while locating com.appdynamics.analytics.processor.slm.resource.SlmResourceModule
Caused by: java.lang.IllegalArgumentException: Service key not provided in any source.
...

 

 

To resolve this issue, always install the Events Service through the Enterprise Console. See Best practices for AppDynamics 4.4 installation or upgrade for more information.

 

 

Another option is to open the event-service-api-store.properties file and fill in the following 3 properties with the same value (for example, making all of them "12345" works).

  • ad.accountmanager.key.slm
  • ad.accountmanager.key.jf
  • ad.accountmanager.key.service 
Version history
Last update:
‎09-07-2018 10:14 AM
Updated by:
On-Demand Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here