com.aveksa.common.ConfigException: java.lang.NullPointerException
   at com.aveksa.client.datacollector.framework.DataCollectorManager.initCollector(DataCollectorManager.java:627)
   at com.aveksa.client.datacollector.framework.DataCollectorManager.performQuery(DataCollectorManager.java:562)
   at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:480)
   at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:120)
   at com.aveksa.client.component.event.DefaultEventManager.handle(DefaultEventManager.java:60)
   at com.aveksa.client.datacollector.framework.SimpleEventSource.notifyListeners(SimpleEventSource.java:67)
   at com.aveksa.client.component.communication.DefaultCommunicationManager.notifyEvent(DefaultCommunicationManager.java:377)
   at com.aveksa.client.component.communication.ChangeListHandler.applyChanges(ChangeListHandler.java:364)
   at com.aveksa.client.component.communication.ChangeListHandler.access$300(ChangeListHandler.java:58)
   at com.aveksa.client.component.communication.ChangeListHandler$ChangeApplyingRunnable.run(ChangeListHandler.java:275)
   at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
   at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.getReaderClassName(AccountDataCollector.java:226)
   at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.configureReader(AccountDataCollector.java:183)
   at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.init(AccountDataCollector.java:159)
   at com.aveksa.client.datacollector.framework.DataCollectorManager.initCollector(DataCollectorManager.java:621)
   ... 10 more

Other errors that have been seen in the aveksaAgent.log file (/home/{remoteagentuser}/AveksaAgent/logs/aveksaAgent.log) associated with this issue are:

java.lang.NoClassDefFoundError: com/aveksa/collector/accountdata/LdapAccountDataReaderConfig

and/or

java.lang.NoClassDefFoundError: com/aveksa/collector/db/util/DBPerformQueryCallbacks

• RSA Identity Governance & Lifecycle 7.1.0 P07
• RSA Identity Governance & Lifecycle 7.1.1 P01
• RSA Identity Governance & Lifecycle 7.2.0 *

After installing one of the above patches, the next step is to generate and download new RSA Identity Governance & Lifecycle server and client internal certificates. Because of the patch, these newly generated certificates will be of the correct format expected by the latest JRE and JDK versions.

* Note that new installations of RSA Identity Governance & Lifecycle 7.2.0 are not susceptible to this issue. Customers upgrading to 7.2.0 from a previous version are affected and will have to follow the steps in the following section.

Steps:

1. Download and apply patch 7.1.0 P07 or 7.1.1 P01 or 7.2.0 depending on your product version.
2. Regenerate the server and client certificates as per RSA Knowledge Base Article 000038314 -- How to update the root (server) and client certificates in RSA Identity Governance & Lifecycle.

IMPORTANT: If you use AFX, the AFX Server client keystore will also need to be updated as explained in the above-referenced RSA Knowledge Base Article.