- Shishir Pandey, Software Engineer @ Adobe
The following lists the common configuration errors, why they occur, and steps to troubleshoot them.
- Error: Component: com.adobe.xxx version: 10.0.3.20120511.1.316647 introduced a new service, it should not be patched
Reason: This issue generally occurs when order of operation in Configuration Manager is incorrect after applying a patch. That is, the deployment of the component is performed before configuring and deploying of the EAR files. It usually occurs in command line execution because each step is run separately in this mode.
Workaround: Re-run the Configuration Manager and ensure that configuration and deployment of ear is done before deploying components.
- Error: In case of Weblogic, a “null” folder gets created after deploying EARs.
Workaround: Stop the managed-server first, followed by the node manager, and finally stop the admin-server. Restart them in reverse order. You will see a folder Adobe gets created in the Weblogic domain.
- Error: The following error occurred while executing this line: java.lang.OutOfMemoryError: Java heap space
Reason: This issue generally occurs if the XMX setting is missing from the server configuration.
Workaround: Increase the XMX value for the server or restart the server, and re-run Configuration Manager.
- Error: weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=, on Resource AdobeService Operation: set , Target: EnableSSL at com.adobe.livecycle.bootstrap.bootstrappers.CoreBootstrapper.bootstrap(CoreBootstrapper.java:60)
Reason: This error generally occurs due to missing JMX policies in case of Weblogic during the Initialize LiveCycle step of the Configuration Manager.
Workaround: Configure JMX as described in Creating JMX policies for database initialization. Restart the server and re-run the Initialize LiveCycle step.