EUM license failed error

[CommunityUser]

I woud appriciate if anyone can help me.

I licensed EUM license but, it failed.

lisence file is in it.
property_eum-account-name=XXXXXXXXXXXXXXX-a0Q34000002q5JSEAY 
(masked)

is license file bad? or any reason?

--------------------------------------------

EUM：euem-64bit-linux-4.4.3.23183.sh
APM：4.4.3.4, build 4.4.3.20077
java version "1.8.0_181"

--------------------------------------------
log
[root@eum01 eum-processor]#  ./bin/provision-license  /root/license.lic
Reading the license file at /root/license.lic
Successfully read the license file
Provisioning from license file /root/license.lic
Register the account ...
Exception in thread "main" java.lang.NullPointerException
        at com.appdynamics.eumcloud.LicenseProvisioner.getEventServiceKey(LicenseProvisioner.java:186)
        at com.appdynamics.eumcloud.LicenseProvisioner.registerAccount(LicenseProvisioner.java:164)
        at com.appdynamics.eumcloud.LicenseProvisioner.provisionLicense(LicenseProvisioner.java:47)
        at com.appdynamics.eumcloud.OnPremLicenseProvisionCommand.provisionLicense(OnPremLicenseProvisionCommand.java:89)
        at com.appdynamics.eumcloud.OnPremLicenseProvisionCommand.run(OnPremLicenseProvisionCommand.java:81)
        at com.appdynamics.eumcloud.OnPremLicenseProvisionCommand.main(OnPremLicenseProvisionCommand.java:29)

07 9 2018 03:54:00.781 +0900  main                  AD.SqlAccountStore         ERROR
 |      Exception caught while querying account store:
 |      SQL: select * from accounts where account_name=?
 |      Params: [XXXXXXXXXXXXXXX-a0Q34000002q5JSEAY] masked
 |      java.sql.SQLException: Connections could not be acquired from the underlying database!
 |              at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
 |              at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:529)
 |              at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
 |              at com.appdynamics.eumcloud.data.sql.SqlDBManager.getConnection(SqlDBManager.java:59)
 |              at com.appdynamics.eumcloud.data.sql.SqlAccountStore.runQuery(SqlAccountStore.java:527)
 |              at com.appdynamics.eumcloud.data.sql.SqlAccountStore.findAccountByName(SqlAccountStore.java:334)
 |              at com.appdynamics.eumcloud.LicenseProvisioner.registerAccount(LicenseProvisioner.java:163)
 |              at com.appdynamics.eumcloud.LicenseProvisioner.provisionLicense(LicenseProvisioner.java:47)
 |              at com.appdynamics.eumcloud.OnPremLicenseProvisionCommand.provisionLicense(OnPremLicenseProvisionCommand.java:89)
 |              at com.appdynamics.eumcloud.OnPremLicenseProvisionCommand.run(OnPremLicenseProvisionCommand.java:81)
 |              at com.appdynamics.eumcloud.OnPremLicenseProvisionCommand.main(OnPremLicenseProvisionCommand.java:29)
 |      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(BasicResourcePool.java:1319)
 |              at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
 |              at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
 |              at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
 |              ... 9 more
 |
 +---------------------------------------------------------------------------------------

[CommunityUser · Accepted solution]

Hi @Anonymous

We are sorry to hear that you are facing issues with EUM license.

At the first glance, it is not clear what type of License you have: Browser, Mobile, or Device.

We would recommend referring to the EUM License documentation, Compatibility Metrics, and a solution posted to a similar question as yours.

Let us know how it goes. Don't hesitate to update the thread if you have further questions or concerns.