Symptom
After newly installed one Introscope Enterprise Manager or upgraded from a lower version, it fails to start.
When you try to start it, it starts but stops immediately.
Navigate to the EM log folder with path <Drive>:\usr\sap\CCMS\apmintroscope\logs and check IntroscopeEnterpriseManager.log.
you will find the following error messages.
"[ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Error activating bean: com.wily.apm.em.monitor.isengard.support.EventMonitorService (com.wily.apm.em.monitor.isengard.support.EventMonitorService)
[INFO] [WrapperSimpleAppMain] [Manager] Shutting down data persistence subsystem
[INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
[ERROR] [WrapperSimpleAppMain] [Manager] Caught Exception while passivating bean com.ca.apm.transactiontrace.appmap.mapper.beans.StandAloneTransactionTraceAppMapProcessorBean@21889e70
[INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
[ERROR] [SpringOsgiExtenderThread-7] [Manager] Uncaught Exception in Enterprise Manager: In thread SpringOsgiExtenderThread-7 and the message is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configPersisterDependentServices': FactoryBean threw exception on object creation; nested exception is org.springframework.osgi.service.ServiceUnavailableException: service matching filter=[(objectClass=com.wily.apm.em.monitor.entity.dependency.IMonitorConfigPersisterDependencyHelper)] unavailable"
Read more...
Product
Keywords
KBA , XX-PART-WILY , Introscope by CA Technologies , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.