Posts tagged "configuration"

Troubleshooting Common LiveCycle Configuration Errors

- 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.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (4 votes cast)

Updates to the install documentation

We updated the Installing and Deploying LiveCycle ES2 for JBoss (Single Server) guide recently to capture how to configure the JBoss Application Server to run as a service on Windows Server 2003 and 2008. While free tools to achieve this for 32-bit Windows/Java environments have existed for a while, you can now use the JBoss Web Native Connector for both 32-bit- and 64-bit environments.

We also updated the Prepare to Install/Upgrade LiveCycle ES2 documentation. The revised guides now explicitly mention support for JBoss Enterprise Application Platform (EAP) 4.3, besides JBoss 4.2.0 and 4.2.1.

You can download the latest PDFs from the LiveCycle Developer Center.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)