[PDF] Troubleshooting LiveCycle ES4 - Adobe Help Center PDF lc

The JVM system output and error logs are valuable tools for troubleshooting problems with your server To view the JVM system output and error logs: 1 Log in to

[PDF] Adobe Acrobat 90 Troubleshooting - Adobe Help Center

3 nov 2015 · Scan issues with the ImageCapture driver on Mac Acrobat-Reader XI Acrobat prompts for admin login when you start from a non-admin

[PDF] How to Login to Adobe Creative Cloud

This tutorial is designed to help you resolve login problems with Adobe's Creative Cloud This often occurs when trying to access any program in the Adobe

[PDF] Adobe Creative Cloud Troubleshooting - Sheffield Hallam University

14 oct 2020 · Is your Adobe account signed in? A common issue with Adobe is that it can sometimes sign you out of the Creative Cloud Desktop Application

[PDF] Adobe Connect Trouble Shooting Guide - ACU

Enable Flash and install the Adobe Connect Add-in Because other students can log in + don't get booted out + have no microphone problems, then the

[PDF] Adobe Reader Settings - BSA E-Filing System

Adobe 9 and X (10) Reader Settings If it is not working at this point, uninstall Adobe Reader and install the latest version available at Log in as the root user

[PDF] How to Support Your End Users - Vitrium Security

User Cannot Login to a Protected PDF File If the issue relates to the protected PDF file, find out which version of Adobe Reader or FoxIt Reader the person

[PDF] DocuSign Troubleshooting Guide

For example, there are known issues with Bluebeam populated fields Users of Adobe Pro DC may find that they are not being prompted to log in to CoSign

[PDF] Adobe pdf online sign in - Squarespace

The software is turned on at the computer level, but needs to log in an Adobe ID Learn about some simple solutions for common Adobe account sign-in issues

[PDF] Adobe Creative Cloud Login Experience Non-Instructional

Adobe Creative Cloud Login Experience Non-Instructional Computers contact the IT Help Desk at 714-564-HELP (4357) if you have any questions or issues

[PDF] adobe login keychain password

[PDF] adobe login pdf

[PDF] adobe logo

[PDF] adobe logo black and white

[PDF] adobe logo png

[PDF] adobe logo vector

[PDF] adobe logos

[PDF] adobe management console login

[PDF] adobe management experience

[PDF] adobe management login

[PDF] adobe management structure

[PDF] adobe management style

[PDF] adobe management system

[PDF] adobe management tool

[PDF] adobe marketing campaign manager

TROUBLESHOOTING ADOBE

LIVECYCLE

ES4

Last updated 1/15/2015

Legal notices

For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. iii

Last updated 1/15/2015

Chapter 1: About This Document

Who should read this document? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2: Troubleshooting Installation and Deployment

Installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

System requirements considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Application server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Database initialization considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

PDF Generator considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation, Configuration and Deployment Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Troubleshooting your application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Troubleshooting your LiveCycle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Troubleshooting with log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3: Troubleshooting Administration Tasks

Login issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Performance considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Uninstall issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Troubleshooting output errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Miscellaneous errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 4: Troubleshooting Error Messages

General Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Database Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

LiveCycle Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Client-side Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Installation Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Miscellaneous Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Troubleshooting CQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Last updated 1/15/2015

Chapter 1: About This Document

This document contains information about how to troubleshoot many installation, configuration and administration

issues that may arise with an Adobe® LiveCycle® Enterprise Suite 4 (ES4) production environment.

Who should read this document?

This guide provides information for administrators or developers who are responsible for installing, configuring,

administering, or deploying LiveCycle components. The information provided is based on the assumption that anyone

reading this guide is familiar with the following:

Conventions used in this document

This document uses the following naming conventions for common file paths.

NameDescriptionDefault value

[LiveCycle root]The installation directory that is used for all LiveCycle modules. The installation directory contains subdirectories for the Adobe®

LiveCycle® Configuration Manager.

This directory also includes directories

relating to third-party technologies.Windows:

C:\Adobe\Adobe LiveCycle ES4

Linux and UNIX:

opt/adobe/adobe_livecycle_ES4

[JBoss root](JBoss Turnkey) The home directory of the application server that runs LiveCycle.C:\Adobe\Adobe LiveCycle ES4\jboss

[Adobe_JAVA_HOME](JBoss Turnkey) The home directory of the Java JDK installed by LiveCycle turnkey.C:\Adobe\Adobe LiveCycle ES4\Java\jdk1.6.0_26

[Workbench_HOME]The home directory of Workbench installed by LiveCycle.Windows(32-bit): Windows (32-bit): C:\Program Files\ Adobe LiveCycle Workbench 11

Windows(64-bit): C:\Program Files (x86)\Adobe

LiveCycle Workbench 11

TROUBLESHOOTING LIVECYCLE ES4

About This Document

Last updated 1/15/2015

Additional information

The resources in this table can help you learn about LiveCycle. [appserver root]The home directory of the application server that runs the services that are part of LiveCycle. JBoss on Windows: C:\jboss

JBoss on Linux, Solaris: /opt/jboss

WebSphere on Windows:

C:\Program Files\IBM\WebSphere\AppServer

WebSphere on Linux and Solaris:

/opt/IBM/WebSphere/AppServer

WebSphere on AIX:

/usr/IBM/WebSphere/AppServer

WebLogic on Windows:

C:\Oracle\Middleware\wlserver_10.3

WebLogic on Linux and Solaris:

/opt/Oracle/Middleware/wlserver_10.3 WL_HOMEThe install directory for WebLogic as specified for the

WL_HOME

environment variable.

WebLogic on Windows C:\Oracle\Middleware\

WebLogic on Linux and UNIX:

/opt/Oracle/Middleware/ [appserverdomain]The domain that you configured on WebLogic server.WebLogic on Windows: se_domain

WebLogic on Linux and UNIX:

base_domain

For information aboutSee

LiveCycle, the LiveCycle solutions, and

development toolsLiveCycle Overview

Preparing your environment for installing or

upgrading to LiveCyclePreparing to Install LiveCycle (Single Server)

Preparing to Install LiveCycle (Server Cluster)

Preparing to Upgrade to LiveCycle ES4

Installing LiveCycle (Single Server)Installing and Deploying LiveCycle Using JBoss Turnkey

Installing and Deploying LiveCycle for JBoss

Installing and Deploying LiveCycle for WebLogic

Installing and Deploying LiveCycle for WebSphere

Name Description Default value

TROUBLESHOOTING LIVECYCLE ES4

About This Document

Last updated 1/15/2015

Getting help

This section describes the steps you should take before you contact Adobe Enterprise Support. If, after reviewing the

LiveCycle documentation, you have not resolved your issues, contact Adobe Enterprise Support. To help expedite your

service, have the following information available: Configuring LiveCycle (Server Cluster)Configuring LiveCycle Application Server Clusters Using JBoss Configuring LiveCycle Application Server Clusters Using

WebLogic

Configuring LiveCycle Application Server Clusters Using

WebSphere

Upgrading to LiveCycleUpgrading to LiveCycle ES4 for JBoss Turnkey

Upgrading to LiveCycle ES4 for JBoss

Upgrading to LiveCycle ES4 for WebLogic

Upgrading to LiveCycle ES4 for WebSphere

Installing LiveCycle - Workbench 11Installing LiveCycle Workbench

Performing general administrative tasks for

LiveCycleLiveCycle Administration Help

Other services and products that integrate with

LiveCyclehttp://www.adobe.com

LiveCycle documentation setLiveCycle Documentation Set

For information about See

Last updated 1/15/2015

Chapter 2: Troubleshooting Installation

and Deployment

Installation considerations

If you have problems installing, configuring, or deploying LiveCycle, make sure that you carefully followed the

instructions in the LiveCycle documents listed in "Additional information" on page 2.

If you installed and configured everything according to the documentation, review the following sections for issues

similar to those you are experiencing.

System requirements considerations

Temporary directory space issues

LiveCycle installer fails to install on a system which has no space available on system temporary directory. In such

cases, you get the error message in the console window indicating that the temporary directory does not have enough

disk space.

To avoid this issue, ensure that your temporary directory has enough space. See the Preparing to Install LiveCycle

(Single Server) guide for information about system requirements. Slow performance of APIs for SharePoint, Documentum, and IBM Content

Manager Connectors on Windows Server 2008

If LiveCycle is deployed on Windows Server 2008, the connector API calls made from Adobe® LiveCycle® Workbench

11 or from LiveCycle SDK to the Microsoft® SharePoint®, EMC® Documentum®, or IBM® Content Manager servers

show slow performance.

To avoid this issue, disable automatic tuning of TCP Receive Window on your repository server or set the fine tuning

level to highlyrestricted.

Use one of the following commands:

netsh interface tcp set global autotuninglevel=highlyrestricted OR netsh interface tcp set global autotuninglevel=disabled

Refer to the Microsoft knowledge base for more information on improving performance on Windows 2008 server.

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

File size limitations for Output service

To generate large files on UNIX systems using the Output Service, you must set the upper limit for file size to greater

than or equal to the file being generated.

To avoid errors when generating PDF documents from large files, change the value for fsize in /etc/security/limits

on UNIX systems to a value large enough to cover all file sizes.

Application server considerations

Verify the following application server settings before you contact Adobe Enterprise Support:

Configuring Solaris 10 memory requirements

Make the following memory configurations to avoid StuckThread issues on a Solaris environment:

Modify the rlim values:

1Locate and open the /etc/system file.

2Locate and modify the rlim values as follows:

set rlim_fd_cur: The initial (soft) maximum number of file descriptors per process. Set this value to 8192 or

more.

set rlim_fd_max: The hard maximum number of file descriptors per process. Set this value to 8192 or more.

(This modification is required only if the default value is lower than 8192). You must have super user privileges to

change this value. Note: The rlim_fd_max value must be equal to or greater than the rlim_fd_cur value.

3Save and close the file.

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

4Restart your computer.

Add additional swap space:

1Increase the swap space so that the total swap space limit exceeds twice the total RAM amount. For example, if you

have 8 GB of RAM, configure the swap space to exceed 16 GB.

2Restart the computer if required.

Verify the updated settings:

1Launch a new shell.

2Type ulimit -n and press Enter.

3Verify the value returned matches the rlim values you have set.

4Type swap -s and press Enter.

5Verify the value returned matches the new swap space value.

If any of the values fail to match the updated settings, ensure you have performed the steps as described and restart

your computer.

Database initialization considerations

If you are having problems initializing the LiveCycle server, consider the following possibilities: If the initialization fails at the beginning of the process, check the following: For more information see "Database Error Messages" on page 48.

Addressing a high number of concurrent calls

A high number of concurrent calls can negatively impact database performance. To avoid poor performance, increase

the maximum connection pool size for the datasource (IDP_DS) to be more than the expected (or actual) number of

concurrent calls. 7

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

Trust store initialization fails

(SQL Server only) When you create an SQL Server user name (for example, admin1) and you create a schema for the

database (for example, admin2), and configure it to be the default schema for the SQL Server account, trust store

initialization fails and a message similar to the one below appears: installed.

Ensure that the SQL Server user name (for example, admin1) and database schema name (for example, admin1)

match, in order for the trust store to initialize successfully.

Security Considerations

XMLForm.exe crashes when SELinux security is in "enforcing" mode

You may encounter problems running LiveCycle on a server where NSA Security Enhanced Linux (SELinux) is in

enforcing mode. With that configuration, a LiveCycle process that calls XMLForm.exe will not run. Users will not be

able to open the associated form in Adobe® LiveCycle® Workspace, and an error message similar to this one appears in

your application server log file: abnormally with error code {3} To correct this problem, change SELinux security to permissive mode.

Upgrade Considerations

Invalid Configuration Manager screens

When upgrading to LiveCycle ES4 from LiveCycle ES2, you can ignore the following Configuration Manager screens

as they are no longer valid:

Error when connecting to the database server

When upgrading to LiveCycle ES4 from LiveCycle ES2, clicking the Verify Connection button on the Adobe LiveCycle

ES4 Database screen might return the following error: Unable to connect to the database server. Communication link failure.Last packet sent to the server was 0 ms ago. In this case, start the database manually and re-run LiveCycle Configuration Manager.

GDS directory not detected

If you are upgrading to LiveCycle ES4 using command-line interface, the upgrade-migrateGDS command may not

detect the default GDS directory from your previous LiveCycle installation. 8

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

In this case, copy the GDS contents manually to the default GDS directory of your LiveCycle ES4 installation.

Content Services (deprecated) EAR fails to deploy during upgrade

Note: Adobe is migrating Adobe® LiveCycle® Content Services ES customers to the Content Repository built on the

modern, modular CRX architecture, acquired during the Adobe acquisition of Day Software. The Content Repository is

provided with LiveCycle Foundation and is available as of the LiveCycle ES4 release.

While upgrading to LiveCycle, deployment of the Adobe® LiveCycle® Content Services 9 (deprecated) EAR may fail

with the following exception message: SchemaBootstr E org.alfresco.util.LogUtil error Schema auto-update failed org.alfresco.error.AlfrescoRuntimeException: A previous schema upgrade failed or was not completed. Revert to the original database before attempting the upgrade again. This issue occurs when the ALF_BOOTSTRAP_LOCK table is present in the LiveCycle database. EAR deployment failure due to high WebSphere resource utilization

Content Services deployment may fail during upgrade if the WebSphere application server resource utilization is high.

To resolve this issue, perform the following procedures. Restoring the contents of lccs_data and the database from backup

1Revert to the original Content Services database by restoring the tables beginning with alf and avm from the

backup copy of the database.

2Restore the contents of the Content Store root location from the backup copy.

Increasing the total transaction lifetime timeout value

1In the WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and

then click the server name.

2Click Container Settings > Container Services > Transaction Service.

3On the Configuration tab, set the value of the Total transaction lifetime timeout setting to 900 seconds.

4Click Apply or OK.

5Restart the application server.

Deploying the EARs in a different order

Initiate the upgrade again. Now, in Configuration Manager, deploy the Content Services EAR before deploying the

other EARs.

1On the Deploy LiveCycle EARs screen, select adobe-contentservices.ear and then click Deploy.

2Once the Content Services EAR has deployed successfully, deselect adobe-contentservices.ear, select the

other EARs, and click Deploy. EAR deployment failure due to the ALF_BOOTSTRAP_LOCK database table

If the ALF_BOOTSTRAP_LOCK table is present in the LiveCycle database, Content Services EAR deployment may

fail during upgrade. 9

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

To resolve this issue, follow these steps:

1Restore the contents of lccs_data and the database from backup. See "EAR deployment failure due to high

WebSphere resource utilization" on page 8.

2Delete the ALF_BOOTSTRAP_LOCK table from the LiveCycle database and reinitiate the upgrade.

3Deploy the Content Services EAR and then deploy the other EARs. See "EAR deployment failure due to high

WebSphere resource utilization" on page 8.

Content Services (deprecated) EAR file is not deployed to all nodes during upgrade

When upgrading to Content Services on a cluster, the Content Services EAR file is deployed to the first node but not

to the other cluster nodes. The following two workarounds resolve this issue, but each has its drawbacks. Review each

workaround to determine which is the best solution for your environment.

Note: With this option, the LiveCycle server can take a long time to start up if you have a lot of content saved in the

Content Services repository. This is because each node of the cluster attempts to recreate the indexes.

Once the node starts successfully, manually copy the indexes directory from that node to the other nodes of the

cluster where you do not plan to run Configuration Manager. Now, start the other nodes of the cluster. The Content

Services EAR file will now be successfully deployed to all cluster nodes.

Note: Although this workaround is time-consuming to implement, it ensures minimal server downtime during

startup.

LiveCycle ES4 Service Pack 1 fails to install

On upgrading from LiveCycle ES2 SP2 to LiveCycle ES4 SP1, LiveCycle configuration manager (LCM) encounters

following errors java.lang.IllegalArgumentException: Comparison method violates its general contract!

To resolve the issue, add the following JVM argument in the generic JVM argument list of application server:

PDF Generator considerations

The following topics address issues encountered with Adobe® LiveCycle® PDF Generator 11 and their respective

resolutions. 10

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

Configure Acrobat to run Microsoft Office macros

PDFMaker disables macros while converting Microsoft Word and Microsoft Excel documents to PDF using PDF

Generator, even when you have enabled macros in the File Type Settings using Administration Console.

To prevent PDFMaker from disabling the macro, you must set the value for the following registry to 0:

For more information about this known issue with Acrobat, see http://kb2.adobe.com/cps/877/cpsid_87775.html.

Configuring PDF Generator to convert MS Office files to PDF format

It is a known issue that on some LiveCycle servers, a DCOM permission policy must be modified to use PDF Generator

to convert Microsoft Office application files successfully. Otherwise, the following error message appears:

INFO [STOUT] com.jniwrapper.win32.com.ComException: COM object method returns error code:

0x80004005; E_FAIL (Unspecified error)

Microsoft has documented the required steps in a knowledge base article on the Microsoft Help and Support site.

Known issue when a LiveCycle server is accessed over a Telnet session

Native to PDF conversions fail with an error when you access a LiveCycle server running on Windows Server 2008

using the Telnet service and start the application server using a batch script.

To prevent this issue, start the Telnet service with the Allow service to interact with desktop option selected. You can

select this option when you modify the properties of the Services panel in Windows Server 2008. Resolving paths when converting Excel files to PDF file

When you use PDF Generator to convert an Excel file to a PDF file, and the Excel file contains a file name and path

function ( &[Path]&[File]) in the header or footer, unexpected results may occur. When converting the file, PDF

Generator copies it to a temporary location on the LiveCycle server and performs the conversion on that copy. As a

result, the file name and path functions in the Excel document resolve to the temporary file name and location, and

those values appear in the generated PDF file.

Installation, Configuration and Deployment Issues

General 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 11

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

Red Hat® Enterprise Linux®, the following error message appears:

This occurs because Red Hat Enterprise Linux auto-mounts the DVD with noexec permissions. To resolve this

issue and start the LiveCycle installation, perform these steps:

1Unmount the drive by entering the following command:

umount /media/CDROM

2Remount the drive manually by completing the following tasks:

mkdir /media/CDROM

3Mount the LiveCycle DVD under the /media/CDROM folder:

mount /dev/hda /media/CDROM

4Change to the directory on which the DVD is mounted and run ./install.bin

Configuration issues

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 Configuration Manager:

1Open ConfigurationManager.bat from the [LiveCycle root]/configurationManager/bin folder, in an editor.

2Add the following JVM argument:

-Duser.language=en -Duser.country=US

3Save 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 of

ConfigurationManager.exe.

You can examine the Configuration Manager logs to ensure that it is using the correct JDK.

Deployment issues

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. 12

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

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:

1Verify 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.

2From 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:

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:

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:

1Exit Configuration Manager.

2Manually deploy the EAR files. (See the "Manually Deploying" chapter in Installing and Deploying LiveCycle

document for your application server.)

3Run 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 error: Component deployment failed validation. Cannot connect to server container

If so, complete the following procedure.

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

To increase the maximum transaction time-out and ORB service values:

1In the WebSphere Administrative Console navigation tree, click Servers > Server Types> WebSphere application

servers and, in the right pane, click the server name.

2Under Container Settings, click Container Services > Transaction Service.

3Increase all of these time-out values to address this error:

4Restart 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 java.lang.ClassNotFoundException: org.jboss.invocation.http.servlet.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.

Reason

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.

Resolution

To display the correct version in the about dialog box of LiveCycle components, perform the following steps:

1After an install, delete the following folders.

2Restart the JBoss application server.

Troubleshooting your application server

This section describes possible issues you may encounter with your application server and how to troubleshoot them

using log files.

Application server does not start

If the server does not start, perform these checks: 14

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

application server.

JBoss Application Server issues

Content Services deployment fails after a JBoss server restart

If deployment of Content Services fails after a JBoss Application Server restart, add Java processes and mysqld-max-

nt.exe to the safe-processes list of your anti-virus software. The error code 13 that appears in the logs is a permission-denied error.

WebLogic Server issues

Configuration Manager hangs when redeploying an EAR file

Configuration Manager may hang at an incomplete stage when redeploying a LiveCycle EAR file, and fail to deploy

the new EAR file.

This problem occurs occasionally when WebLogic Server does not release a currently deployed EAR file. Perform the

following procedure to correct this problem:quotesdbs_dbs17.pdfusesText_23

[PDF] [PDF] Troubleshooting LiveCycle ES4 - Adobe Help Center

TROUBLESHOOTING ADOBE

LIVECYCLE

Last updated 1/15/2015

Legal notices

Legal notices

Last updated 1/15/2015

Contents

Chapter 1: About This Document

Chapter 3: Troubleshooting Administration Tasks

Chapter 4: Troubleshooting Error Messages

Last updated 1/15/2015

Chapter 1: About This Document

Who should read this document?

Conventions used in this document

NameDescriptionDefault value

LiveCycle® Configuration Manager.

This directory also includes directories

C:\Adobe\Adobe LiveCycle ES4

Linux and UNIX:

Windows(64-bit): C:\Program Files (x86)\Adobe

LiveCycle Workbench 11

TROUBLESHOOTING LIVECYCLE ES4

About This Document

Last updated 1/15/2015

Additional information

JBoss on Linux, Solaris: /opt/jboss

WebSphere on Windows:

C:\Program Files\IBM\WebSphere\AppServer

WebSphere on Linux and Solaris:

WebSphere on AIX:

WebLogic on Windows:

C:\Oracle\Middleware\wlserver_10.3

WebLogic on Linux and Solaris:

WL_HOME

WebLogic on Windows C:\Oracle\Middleware\

WebLogic on Linux and UNIX:

WebLogic on Linux and UNIX:

For information aboutSee

LiveCycle, the LiveCycle solutions, and

Preparing your environment for installing or

Preparing to Install LiveCycle (Server Cluster)

Preparing to Upgrade to LiveCycle ES4

Installing and Deploying LiveCycle for JBoss

Installing and Deploying LiveCycle for WebLogic

Installing and Deploying LiveCycle for WebSphere

Name Description Default value

TROUBLESHOOTING LIVECYCLE ES4

About This Document

Last updated 1/15/2015

Getting help

WebLogic

WebSphere

Upgrading to LiveCycle ES4 for JBoss

Upgrading to LiveCycle ES4 for WebLogic

Upgrading to LiveCycle ES4 for WebSphere

Performing general administrative tasks for

LiveCycleLiveCycle Administration Help

Other services and products that integrate with

LiveCyclehttp://www.adobe.com

For information about See

Last updated 1/15/2015

Chapter 2: Troubleshooting Installation

Installation considerations

See also

System requirements considerations

Temporary directory space issues

Manager Connectors on Windows Server 2008

11 or from LiveCycle SDK to the Microsoft® SharePoint®, EMC® Documentum®, or IBM® Content Manager servers

Use one of the following commands:

TROUBLESHOOTING LIVECYCLE ES4

Troubleshooting Installation and Deployment

Last updated 1/15/2015

File size limitations for Output service

Application server considerations

See also

Configuring Solaris 10 memory requirements

Modify the rlim values:

1Locate and open the /etc/system file.

2Locate and modify the rlim values as follows: