Showing results for 
Show  only  | Search instead for 
Did you mean: 
AppDynamics Team (Retired)
Why am I seeing : 
"EUM Account <EUM_ACCOUNT_NAME>with key<EUM_ACCOUNT_KEY>could not be provisioned in the EUM PROCESSOR"?


When trying to re-provision the on-premise EUM license, the above error message is seen.

./bin/provision-license <path_to_license_file> 


Complete Stacktrace:

Provisioning license from license file

Unable to add global account names to accounts table for eum_account:<EUM_ACCOUNT_NAME>

java.sql.SQLException: Connections could not be acquired from the underlying database!

        at com.mchange.v2.sql.SqlUtils.toSQLException(

        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(

        at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(


        at com.appdynamics.eumcloud.OnPremLicenseProvisioner.getGlobalAccountNameFromControllerDb(

        at com.appdynamics.eumcloud.OnPremLicenseProvisioner.provisionFromLicenseFile(

        at com.appdynamics.eumcloud.OnPremLicenseProvisioner.main(

Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.

        at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(

        at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(

        at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(

        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(

        ... 5 more


isValid:false, isAlreadyRegistered:true, description:Account <EUM_ACCOUNT_NAME> already registered,

EUM Account <EUM_ACCOUNT_NAME> with key <EUM_ACCOUNT_KEY>  could not be provisioned in the EUM PROCESSOR, error : Account <EUM_ACCOUNT_NAME> already registered


This issue occurs as the EUM account name present in the new on-premise license file is already present inside the EUM DB.



To resolve this issue, please follow the following steps:


  1. Make a copy of your license file in <EUEM>/eum-processor/bin
  2. Make sure your <EUEM>/eum-processor/ has your controller root password for the value of onprem.controllerDbPassword
  3. Navigate to <controller>/bin and enter ./ login-db
  4. Enter use eum_db;
  5. Enter delete from accounts
  6. Enter exit
  7. From the eum-processor directory, run the following script:
    • On Linux: 
      ./bin/provision-license <path_to_license_file> 
    • On Windows:
      bin\provision-license.bat <path_to_license_file>
  8. Restart EUM processor: from <EUEM>/eum-processor enter .bin/ stop and .bin/ start
  9. Disable and re-enable EUM from Instrumentation/Configuration/End User Monitoring

Once this is done, the updated license should reflect under License page and EUM data should start flowing again.

Version history
Last update:
‎08-14-2019 12:56 PM
Updated by: