Installation, Configuration and Deployment Issues
Configuration Manager does not start in command line interface
This error occurs when you haven’t set the environment
variable (ADOBE_JAVA_HOME for turnkey installations and JAVA_HOME
for others). To ensure successful installation, always ensure that
the required parameters are set before you launch the installer
and Configuration Manager.
install.bin fails to launch on Red Hat Enterprise Linux
When you try to run the install.bin executable from the
LiveCycle DVD on a machine running
Red Hat® Enterprise Linux®,
the following error message appears:
/bin/sh:bad interpreter: Permission denied
occurs because Red Hat Enterprise Linux auto-mounts the DVD with noexec
permissions. To resolve this issue and start the LiveCycle installation, perform
Unmount the drive by entering the following
Remount the drive manually by completing the following tasks:
Mount the LiveCycle DVD under the /media/CDROM folder:
mount /dev/hda /media/CDROM
Change to the directory on which the DVD is mounted and run ./install.bin
Turnkey Express mode fails on Turkish Windows Server 2008
The Configuration Manager fails with the ALC-TTN-104-002
error on the Turkish Windows Server 2008 operating system.
To avoid this issue, perform the following steps and rerun the
Open ConfigurationManager.bat from the [LiveCycle root]/configurationManager/bin
folder, in an editor.
Add the following JVM argument:
Save and close the file.
Configuration Manager picks a different JDK than is expected
If you have JDKs from multiple vendors installed on your
system, Configuration Manager may pick a JDK other than the JDK
specified in the PATH environment variable.
To resolve this issue, launch Configuration Manager using ConfigurationManager.bat instead
You can examine the Configuration Manager logs
to ensure that it is using the correct JDK.
Failure to deploy EAR files
Depending on the services you are installing and your system
configuration, you may receive errors when deploying the EAR files.
If this occurs, increase the MaxPermSize on your
application server. For specific instructions on setting this value
on your application server, see the Preparing to Install LiveCycle (Single Server) document.
Incorrect reporting of failure to deploy Content Services (deprecated) EARs
If the system does not meet minimum system requirements
or is heavily loaded, during installation or upgrade to LiveCycle,
Configuration Manager incorrectly reports failure in deploying the
Content Services EAR. This can occur while installing LiveCycle
or upgrading from LiveCycle 9.x or earlier.
In addition, Configuration Manager logs contain the error message:
“Failed to make SOAP RPC call: invoke”. As a result of this incorrect
reporting, Workspace EAR is not deployed and you are unable to proceed
to the next step in the Configuration Manager.
If this error appears, do the following:
Verify that the SOAP request time out is correctly set
per the documentation. See the section “Configuring WebSphere time-out
settings” in the Installing and Deploying LiveCycle for WebSphere document.
From the WebSphere Administrative Console, verify if Content
Services EAR is correctly deployed and running. If you determine
that Content Services EAR is deployed correctly, do one of the following:
In Configuration Manager, deselect the EARs that are already
deployed and running and select only those EARs that are yet to
be deployed (in this case, adobe-workspace-client.ear), and click Deploy.
Deploy the Workspace EAR file (adobe-workspace-client.ear)
manually from WebSphere Administrative Console. After this step,
run the Configuration Manager again, and then select the tasks that
follow the deployment of EARs in Configuration Manager.
Note: When Configuration Manager fails to deploy any
EAR files, you can deploy them manually from the administrative
console of your application server. Follow this general outline
for manually deploying EAR files and continuing the configuration
tasks in Configuration Manager:
the required EAR files from the administrative console of your application
Close the currently running instance of Configuration Manager.
Launch Configuration Manager again, and select the tasks
that follow the deployment of EARs that you completed manually.
Deploying LiveCycle in a distributed environment
If the application server instance (WebSphere) or Managed
Server (WebLogic) is on a different server, and not on the server
with Deployment Manager (WebSphere) or Admin Server (WebLogic),
you must manually deploy the LiveCycle EAR files. If you attempt
to deploy by using Configuration Manager, you may receive an error
message indicating that deployment failed.
If you are experiencing this error when using Configuration Manager
to deploy the EAR files, complete the following procedure.
To deploy the LiveCycle EAR files:
Exit Configuration Manager.
Manually deploy the EAR files. (See the “Manually Deploying”
chapter in Installing and Deploying LiveCycle document for
your application server.)
Run Configuration Manager and select the tasks only after
you deploy LiveCycle EAR files.
LiveCycle component deployment validation failure on WebSphere
On deployment of the LiveCycle component, you may see this
Component deployment failed validation. Cannot connect to server container
If so, complete the following procedure.
To increase the maximum transaction time-out and ORB service values:
In the WebSphere Administrative Console navigation
tree, click Servers > Server Types> WebSphere application servers and,
in the right pane, click the server name.
Under Container Settings, click Container Services > Transaction Service.
Increase all of these time-out values to address this error:
Total transaction lifetime timeout:1800
Async response timeout:1800
Maximum transaction timeout:1800
Restart WebSphere Application Server.
Could not start/create deployment errors on Solaris
Download the GNU tar tool and use it to extract all files
on a Solaris environment. Do not use the Solaris tar command to
extract files otherwise errors similar to the following may occur
due to missing files:
ERROR[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/invoker]] Exception starting filter ReadOnlyAccessFilter
LiveCycle components display older version
After upgrading the LiveCycle server to the latest version
or after deploying a service pack, the about dialog box of LiveCycle
components displays an older version of the application.
After an upgrade or service pack
install, the JBoss service is in a high-memory-use initialization
state and the LiveCycle server is running in a non-clean state.
It causes the LiveCycle components to display an older version.
To display the correct version
in the about dialog box of LiveCycle components, perform the following
After an install, delete the following folders.
Restart the JBoss application server.