Endeca 11.x - EacCommunicationException Error After Running Initialize Services
The following error is being thrown for any new application trying to run initialize_services on:
[01.22.16 16:33:09] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[01.22.16 16:33:10] INFO: Setting definition for application '<app_name>'.
[01.22.16 16:33:10] SEVERE: Caught an exception while checking provisioning.
Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
com.endeca.soleng.eac.toolkit.application.Application setDefinition - Caught exception while defining application '<app_name>'.
Caused by com.endeca.eac.client.EACFault
sun.reflect.NativeConstructorAccessorImpl newInstance0 - null
SEVERE: Caught an exception while checking provisioning.
com.endeca.soleng.eac.toolkit.exception.EacCommunicationException: Caught exception while defining application '<app_name>'.
at com.endeca.soleng.eac.toolkit.application.Application.setDefinition(Application.java:141)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:667)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
Caused by: An error occurred while trying to create the application: Error while running a hibernate transaction: could not insert: [com.endeca.esf.centralserver.service.ApplicationType]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Solution :-
This issue can be caused by a db.lck file in the %ENDECA_CONF%\state\eacstore directory.
Stop all services, delete db.lck file, restart the services and then run initialize_services again.
[01.22.16 16:33:09] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[01.22.16 16:33:10] INFO: Setting definition for application '<app_name>'.
[01.22.16 16:33:10] SEVERE: Caught an exception while checking provisioning.
Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
com.endeca.soleng.eac.toolkit.application.Application setDefinition - Caught exception while defining application '<app_name>'.
Caused by com.endeca.eac.client.EACFault
sun.reflect.NativeConstructorAccessorImpl newInstance0 - null
SEVERE: Caught an exception while checking provisioning.
com.endeca.soleng.eac.toolkit.exception.EacCommunicationException: Caught exception while defining application '<app_name>'.
at com.endeca.soleng.eac.toolkit.application.Application.setDefinition(Application.java:141)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:667)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
Caused by: An error occurred while trying to create the application: Error while running a hibernate transaction: could not insert: [com.endeca.esf.centralserver.service.ApplicationType]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Solution :-
This issue can be caused by a db.lck file in the %ENDECA_CONF%\state\eacstore directory.
Stop all services, delete db.lck file, restart the services and then run initialize_services again.
Discussion (4)
Technical questions and architecture discussionsJoin the Discussion