livecycle es error code reference - adobe - adobe support · pdf fileadobe livecycle es about...

bbc

LiveCycle® ES Error Code Reference

Adobe® LiveCycle® ESFebruary 2009 Update 1

© 2009 Adobe Systems Incorporated. All rights reserved.

Adobe® LiveCycle® Update 1 (8.2) Error Code Reference for Microsoft® Windows®, UNIX®, and LinuxEdition 2.1, February 2009

If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end-user license agreement.

The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide.

Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any permission required from the copyright owner.

Any references to company names, company logos and user names in sample material or sample forms included in this documentation and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.

Adobe, the Adobe logo, Acrobat, and LiveCycle are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

BEA Weblogic Server is a registered trademark and BEA WebLogic Platform is a trademark of BEA Systems Inc.

IBM, AIX, DB2, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.

Red Hat and Boss are registered trademarks of Red Hat, Inc. in the United States and other countries.

Sun, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

UNIX is a registered trademark of The Open Group in the US and other countries.

All other trademarks are the property of their respective owners.

This product contains either BSAFE and/or TIPEM software by RSA Security, Inc.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).

This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).

This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).

This product includes copyrighted software developed by E. Wray Johnson for use and distribution by the Object Data Management Group (http://www.odmg.org/).

Portions © Eastman Kodak Company, 199- and used under license. All rights reserved. Kodak is a registered trademark and Photo CD is a trademark of Eastman Kodak Company.

Powered by Celequest. Copyright 2005-2008 Adobe Systems Incorporated. All rights reserved. Contains technology distributed under license from Celequest Corporation. Copyright 2005 Celequest Corporation. All rights reserved.

Single sign-on, extending Active Directory to Adobe LiveCycle ES provided by Quest Software “www.quest.comlidentity-management” in a subsequent minor release that is not a bug fix (i.e., version 1.1 to 1.2 but not 1.1.1 to 1.1.2) of the Licensee Product that incorporates the Licensed Product.

The Spelling portion of this product is based on Proximity Linguistic Technology.

©Copyright 1989, 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1990 Merriam-Webster Inc. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 2003 Franklin Electronic Publishers Inc. © Copyright 2003 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 2004 Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1991 Dr.Lluis de Yzaguirre I Maura © Copyright 1991 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1990 Munksgaard International Publishers Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1995 Van Dale Lexicografie bv © Copyright 1996 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1990 IDE a.s. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 2004 Franklin Electronics Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1992 Hachette/Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 2004 Bertelsmann Lexikon Verlag © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 2004 MorphoLogic Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 1990 Williams Collins Sons & Co. Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. © Copyright 1993-95 Russicon Company Ltd.

© Copyright 1995 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

© Copyright 2004 IDE a.s. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.

Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.

Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101, consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60, 60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.

4

Contents

About This Document.................................................................................................................. 6What’s in this document? ............................................................................................................................................................ 6Who should read this document? ............................................................................................................................................ 6Conventions used in this document ....................................................................................................................................... 6Additional information................................................................................................................................................................. 8

1 Using LiveCycle ES and Application Server Log Files ............................................................... 9LiveCycle ES log files ..................................................................................................................................................................... 9

LiveCycle ES log file error messages ................................................................................................................................. 9OutOfMemoryError ........................................................................................................................................................ 9404 File not found ...........................................................................................................................................................11Class not found.................................................................................................................................................................11JNDI name not found .....................................................................................................................................................11

Application server log files........................................................................................................................................................12

2 Error Code Reference................................................................................................................. 13Applications and Services .........................................................................................................................................................14LiveCycle Configuration Manager..........................................................................................................................................15Convert PDF ...................................................................................................................................................................................25Document Security ......................................................................................................................................................................26Encryption.......................................................................................................................................................................................38File Provider....................................................................................................................................................................................40LiveCycle Foundation bootstrapping ...................................................................................................................................40FDI ......................................................................................................................................................................................................45Job Manager...................................................................................................................................................................................47Repository .......................................................................................................................................................................................47Trust Store.......................................................................................................................................................................................55User Manager.................................................................................................................................................................................56XMLForm service ..........................................................................................................................................................................59LiveCycle Barcoded Forms ES ..................................................................................................................................................59LiveCycle Content Services ES .................................................................................................................................................60LiveCycle Forms ES ......................................................................................................................................................................63LiveCycle Output ES ....................................................................................................................................................................67LiveCycle PDF Generator ES .....................................................................................................................................................75LiveCycle PDF Generator 3D ES...............................................................................................................................................98LiveCycle Rights Management ES ....................................................................................................................................... 101LiveCycle Workbench ES (JBoss) .......................................................................................................................................... 107LiveCycle Workspace ES.......................................................................................................................................................... 107Web Services ............................................................................................................................................................................... 126JBoss............................................................................................................................................................................................... 126MySQL............................................................................................................................................................................................ 128

3 Error Code Reference for Upgrading LiveCycle ES................................................................129Upgrading the LiveCycle ES server ..................................................................................................................................... 130Upgrading repository .............................................................................................................................................................. 133Upgrading LiveCycle Barcoded Forms .............................................................................................................................. 136Upgrading LiveCycle Workflow............................................................................................................................................ 136

Adobe LiveCycle ES ContentsLiveCycle ES Error Code Reference 5

3 Error Code Reference for Upgrading LiveCycle ES (Continued)Upgrading LiveCycle Workflow 7.2.2 to LiveCycle ES on JBoss/MySQL ................................................................ 138Upgrading LiveCycle PDF Generator ................................................................................................................................. 139Upgrading LiveCycle Policy Server ..................................................................................................................................... 141Upgrading LiveCycle Form Manager ................................................................................................................................. 141Upgrading LiveCycle Forms .................................................................................................................................................. 145Upgrading LiveCycle Print ..................................................................................................................................................... 146Upgrading core components................................................................................................................................................ 147Upgrading Font Manager Module ...................................................................................................................................... 150Upgrading Trust Manager Module ..................................................................................................................................... 151Upgrading LiveCycle Assembler.......................................................................................................................................... 156Upgrading LiveCycle Document Security ........................................................................................................................ 157Upgrading watched folders................................................................................................................................................... 159Upgrading Content Repository Connector for EMC Documentum........................................................................ 161Upgrading Content Repository Connector for IBM FileNet ....................................................................................... 162

6

About This Document

This document contains information to help you diagnose problems that may occur when you are installing, configuring, upgrading, or running Adobe® LiveCycle® ES (Enterprise Suite) Update 1 (8.2).

This document will be updated regularly to incorporate changed and new information about how to handle error conditions.

What’s in this document?This document provides information about the log files in which you can find information about errors in LiveCycle ES, Adobe LiveCycle Configuration Manager, and the application server you are using (JBoss®, BEA WebLogic®, or IBM® WebSphere®.)

Who should read this document?This document provides information for administrators or developers who are responsible for installing, configuring, administering, or deploying LiveCycle ES components. The information provided is based on the assumption that those reading this guide is familiar with Java™ 2 Platform, Enterprise Edition (J2EE) application servers; Linux®, and Microsoft® Windows®, IBM AIX®, or Sun™ Solaris™ operating system; MySQL, Oracle®, DB2®, or SQL Server database servers; and web environments.

Conventions used in this documentThis document uses the following naming conventions for common file paths.

Name Default value Description

[LiveCycleES root] Windows: C:\Adobe\LiveCycle8\

Linux and UNIX®:/opt/adobe/livecycle8/

The installation directory used for all LiveCycle ES solution components. This directory contains subdirectories for LiveCycle Configuration Manager, the Adobe LiveCycle ES SDK, and each LiveCycle ES solution component installed (along with the product documentation). This directory also includes directories that relate to third-party technologies.

Adobe LiveCycle ES About This DocumentLiveCycle ES Error Code Reference Conventions used in this document 7

Most of the information about directory locations in this document is cross-platform (all file names and paths are case-sensitive on Linux and UNIX®). Any platform-specific information is indicated as required.

[JBoss root] JBoss Application Server on Windows:C:\jboss

JBoss Application Server on Linux:/opt/jboss

Turnkey installation of LiveCycle ES (JBoss on Windows):C:\[LiveCycleES root]\jboss

The home directory of the JBoss Application Server that runs the LiveCycle ES services.

[WebLogic root] WebLogic Server on Windows: C:\bea\weblogic92\

WebLogic Server on Linux and Solaris:/opt/bea/weblogic92

WebLogic Server on AIX:/usr/bea/weblogic92

The home directory of the WebLogic Server that runs the LiveCycle ES services.

[WebSphere root] 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

The home directory of the WebSphere Application Server that runs the LiveCycle ES services.

BEA_HOME WebLogic Server on Windows: C:\bea

WebLogic Server on Linux and UNIX: /opt/bea

The installation directory for WebLogic Server as specified for the BEA_HOME environment variable.

[appserverdomain] WebLogic Server on Windows:C:\bea\user_projects\domains\base_domain

WebLogic Server on Linux and UNIX: /opt/bea/user_projects/domains/base_domain

The domain that you configured on WebLogic Server.

[dbserver root] Depends on the database type and your specification during installation.

The location where the LiveCycle ES database server is installed.

Name Default value Description

Adobe LiveCycle ES About This DocumentLiveCycle ES Error Code Reference Additional information 8

Additional informationThe resources in this table can help you learn more about LiveCycle ES.

For information about See

General information about LiveCycle ES and the solution components

LiveCycle ES Overview

What’s new in the LiveCycle ES release What’s New for LiveCycle ES

LiveCycle ES terminology LiveCycle ES Glossary

Other services and products that integrate with LiveCycle ES

www.adobe.com

LiveCycle ES solution components partners.adobe.com/public/developer/main.html

Performing administrative tasks for LiveCycle ES Administering LiveCycle ES

All documentation available for LiveCycle ES Adobe LiveCycle ES Documentation

LiveCycle ES release information and last-minute changes that occur to the product

Release Notes

Patch updates, technical notes, and additional information about this product version

LiveCycle Technical Support

http://www.adobe.com/go/learn_lc_overview_82

http://www.adobe.com/go/learn_lc_whatsNew_82

http://www.adobe.com/go/learn_lc_glossary_82

http://www.adobe.com/go/learn_lc_administration_82

http://www.adobe.com/go/learn_lc_releaseNotes_82

http://www.adobe.com

http://www.adobe.com/go/learn_lc_support_82

http://partners.adobe.com/public/developer/main.html

http://www.adobe.com/go/learn_lc_documentation_82

9

1 Using LiveCycle ES and Application Server Log Files

Log files are useful for LiveCycle ES and application server failure analysis and may be required when dealing with Adobe Enterprise Support.

This section lists the common log files that you can use to diagnose LiveCycle ES problems. It also describes some of the most common errors that may be included in the LiveCycle ES log file.

LiveCycle ES log filesThis section describes how to troubleshoot LiveCycle ES using the log files.

LiveCycle ES log file

By default, the LiveCycle ES log file is located in the [LiveCycleES root] directory and named log.txt.

LiveCycle Configuration Manager log file

By default, the LiveCycle Administration Console log file is in [LiveCycleES root]/ConfigurationManager/log and is named lcm.0.log or similar (the higher the number, the more recent the logs). The log files are useful for LiveCycle Configuration Manager failure analysis.

LiveCycle ES log file error messages

This section describes some of the most common errors that may be included in the LiveCycle ES log file.

OutOfMemoryError

These types of errors are typically caused by one of these issues:

● Running out of threads

● Threads and memory allocations

Running out of threads

Many different types of threads are available; however, they fall into two categories: Java threads and native threads. All threads that are running within a Java™ virtual machine (JVM™) are Java threads (java.lang.Thread class inside Java). The native code (C++/C) creates native threads that are scheduled and managed by the operating system. Here are the key differences between the two types:

● Operating system tools (such as perfmon or Task Manager) knows only about native threads.

● Java threads are created and managed by LiveCycle ES code, application server, or the JVM itself.

Because the operating system has no visibility into Java threads, when you monitor threads by using operating system tools such as perfmon, you are monitoring only native threads. The only way to get details into Java threads is to get a Java thread dump. The process about how to get a Java thread dump varies, depending on your application server and JVM. Refer to the manufacturer’s documentation.

Adobe LiveCycle ES Using LiveCycle ES and Application Server Log FilesLiveCycle ES Error Code Reference LiveCycle ES log file error messages 10

Incidentally, the implementation of the JVM is done in C/C++ code and that JVM code maps Java threads to native threads. This mapping can be either 1:1 (1 Java thread to 1 native thread) or N:1 (multiple Java threads to 1 native thread). The details of how this mapping works will be specific to the JVM vendor; however, 1:1 mapping is a typical default. This means that each Java thread will have a corresponding native thread. The number of Java threads has no definite limit; however, because 1:1 mapping is typical and the number of native threads has definite limits, you can run out of Java threads as well. This limit applies per process (JVM being a single process) and varies on each operating system. You can assume that the limit will be in the thousands (but less than 10,000). Regardless of this number, having several hundreds of threads is a performance problem because the operating system has to schedule up to that many threads.

Threads and memory allocation

Another common issue for threads pertains to memory allocations. When a new Java thread is allocated, a fixed amount of memory is required for the thread's stack. This thread stack space is a tunable parameter (-Xss option for JVM) and the default is ~512 KB. Therefore, if you have 1000 threads, 500 MB of memory will be required just for the thread's stacks. This memory will compete with all the other memory allocations being done in the JVM (for example, what LiveCycle ES allocates) and will create memory allocation issues.

In practice, when the JVM cannot allocate memory or create threads, it throws an OutOfMemory exception back to the caller. Along with this exception will be a stack trace and a reason for throwing the exception. This reason is very important to take notice of; it will give you further clues to what the problem may be.

The following code is an example of a message that displays two errors and their associated reason codes:

"unable to create new native thread: java.lang.OutOfMemoryError: unable to create new native thread java.lang.OutOfMemoryError: Java heap space"

These errors mean that the JVM could not create more threads for one of these reasons:

● The per-process thread limit is reached.

● The thread stack could not be allocated.

To determine the exact cause, you need to get a thread dump (also known as Java jump). Thread dump will generally be called javacore.xxxx.txt and reside under an application server's log directories. Much information will be inside the thread dump, but you can quickly determine the number of threads by counting the occurrences of the TID: token on the list. A typical entry will look like this example:

"Thread-1227" (TID:0x106948F0, sys_thread_t:0x78996DA0, state:R, native ID:0x191C) prio=54XESTACKTRACE at java.net.SocketInputStream.socketRead0(Native Method)4XESTACKTRACE at java.net.SocketInputStream.read(SocketInputStream.java(Compiled Code))4XESTACKTRACE at java.io.BufferedInputStream.fill(BufferedInputStream.java(Compiled Code))4XESTACKTRACE at java.io.BufferedInputStream.read1(BufferedInputStream.java(Compiled Code))4XESTACKTRACE at java.io.BufferedInputStream.read(BufferedInputStream.java(Compiled Code))4XESTACKTRACE at com.sun.jndi.ldap.Connection.run(Connection.java(Compiled Code))4XESTACKTRACE at java.lang.Thread.run(Thread.java:567)

Adobe LiveCycle ES Using LiveCycle ES and Application Server Log FilesLiveCycle ES Error Code Reference LiveCycle ES log file error messages 11

If you find thousands of threads, you are probably running out of threads. Developers should be able to identify obvious culprits by scanning the stack traces of these threads.

Note: Thread dumps are typically intrusive and require that you restart the application server afterward.

If the thread count is in the hundreds, the reason for the java.lang.OutOfMemory error is not the thread limit. Reduce the thread stack size (-Xss option mentioned above), rerun LiveCycle ES, and check whether the problem disappears.

404 File not found

If you see this error, perform these checks:

● Confirm the problem in the browser’s access log.

● Confirm that the EAR file deployed properly and that the application initialized.

● If the URL is intended for the HTTP server, check that the file exists. Look in the error_log file or error.log file for the full file name that the web server is looking for.

● (JBoss) Make sure the URL uses the correct case (it is case-sensitive).

● (JBoss) Check whether the web application context root (first part of the URL) exist in the uriworkermap.properties file of the JK plug-in configuration.

● (JBoss) If the file is a JSP, does the file exist in the EAR? This option will be confirmed by the absence of an entry in the HTTP server's error log file.

Class not found

If you see this error, check whether any of these problems exist:

● The class path setting is invalid or missing.

● The JAR file is obsolete.

● A compilation problem exists in the class.

JNDI name not found

If the symptom is an exception stack trace showing javax.naming.NameNotFoundException: jdbc/<badName>, check whether the expected name is spelled correctly; if it is not, fix the code.

To correct most common JNDI exceptions, follow this process:

1. Check the JNDI tree on the LiveCycle ES application server. Does the name used appear in the tree?

● If yes, it is most likely that your code has not properly set up the InitialContext object being used for the look-up, and the look-up is being done on a JNDI tree that is not the one the resource is listed in. For the property values to use, see the Installing and Deploying LiveCycle ES document for your application server.

● If no, continue to step 2.

2. Check whether the resource appears in the JNDI tree under a name other than the name that is listed in the look-up?

● If yes, you are using the incorrect look-up name. Provide the correct name.



Adobe LiveCycle ES Using LiveCycle ES and Application Server Log FilesLiveCycle ES Error Code Reference Application server log files 12

3. Review the application server logs during startup. If the application server is configured to make this resource available but it is not working properly, an exception appears here. Did an exception appear?

● If yes, review the exception and stack trace. If the NameNotFoundException is a symptom of another problem based on your investigation of the server logs, go to the troubleshooting steps for that problem.


4. If the resource is not listed in the JNDI tree and no exception appears at startup to explain why it is not available, the most probable issue is that the application server is not configured properly to make that resource available. Review the application server configuration. Is it configured to make this resource available?

● If no, refer to the Installing and Deploying LiveCycle ES document for your application server.

● If yes, this problem is not one of the common ones that cause this issue. Contact Adobe Support.

Application server log filesThe application server log files are useful for application server and LiveCycle ES bootstrapping failure analysis. The default log files are in the following location for your application server:

JBoss: [LiveCycleES root]/jboss/server/all/log or [JBoss root]/server/all/log and named boot.log and server.log

WebLogic: /var/log/httpd/error_log

WebSphere: [WebSphere root]/logs/server1/trace.log

If the log file does not provide enough information to help you troubleshoot problems, you can specify the level of tracing in the log file to increase logging details. (See “Troubleshooting” in Administering LiveCycle ES.)




13

2 Error Code Reference

This section lists the error codes that may appear or may be written to log files when you are installing, configuring, or running LiveCycle ES. The error code tables also provide the causes of the error codes and the actions to take. This section will be updated regularly to incorporate new and changed information about how to handle error conditions.

This table lists the areas of LiveCycle ES where error messages are generated.

Area of LiveCycle ES See...

LiveCycle ES services “Convert PDF” on page 25

“Document Security” on page 26

“Encryption” on page 38

“File Provider” on page 40

“FDI” on page 45

“Job Manager” on page 47

“Repository” on page 47

“Trust Store” on page 55

“User Manager” on page 56

“XMLForm service” on page 59

“Web Services” on page 126

“LiveCycle PDF Generator ES” on page 75

Tools and utilities “Applications and Services” on page 14

“LiveCycle Configuration Manager” on page 15

“LiveCycle Foundation bootstrapping” on page 40

LiveCycle ES solution components “LiveCycle Barcoded Forms ES” on page 59

“LiveCycle Content Services ES” on page 60

“LiveCycle Forms ES” on page 63

“LiveCycle Output ES” on page 67

“LiveCycle PDF Generator ES” on page 75

“LiveCycle PDF Generator 3D ES” on page 98

“LiveCycle Rights Management ES” on page 101

“LiveCycle Workbench ES (JBoss)” on page 107

“LiveCycle Workspace ES” on page 107

Application servers and databases “JBoss” on page 126

“MySQL” on page 128

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Applications and Services 14

Applications and Services

Error code Cause Action

ALC-AAC-003-000 Required parameter was null when configuring a service or an endpoint.

Specify the required parameter.

ALC-AAC-004-000 Endpoint category with the specified name already exists.

Endpoint category name must be unique. Choose a different name when adding the category.

ALC-AAC-006-000 Error occurred when previewing archive. The archive file is corrupted or invalid, which prevents previewing the content of the LiveCycle ES archive (LCA) file.

Re-export the LCA file and then open it to review its contents.

ALC-AAC-007-000 Unexpected archive status. Archive status when import, preview, or removal is successful is reported as Import Complete, Preview Complete, or RemoveComplete. Any other status indicates an import error, a preview error, a removal error, or an unknown error.

Address the issue identified in the Cause section of the log message.

ALC-AAC-008-000 Error importing archive. Address the issue identified in the Cause section of the log message.

ALC-AAC-009-000 Error removing archive. Address the issue identified in the Cause section of the log message.

ALC-AAC-010-000 An archive already exists with the ID [application name]. The application name for imported archives must be unique.

Rename application by opening the LCA file and changing application ID in the application.xml file.

ALC-AAC-011-000 Failed to locate the archive. User attempted to perform an action with an archive ID that could not be located.


ALC-AAC-012-000 Failed to locate category. User attempted to perform an action with a category ID that could not be located.


ALC-AAC-013-000 Error viewing archive. An error occurred while opening a specific archive for viewing.


ALC-AAC-014-000 Failed to load system context. An error occurred while attempting to retrieve the User Management system context.


ALC-AAC-015-000 Failed to locate endpoint. User attempted to perform an action with an endpoint that could not be located.

Add a new endpoint.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Configuration Manager 15

LiveCycle Configuration ManagerFor all error messages that occur while running LiveCycle Configuration Manager (LCM), you should first review the log files for more details that can reveal the cause of the error.


ALC-LCM-000-001 Invalid JDK version detected. Set JAVA_HOME to the supported JDK version that is listed in Preparing to Install LiveCycle ES Single Node or Preparing to Install LiveCycle ES Clustering.



ALC-LCM-000-010 Installation context undeterminable. Installation may be invalid.

LiveCycle Configuration Manager gets its installation context from {INSTALL_ROOT}\licenses\LFS_Foundation.properties.

This happens if this file is missing.

This should not happen in production.

Reinstall the LiveCycle Configuration Manager.

ALC-LCM-000-011 Target application server undeterminable or invalid. Installation may be invalid.

LiveCycle Configuration Manager determines the target appserver from the AppServer property as set in the {INSTALL_ROOT}\licenses\LFS_Foundation.properties

If this value is missing or does not match a supported value, this can occur.

Should not happen in production.

Reinstall LiveCycle ES.

http://www.adobe.com/go/learn_lc_prepareInstallsingle_82


http://www.adobe.com/go/learn_lc_prepareInstallcluster_82











ALC-LCM-000-012 Target operating system undeterminable or invalid. The installation may be invalid.

LiveCycle Configuration Manager determines the target appserver from the OSFileSetIntendedFor property as set in the {INSTALL_ROOT}\licenses\LFS_Foundation.properties

If this value is missing or does not match a supported value, this can occur.


Action is to reinstall.

ALC-LCM-000-013 Installation context undeterminable. LiveCycle Configuration Manager root directory, {0}, does not exist.

Happens if this directory does not exist.


No action would be an bug that should never release.

ALC-LCM-000-020 Failed to start LiveCycle Configuration Manager. This error occurs when LiveCycle Configuration Manager cannot start the user interface.

Uninstall and reinstall LiveCycle ES.

ALC-LCM-000-030 Failed to load JAR file into class path. JAR file {0} does not exist.


ALC-LCM-000-100 Failed to load plug-in [pluginName]. This error can occur if a problem exists with the plug-in or the installation.

Review the logs for more information. Uninstall and reinstall LiveCycle ES.

ALC-LCM-010-100 Failed to configure core. This error can occur because of insufficient disk space or a problem with the installation.

Review the logs for more information.

ALC-LCM-010-110 Failed to find credential with alias [aliasName].

LiveCycle Configuration Manager uses LiveCycle ES SDK to communicate with the server to query whether the credential to be imported already exists.

This error occurs if a problem exists with the SDK or the application server.

Review the log and application server log for more details.



ALC-LCM-010-111 Failed to import credential [credentialName].

LiveCycle Configuration Manager uses LiveCycle ES SDK to communicate with the server to query whether the credential to be imported already exists.

This error occurs if a problem exists with the SDK or the application server.

Review the LiveCycle Configuration Manager log and application server log for more details.

ALC-LCM-010-112 Failed to import credential [credentialName]. The credential password provided is invalid.

Review the credential password and try retyping the password in LiveCycle Configuration Manager.


ALC-LCM-010-120 Failed to configure. Review the LiveCycle Configuration Manager log and application server log for more details.

ALC-LCM-010-180 Failed to initialize BAM Server. Review the LiveCycle Configuration Manager log and application server log for more details.

ALC-LCM-010-181 Failed to initialize BAM Server. Failure to connect due to invalid host [hostName]. The host server is not available or is invalid.

Ensure that the host value provided is valid and the host is online.

ALC-LCM-010-182 Failed to initialize BAM. Failure to connect due to invalid port [portName]. The port is invalid.

Ensure that the port value provided is valid and BAM Server is running on that port.

ALC-LCM-010-183 Failed to initialize BAM. Error occurred on server [{0} : {1}].

BAM Server is running but failed to service the request.


ALC-LCM-010-184 Failed to initialize BAM. Missing file [fileName].

BAM Server file to import is missing from the [LiveCycleES root]/deploy directory.


ALC-LCM-010-200 Failed to merge EAR files.

This error may be caused by a file permission problem or insufficient disk space.

Review the LiveCycle Configuration Manager log files for details.

ALC-LCM-010-201 Failed to merge EAR files. File does not exist [fileName].


ALC-LCM-010-300 Failed to generate licensed JAR file.

This error may be caused by a file permission problem or insufficient disk space.

Review the LiveCycle Configuration Manager log files for details.



ALC-LCM-030-101 Failed to deploy EAR file. EAR file not found on disk.


ALC-LCM-030-102 Failed to deploy EAR file. [fileName] does not exist in archive [name].


ALC-LCM-030-103 Failed to deploy EAR file. Failed to load application information from EAR: {0}.


ALC-LCM-030-110 Failed to deploy EAR file. Could not undeploy [archiveName].

Undeploy EAR file manually by using the application server administration console and then try again.

ALC-LCM-030-111 Failed to deploy EAR file. Could not stop application [applicationName].

Undeploy EAR file manually by using application server administration console and then try again.

ALC-LCM-030-112 Failed to deploy EAR file. Failed to deploy [archiveName].


ALC-LCM-030-113 Failed to deploy EAR file. Failed to start application [applicationName].


ALC-LCM-030-200 Failed to deploy component [componentName].


ALC-LCM-030-201 Failed to deploy component. Failed to connect to service container.


ALC-LCM-030-202 Failed to deploy component [componentName]. Component archive not found on disk.


ALC-LCM-030-203 Failed to deploy component {0}. Component not found on server.


ALC-LCM-030-204 Failed to deploy component. Component archives could not be copied to working directory.


ALC-LCM-030-205 Failed to deploy component. [componentName] does not exist in archive {1}.


ALC-LCM-030-206 Failed to deploy component. Failed to load component information from component: [componentName].


ALC-LCM-030-207 Failed to deploy component {0}. Cluster member clock times may not be synchronized. Review the logs and cluster configuration.

ALC-LCM-030-300 Failed to deploy LCA [fileName]. Address the issue identified in the Cause section of the log message.



ALC-LCM-030-301 Failed to deploy LCA. LCA file [fileName] not found on disk.


ALC-LCM-030-302 Failed to deploy LCA. {0} does not exist in archive {1}.


ALC-LCM-030-303 Failed to deploy LCA. Failed to load archive information from EAR: {0}.


ALC-LCM-035-200 Component deployment failed validation for [componentName].


ALC-LCM-035-201 Component deployment failed validation for [componentName]. Component archive not found on disk.


ALC-LCM-035-202 Component deployment failed validation for [componentName]. Component not found on server.


ALC-LCM-035-203 Component deployment failed validation. Failed to connect to service container.


ALC-LCM-035-300 LCA deployment failed validation. Address the issue identified in the Cause section of the log message.

ALC-LCM-035-301 LCA deployment failed validation. LCA [fileName] is not deployed.


ALC-LCM-080-100 Failed to generate version report. Address the issue identified in the Cause section of the log message.

ALC-LCM-100-000 Failed to perform application server operation. {0}


ALC-LCM-100-010 Failed to connect to application server. Application server information, login information may be invalid, or server is not running or accessible.


ALC-LCM-100-011 Failed to connect to application server. Application server host or port may be invalid.


ALC-LCM-100-012 Failed to connect to application server. Administrator ID or password may be invalid.


ALC-LCM-100-013 Failed to connect to application server. Target server instance [instanceName] does not exist.


ALC-LCM-100-014 Failed to connect to application server. Target cluster instance [componentName] does not exist.




ALC-LCM-100-020 Operation timed out. Address the issue identified in the Cause section of the log message.

ALC-LCM-100-030 SSL not configured properly. Ensure that the certificate is accepted by the host computer.

ALC-LCM-100-040 Supported version validation failure. Address the issue identified in the Cause section of the log message.

ALC-LCM-100-041 Supported version validation failure. The detected version of the target application server is [versionNumber1], which does not meet the minimum supported version [versionNumber2].


ALC-LCM-100-042 Supported version validation warning. The detected version of the target application server is [versionNumber1], which exceeds the supported version [versionNumber2], as known at the time of release.


ALC-LCM-100-050 Cannot locate server ports for WC_defaulthost or WC_defaulthost_secure in the available virtual hosts\nfor: {0}.

This may prevent access to the server.

Refer to the WebSphere Application Server configuration documentation.

ALC-LCM-100-060 Server {0} is an administration server. Only managed servers should be used as LiveCycle ES servers.

ALC-LCM-100-070 Server has pending changes that require a restart.

Restart the server and re-run configuration.

ALC-LCM-101-013 Failed to connect to application server. Target server instance [instanceName] does not exist.


ALC-LCM-101-014 Failed to connect to application server. Target cluster instance [instanceName] does not exist.


ALC-LCM-101-020 Failed to run JACL scripts. Review the logs for further details.

ALC-LCM-101-030 Failed to parse JACL {0} stream ''{1}'' Address the issue identified in the Cause section of the log message.

ALC-LCM-110-000 Failed to configure application server. Address the issue identified in the Cause section of the log message.

ALC-LCM-110-010 Failed to configure server settings. Address the issue identified in the Cause section of the log message.

ALC-LCM-110-020 Failed to configure JMS. Address the issue identified in the Cause section of the log message.



ALC-LCM-110-030 Failed to configure data source. Address the issue identified in the Cause section of the log message.

ALC-LCM-110-040 Failed to get server information. Address the issue identified in the Cause section of the log message.

ALC-LCM-110-050 Failed to get version information from application server.


ALC-LCM-110-110 Failed to deconfigure data source. Address the issue identified in the Cause section of the log message.

ALC-LCM-110-130 Failed to deconfigure JMS. Address the issue identified in the Cause section of the log message.

ALC-LCM-110-150 Failed to deconfigure server settings Address the issue identified in the Cause section of the log message.

ALC-LCM-120-000 Server configuration failed validation. Address the issue identified in the Cause section of the log message.

ALC-LCM-120-001 Server configuration failed validation. Incorrect number of web servers exists


ALC-LCM-120-002 Server configuration failed validation. Error sending validation request.


ALC-LCM-120-003 Server configuration failed validation. Host path invalid {0}.


ALC-LCM-120-100 Server configuration failed validation. JVM settings failed.


ALC-LCM-120-101 Server configuration failed validation. Unexpected Thread Count [value].


ALC-LCM-120-102 Server configuration failed validation. Unexpected Socket Reader [value].


ALC-LCM-120-103 Server configuration failed validation. Unexpected Thread Max Time [value].


ALC-LCM-120-104 Server configuration failed validation. Expected JVM arguments not found.


ALC-LCM-120-105 Server configuration failed validation. Expected Xmx setting not found.


ALC-LCM-120-106 Server configuration failed validation. Expected Xms setting not found.


ALC-LCM-120-107 Server configuration failed validation. Unexpected JTA time-out [value].


ALC-LCM-120-200 Server configuration failed validation. JMS settings failed.




ALC-LCM-120-201 JMS settings failed validation. Failed to find/look up queue {0}. Queue may not be configured or may have failed to come online.


ALC-LCM-120-202 JMS settings failed validation. Failed to validate queue [queueName].


ALC-LCM-120-203 JMS settings failed validation. Failed to find/look up topic [topicName]. Topic may not be configured or may have failed to come online.


ALC-LCM-120-204 JMS settings failed validation. Failed to validate topic [topicName].


ALC-LCM-120-205 JMS settings failed validation. Failed to find or look up connection factory [factoryName]. Connection factory may have failed to come online.


ALC-LCM-120-206 JMS settings failed validation. Failed to validate connection factory [factoryName].


ALC-LCM-120-207 JMS settings failed validation. Failed to validate queue connection factory [factoryName].


ALC-LCM-120-208 JMS settings failed validation. Failed to validate topic connection factory [factoryName].


ALC-LCM-120-209 JMS settings failed validation. Bus is not functioning properly.

Delete Bus [busName], delete tables that start with SIB, and rerun the configuration for JMS.

ALC-LCM-120-210 JMS settings failed validation. Failed to locate any queue factories.


ALC-LCM-120-211 JMS settings failed validation. Failed to locate any topic factories.


ALC-LCM-120-212 JMS settings failed validation. Failed to validate connection factories.


ALC-LCM-120-300 Data source settings failed validation. Address the issue identified in the Cause section of the log message.

ALC-LCM-120-301 Data source settings failed validation. Failed to find/look up data source [datasourceName]. Data source may not be configured or may have failed to come online.




ALC-LCM-120-302 Data source settings failed validation. Failed to determine database type for data source [datasourceName].


ALC-LCM-120-303 Data source settings failed validation. Failed to connect to database for data source [datasourceName].


ALC-LCM-120-304 Data source settings failed validation. Failed to validate data source [datasourceName].


ALC-LCM-120-305 Data source settings failed validation. Failed to execute query: {0}.


ALC-LCM-130-100 Database settings failed validation. Address the issue identified in the Cause section of the log message.

ALC-LCM-130-101 Database settings failed validation. Unsupported database type [databaseType].


ALC-LCM-130-102 Database settings failed validation. Driver class [className] cannot be loaded.


ALC-LCM-130-103 Database settings failed validation. SQL error code{0}, state{1}.


ALC-LCM-130-104 Database settings failed validation. Failed to execute query: {0}.


ALC-LCM-130-105 Database settings failed validation. Failed to find driver {0} in archive: {1}.


ALC-LCM-130-106 Database settings failed validation. Failed to locate Schema {0} in database {1}.


ALC-LCM-140-100 Failed to control server. Address the issue identified in the Cause section of the log message.

ALC-LCM-140-102 Failed to start server [serverName]. Address the issue identified in the Cause section of the log message.

ALC-LCM-140-104 Failed to stop server [serverName]. Address the issue identified in the Cause section of the log message.

ALC-LCM-140-106 Failed to determine server type. Address the issue identified in the Cause section of the log message.

ALC-LCM-200-001 Failed to connect to LiveCycle ES service container. Service container information or login information may be invalid, or the server is not running or accessible.


ALC-LCM-800-001 Property file {0} does not exist. Address the issue identified in the Cause section of the log message.



ALC-LCM-800-002 Missing required property {0} for cluster topology.


ALC-LCM-800-003 Property {0} from property file {1} can not be empty.


ALC-LCM-800-004 Missing required property {0} from property file {1}.


ALC-LCM-800-010 Could not retrieve password for property {0}. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-000 Failed to turnkey deploy. Deploy EAR files manually to JBoss by following instructions in Installing and Deploying LiveCycle ES for Jboss or Upgrading to LiveCycle ES for JBoss

ALC-LCM-999-010 The ports required by [componentName] are still in use {1}. Another instance may be running or another application may be using some of the required ports.


ALC-LCM-999-020 Windows turnkey service {0} does not exist. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-021 Service shutdown failed for: {0}. Unexpected service state: {1}.


ALC-LCM-999-022 Service shutdown failed for: {0}. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-031 Service startup failed for: {0}. Unexpected service state: {1}.


ALC-LCM-999-032 Service startup failed for: {0}. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-040 JBoss did not come online. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-051 Soap port missing from properties. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-052 Server port missing from properties. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-053 Cannot resolve pop3 path for: {0}. Address the issue identified in the Cause section of the log message.

ALC-LCM-999-054 Cannot resolve driver path for: {0}. Address the issue identified in the Cause section of the log message.


http://www.adobe.com/go/learn_lc_installJBoss_82


http://www.adobe.com/go/learn_lc_upgradeJBoss_82


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Convert PDF 25

Convert PDF

ALC-LCM-999-055 WebLogic domain could not be created for: {0}.


ALC-LCM-999-056 Windows service could not be created for: {0}.




ALC-CNP-001-002 Invalid option value. Verify option values.

ALC-CNP-001-104 Error while loading options. Contact the system administrator.

ALC-CNP-001-201 Invalid ZIP Document. Verify the ZIP format of the document.

ALC-CNP-001-202 Error creating directory. Verify the ZIP format of the document.

ALC-CNP-001-301 Cannot convert PDF file to PostScript. Verify that the input PDF is valid flat PDF and the options sent are valid.

ALC-CNP-001-302 Document is not a valid PDF Document. Verify that the document is a valid PDF document which can be converted to image/ps. The document must meet the following conditions:

● It is not a portable collection (PDF Package).

● It is flattened (should be non-interactive).

● It is not encrypted.

ALC-CNP-001-304 Input document is not a non-interactive PDF document.

Verify that the input document is a non-interactive PDF document.

ALC-CNP-001-305 Convert PDF does not support PDF Package (Portable Collection).

Verify that the document is not a PDF Package (Portable Collection).

ALC-CNP-001-306 An IO Exception occurred while obtaining the PDF document.

Verify that the location of PDF is valid and then retry the operation. If the problem persists, contact the system administrator.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Document Security 26

Document Security

ALC-CNP-001-307 PDF exception. Verify that the document is a valid PDF document which can be converted to image/ps. The document must meet the following conditions:

● It is not a portable collection (PDF Package).

● It is flattened (should be non-interactive).

● It is not encrypted.

ALC-CNP-001-308 Required input parameter missing. Enter all the required input parameters. Review the logs for details.

ALC-CNP-001-401 Cannot convert PDF file to Image. Verify the input PDF document format. Review the logs for details.

ALC-CNP-001-402 MultipageTiff, IncludeComments, ImageSizeWidth, ImageSizeHeight, and PageRange options are not functional in the deprecated toImage API, to use these options please use toImage2 API.

Verify that valid options are supplied. Supported image formats are:

● JPEG

● JPEG2K

● PNG

● TIFF

If you are sending MultipageTiff, IncludeComments, ImageSizeWidth, ImageSizeHeight, and PageRange options, then use the toImage2 API.



ALC-DSS-300-001 An exception occurred from an internal operation.

Review the logs for more information, and contact Adobe Technical Support.

ALC-DSS-300-002 Problem in processing the input PDF Review the logs for more information, and contact Adobe Technical Support.

ALC-DSS-300-003 Insufficient {0} permissions in the input PDF for performing the operation {1} on Signature Field {2}

Verify that the PDF contains the permissions for the operation.


ALC-DSS-300-004 PDF security handler does not allow the operation.

The PDF may be encrypted with a handler that does not provide the specific permissions for the operation.

ALC-DSS-300-005 The specified page number {0} does not exist in/can not be accessed from the input PDF (Total number of pages: {1}).

In the operation call addSignatureField, the page number should be between 1 and the total number of pages, as specified in the error message.

ALC-DSS-300-006 The input PDF is encrypted using {0} and could not be opened, hence the operation {1} can not be performed on Signature Field {2}.

Provide a document to the operation which is decrypted or if encrypted, is unlocked in a process.

ALC-DSS-300-007 Addition of Signature Fields is not supported for Dynamic XFA PDFs. If you wished to subsequently certify the signature field, you may want to try a direct certify operation with an auto generated invisible signature field name. If however you wished to create a visible signature field on this dynamic XFA or subsequently sign the created field, consider modifying the original template from which this XFA Form PDF was generated. See Signatures Service Documentation for more details.

Addition of Signature Fields is not supported for Dynamic XFA PDFs. If you wished to subsequently certify the signature field, you may want to try a direct certify operation with an auto generated invisible signature field name. If however you wished to create a visible signature field on this dynamic XFA or subsequently sign the created field, consider modifying the original template from which this XFA Form PDF was generated. See Signatures Service Documentation for more details.

ALC-DSS-300-008 The operation {0} is not supported for Shell PDFs. A Shell PDF is a special type of static or dynamic XFA Form PDF, which contains XFA streams that are not in synchronization with the rendering available in the PDF version. See Signatures Service Documentation for more details.

Provide a non-shell document to the operation.

ALC-DSS-300-009 The operation {0} is not supported for Dynamic PDFs. See Signatures Service Documentation for more details.

Provide a static document to the operation.

ALC-DSS-300-010 Could not extract the archive revocation information from the certificate.

Verify that the signer certificate has a valid extension for archiving revocation information in the PDF, while signing

ALC-DSS-300-011 Failed to convert from a PDFDocument to Document.

Verify that the document is a PDF document, and can be propagated in the workflow. If the problem persists, contact Adobe Technical Support.



ALC-DSS-300-012 Failed to read the input document. Verify the permissions of the input document and the configuration of the server with respect to document handling and disposal timeouts.

ALC-DSS-300-013 The document is Ubiquitized/Reader Extended and has Insufficient {0} permissions for performing the operation {1} on Signature Field {2}.

Provide a non Reader Extended document to the operation or a Reader Extended document carrying the necessary permission.

ALC-DSS-300-014 Certification of Dynamic Shell XFA Form PDFs is supported only for invisible signature fields. A Shell PDF is a special type of static or dynamic form that contains XFA streams that are not in synchronization with the rendering available in the PDF version.

Try one of the following actions:

● Certify this document with an existing invisible signature field.

● Do not specify any name, so that a default invisible signature field is created.

Note: An invisible certification signature created in this manner will not include a snapshot of the document. For more information, see the Signature service documentation.

ALC-DSS-300-015 Cannot determine SlotListIndex corresponding to SlotInfo {0} of Type {1}.

Ensure that the Token Name or the Slot ID given in the HSMProfile added to the truststore refers to an actual slot with a token.

ALC-DSS-300-016 Failed to create PKCS11 provider config file {0} for provider {1} due to {2}.

Ensure that the Local Temp directory has available memory. You can review the memory allocation through LiveCycle Administration Console:

1. Navigate to the LiveCycle Administration Console URL.

2. Navigate to Settings > Core System > Core Configurations.

ALC-DSS-300-017 Certification of Static Shell XFA Form PDFs is not supported. A Shell PDF is a special type of static or dynamic XFA Form PDF, which contains XFA streams that are not in synchronization with the rendering available in the PDF version. See Signatures Service Documentation for more details.

Certification of Static Shell XFA Form PDFs is not supported. A Shell PDF is a special type of static or dynamic XFA Form PDF, which contains XFA streams that are not in synchronization with the rendering available in the PDF version. See Signatures Service Documentation for more details.



ALC-DSS-300-018 Internal Error. PKCS11 Provider {0} removed bypassing the removal API. PKCS#11 JCE providers created by the Signature Service to enable signing/certifying using a private key on an HSM device are visible to all applications running in the same JVM and can be removed from outside the SecurityService which is the case here.

Ensure that some other application running in the same JVM as the LiveCycle ES server is not adding or removing JCE PKCS#11 providers for the same PKCS#11 library being used by the SignatureService as this will clash with the SignatureService's use of such providers.

ALC-DSS-300-019 Modification of Signature Fields is not supported for {0} XFA PDFs.

Modify the input PDF so that it is supported in the modifySignatureField API.

ALC-DSS-300-020 An exception occurred while certifying the form.

The form cannot be certified if any of the following are true:

● Script-based changes are saved automatically in the PDF in an unsecured fashion. In this case, modify the form in Designer ES and set the option File > Form Properties >Defaults > Scripting > Manually, to allow certification on this form.

● The form contains an empty Submit URL.

● The form uses a Forms ES state packet.


ALC-DSS-301-001 The argument {0} (of type {1}) is invalid. Provide a valid value to the operation for the type mentioned in the error message.

ALC-DSS-301-002 The value {0} for argument {1} (of type {2}) is invalid.

Provide a valid value to the operation for the type mentioned in the error message.

ALC-DSS-301-003 The sub-member {0} of the argument {1} (of type {2}) is invalid.

Provide a valid value for the member field of the argument to the operation as mentioned in the error message.

ALC-DSS-301-004 The value {0} for sub-member {1} of the argument {2} (of type {3}) is invalid.

Provide a valid value for the member field of the argument to the operation as mentioned in the error message.

ALC-DSS-301-005 The certificate encoding is null. The encoding of the Archive Revocation Information extension in the signer certificate is incorrect.

Modify the Signer Certificate so that it contains the proper extension value.



ALC-DSS-301-006 The value {0} of {1} is incompatible with the defined type {2}.For example if an HSMProfile in truststore is created with SlotListIndex which is an integer value given as "aaa".

Ensure that value {0} provided to the operation is of the desired type {2}.

ALC-DSS-301-007 The value {0} of type {1} is out of range.For example for a HSM with two slots, an HSMProfile is defined with SlotListIndex = 3.

Verify that the value {0} supplied to the operation for type {1} is within the desired range.

ALC-DSS-302-001 Could not add Signature Field {0} Verify that the input PDF is valid and has permissions to allow the addition of a signature field.

ALC-DSS-302-002 Could not remove Signature Field {0} Verify that the input PDF is valid and has permissions to allow the removal of a signature field.

ALC-DSS-302-003 Could not clear Signature Field {0} Verify that the input PDF is valid and has the permissions required for clearing (or unsigning) a signature field.

ALC-DSS-302-004 Could not get the signature field list from the input PDF file.

Verify that the input PDF is decrypted, and that it has the permissions required for retrieval of signature field lists and information.

ALC-DSS-302-005 Could not get the signed version of the document for signature field {0}

Validate the input PDF to verify that it is signed and is decrypted.

ALC-DSS-302-006 Could not get the certifying signature field from the input PDF file.

Validate the input PDF to verify that it is certified and is decrypted.

ALC-DSS-302-007 Could not get the signature data for signature field {0}

Validate the input PDF and the field to verify that it is signed and is decrypted.

ALC-DSS-302-008 Could not get the legal attestation Validate the input PDF to verify that it is certified with a legal attestation and is decrypted.

ALC-DSS-302-009 The specified Signature Field {0} does not exist

Provide a valid signature field name to the operation.

ALC-DSS-302-010 The specified field {0} already exists in the PDF. Please specify a different name.

Specify a different name for the SignatureField to be added to the document.

ALC-DSS-302-011 The specified Signature Field {0} cannot be modified.

Validate the input PDF to verify that it is decrypted (not certified), and whether it has the permissions required for signature field modification.



ALC-DSS-303-001 Could not sign Signature Field {0} Verify that the PDF is valid and has the permissions required for signing.

ALC-DSS-303-002 Could not certify Signature Field {0} Verify that the PDF is valid and has the permissions required for certification.

ALC-DSS-303-003 The specified Signature Field {0} is already signed

The operation cannot be done on a signed field. Either clear the signature or mention a different SignatureField name.

ALC-DSS-303-004 The specified Signature Field {0} can not be certified because it is not the first signed field in the document

The document input for certification already has a signed SignatureField. Either clear the previous signature or provide a different unsigned document.

ALC-DSS-303-005 The specified Signature Field {0} can not be signed/certified as it breaks existing signatures on other fields

Specify a different field to sign, or modify the PDF to have permissions for signing the field.

ALC-DSS-303-006 The credential being used for the alias {0} is not time valid.

Check the notBefore and notAfter values in the certificate associated with the private key to ensure that the private key can be used at for signing.

ALC-DSS-303-007 The PrivateKeyUsagePeriod of the credential being used for the alias {0} is expired or in the future.

Obtain a valid credential for signing.

ALC-DSS-303-008 Error while extracting PrivateKeyUsagePeriod extension from the certificate for the credential alias: {0}.

Validate the credential used for signing, and/or obtain a valid credential.

ALC-DSS-303-009 Cannot use CA certificate for signing.

A CA certificate cannot be used for signing documents.

Use a credential that does not have the CA bit set to true.

ALC-DSS-303-010 The credential being used for the alias {0} does not have digital signature or non repudiation key usage set.

Use a private key with the corresponding certificate having either no key usage extension or having one of digitalSignature or nonRepudiation key usage.

ALC-DSS-303-011 The dimensions {0} of the position rectangle for the signature field to be added are invalid. They lie completely outside the crop box of the page on which the signature field is to be added.

Provide the correct bounds of the rectangle.



ALC-DSS-303-012 No certifying signature exists in the document.

Provide a PDF document with a certifying signature field.

ALC-DSS-303-013 The signature field {0} is not signed. Provide the correct field name, that is signed.

ALC-DSS-303-014 Subject Name or Subject Alt Name extension in the signer's certificate is not present.

Provide a correct signer credential with either of these values present.

ALC-DSS-303-015 Subject Name is not present and Subject Alt Name extension in the signer's certificate is not marked critical.

Provide a correct signer credential with either of these values present in the correct form.

ALC-DSS-303-016 The specified Credential Alias {0} not found. Import a credential in TrustStore with the alias {0}.

ALC-DSS-303-017 Could not create an invisible signature field for certifying, when no name for the sigfield was specified in the API. Cannot create an on-the-fly field for signing.

Verify the validity of the PDF. If the problem persists, contact Adobe Technical Support.

ALC-DSS-303-018 Could not set the given Logo for signature field {0}. Verify that the input is valid and decrypted for opening.

Verify that the input logo PDF is valid and decrypted for opening.

ALC-DSS-303-019 Could not set the given Image for signature field {0}. Verify that the input is valid and decrypted for opening.

Verify that the input graphic PDF is valid and decrypted for opening.

ALC-DSS-303-020 The specified Credential Alias {0} cannot be used for signing/certification. It is not trusted as a "Document Signing Credential" in Trust Store.

Review the following LiveCycle Administration Console Help topic: Home > Settings > Trust Store Management > Local Credentials> {0} > Credential Trust Settings . View the "Document Signing Credential" for the alias name.

ALC-DSS-303-021 The specified Signature Field {0} can not be signed/certified as it is a read only field.

Modify the PDF to make the field read-only or specify a valid input PDF.

ALC-DSS-304-001 Could not verify Signature Field {0}. Provide the PDF to Adobe Technical Support for analysis.

ALC-DSS-304-002 The specified filter type {0} is not supported. Provide an input PDF only with the supported Filter types (Adobe.PPKLite)

ALC-DSS-304-003 The specified sub-filter type {0} is not supported.

Provide the PDF signed only with the Adobe supported sub-filters.



ALC-DSS-304-004 Error validating XML signature. Provide a valid XML signature value as the input, or provide the input to Adobe Technical Support for validation.

ALC-DSS-304-005 Signature does not contain signing time. Signature should contain signing time for proper validation. Correct the input file.

ALC-DSS-304-006 Pre-release signature is not supported. The signature is marked as PreRelease signed. Provide a non PreRelease marked signature for validation.

ALC-DSS-304-007 Signature Validation cannot occur at a time in the future. Verification Time: {0} Current Time: {1} Signing Time: {2}

Ensure that the validation time is not in the future, and that the time settings of the server are correct. Alternatively, provide a different input PDF.

ALC-DSS-304-008 The certificate for signing is an Identrust Issued certificate but does not comply with Identrust signing requirements. (May not have proper key usage).

Provide a non-identrust certificate (for the private key to be used for signing) or a valid identrust one.

ALC-DSS-305-001 Seed value constraints for the PDF were not satisfied. {0}

Provide the proper input, as specified in {0}, so that seed values in the PDF can be enforced.

ALC-DSS-305-002 Seed value specify that signature field can only be certified. Please call certify instead.

Certify the field instead of signing, as Seed Values mandate it.

ALC-DSS-305-003 SubFilter not present in seed value. SubFilter mandated in the SeedValue is not compatible with support sub-filter values.

ALC-DSS-305-004 Seed value constraints not satisfied. SeedValue constraints are not compatible with input values. Correct the input values or modify the seed value constraints.

ALC-DSS-305-005 Unsupported filter in seed value. Filter mandated in the SeedValue is not compatible with supported filter values. Correct the filter values in the Seed Values of the signature field in the PDF.

ALC-DSS-305-006 Unsupported sub filter in seed values. SubFilter mandated in the SeedValue is not compatible with supported sub-filter values. Correct the sub-filter values in the Seed Values of the signature field in the PDF.



ALC-DSS-305-007 Reason for signing doesn't exist in seed value.

Correct the reason for signing in the Input PDF Seed Values.

ALC-DSS-305-008 Subject certs in seed value do not contain signing cert.

Provide the correct credential for signing which contains the signer's certificate in the Seed Value subject certificates list.

ALC-DSS-305-009 Invalid policy bytes in seed value. Invalid Policies in the Signer Certificate or Seed Value. Correct the input signer certificate or PDF seed values.

ALC-DSS-305-010 Invalid oid in seed value. Unable to match Policy OIDs in Certificate with Seed Value. Modify the Seed Value in the PDF or provide a valid signer credential.

ALC-DSS-305-011 Exception occurred while encoding the certificate.

Unable to parse Certificates from Seed Value for SV validation. Modify the seed values with the correct certificates.

ALC-DSS-305-012 Issuer certs not validated. The issuer certificates in the Seed Value do not match with the signer's issuer certificate. Provide the correct signing credential or modify the seed value.

ALC-DSS-305-013 Filter not present in seed value SV Filter flag is set to required while there is no Filter. Correct the Seed Values in the PDF.

ALC-DSS-305-014 LegalAttestation missing in seed value. LegalAttestation constraint is required in seed value, but no Legal Attestation value exists in the Seed Value. Modify the PDF to have correct Seed Values.

ALC-DSS-305-015 Legal Attestations Seed Value enforcement failed.

Legal Attestation strings as an Input do not match with the Seed Value. Modify the input or PDF.

ALC-DSS-305-016 Subjects missing in seed value. Subject constraint is enforced in Seed Value while no Subject values are provided. Correct the Seed Values in the PDF.

ALC-DSS-305-017 Issuers missing in seed value. Issuers constraint was enforced in Seed Value while no Issuer certificates are present. Correct the Input PDF's seed values.



ALC-DSS-305-018 OID not present in the seed value. OID constraint is enforced in Seed Value while no OIDs are present. Correct the Input PDF with proper seed values.

ALC-DSS-305-019 Insufficient {0} permissions in the input PDF for performing the operation {1} on Signature Field {2}.

Unlock or decrypt the input PDF so that the permissions are present for the operation.

ALC-DSS-305-020 SubFilter present in seed value is not supported.

SubFilter is not supported as specified in Seed Value. Modify the PDF with correct SubFilter Seed Values.

ALC-DSS-305-021 No URL specified for time stamp server. Timestamp Seed Value does not contain any URL. Correct the input PDF seed values.

ALC-DSS-305-022 Unsupported Seed Value version. Seed Value version is not supported. Correct the Input PDF Seed Values.

ALC-DSS-305-023 Archiving of Revocation Info is required as per Seed Value.

Revocation information could not be archived as per constraint in Seed Value. Ensure that the signer and its chain has revocation fetching information and revocation responders are available.

ALC-DSS-305-024 Unsupported Digest Methods in seed Value. Digest Methods enforced in Seed Value are not supported. Correct the Input PDF Seed Values.

ALC-DSS-305-025 ASSP Credential URLType is unsupported, but required in Seed Value.

Remove the URLType ASSP entry from the Seed Value in the PDF.

ALC-DSS-305-026 Subject DN of signed does not match with any of the ones specified in Seed Value.

Add the Subject DN of the signer in the Seed Value, or modify the signer credential.

ALC-DSS-305-027 KeyUsage of signer does not match as per Seed Value.

Modify the Signer credential or the Seed Value to match the Key Usages.

ALC-DSS-305-028 Subfilter does not support archiving of revocation info as required by Seed Value

Mismatch between archiving and subfilter constraint. Modify the Seed Value so that they do not clash.

ALC-DSS-305-029 Can not parse the certificates in certificate seed value.

Verify that the certificates embedded in the seed value do not contain errors.

ALC-DSS-305-030 Timestamp required as per Seed Value Constraints.

Timestamp could not be retrieved as enforced in SV. Verify that the timestamp server is online and functioning.



ALC-DSS-305-031 Subfilter does not support addition of Timestamp which is required as per Seed Value.

Mismatch between subfilter and timestamp constraints in Seed Value. Modify the seed value to avoid this mismatch.

ALC-DSS-306-001 The algorithm {0} is not available. Modify the input algorithm.

ALC-DSS-306-002 There was an error computing the {0} signature.

Contact Adobe Technical Support with the signer credential and PDF.

ALC-DSS-306-003 Cannot calculate the size of the {0} signature.


ALC-DSS-306-004 Exception when initializing the PKCS1 verifier. {0}


ALC-DSS-306-005 Exception when validating PKCS1 signature. {0}


ALC-DSS-306-006 Problem encountered when DER encoding the {0} attribute.


ALC-DSS-306-007 Error retrieving {0} before signing. Contact Adobe Technical Support with the signer credential, PDF and input parameters.

ALC-DSS-306-008 Exception when validating PKCS7 signature. {0}

Contact Adobe Technical Support with the signer credential, PDF and input parameters.

ALC-DSS-306-009 Cannot get public key of the credential. Contact Adobe Technical Support with the signer credential, PDF and input parameters.

ALC-DSS-306-010 Cannot create the message digester. Contact Adobe Technical Support with the signer credential, PDF and input parameters.

ALC-DSS-306-011 Exception in creating keystore of type {0} due to {1}.

Contact Adobe Technical Support with the signer credential, PDF and input parameters.

ALC-DSS-306-012 Exception in construction of HSM Provider. The provider seems to be created from outside the application. Ensure that some other application in the same JVM is not working with the same HSM slot as the Livecycle server.

ALC-DSS-306-013 Illegal State Exception. Error in releasing lock after operation.

Internal Error. Review the logs for more detailed error messages and contact Adobe Technical Support.



ALC-DSS-306-014 Null keystore. Internal Error. Review the logs for more detailed error messages and contact Adobe Technical Support.

ALC-DSS-306-015 Internal error. Unable to generate {0} thumbprints of certificates for matching

Verify that the JVM has a JCE provider capable of calculating hash value according to the cryptographic hash function mentioned in the error message. Alternatively, use the certificate instead of certificate SHA1 in the HSM Profile.

ALC-DSS-309-001 Digest Algorithm {0} is not FIPS compliant. Provide an FIPS compliant algorithm or turn off FIPS mode.

ALC-DSS-309-002 Encryption key {0} with keylength {1} is not FIPS compliant.

Provide an FIPS compliant algorithm/keylength or turn off FIPS mode.

ALC-DSS-309-003 Encryption key could not be checked for FIPS compliance.

Provide an FIPS compliant key or turn off FIPS mode.

ALC-DSS-309-004 Signature Algorithm {0} is not FIPS compliant.

Provide an FIPS compliant algorithm or turn off FIPS mode.

ALC-DSS-311-001 Cannot recover SlotListIndex from given SlotId. The operations requires "suppressAccessChecks" Reflection in the java policy file on IBM JVM.

To create the PKCS#11 JCE provider on IBM JVM using the slot id of the slot to be used, the Livecycle code requires the permission java.lang.reflect.ReflectPermission "suppressAccessChecks". Either this be granted in the java.policy file used by the application server to set the policies or slot list index of the slot be used in the HSM Profile instead of Slot Id.

ALC-DSS-311-002 Exception thrown from PKCS11 implementation when recovering SlotListIndex from SlotInfo {0} of Type {1}.

Ensure that LiveCycle ES can connect to the HSM device through the network.

ALC-DSS-311-003 The HSM device is in an Inconsistent state w.r.t the Application Server.(Could be a result of abrupt termination of open sessions due to device restart)

Restart LiveCycle ES and try the operation again. If the problem persists, contact Adobe Technical Support.

ALC-DSS-311-004 Incorrect PIN for HSM device. Check the pin of the HSM partition (slot) and correct it in the HSM Profile.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Encryption 38

Encryption


ALC-ENC-100-002 Privatekey used for decrypting is invalid. Provide the private key corresponding to the public key(certificate) used for encryption.

ALC-ENC-100-003 Certificate format is not correct.Acceptable certificates formats are X509 and PEM certs.

Provide a valid certificate format supported by the service.

ALC-ENC-100-004 Input value to the EncryptionService is invalid.

Provide a valid value for the input mentioned in the error message

ALC-ENC-100-005 Input document to the EncryptionService is signed, hence can not be encrypted.

Provide unsigned documents for encryption or clear signature fields in the provided signed document before changing security settings of the document.

ALC-ENC-100-006 Input document is already encrypted. Provide a decrypted document for encryption or unlock the encrypted document first before trying to re-encrypt.(For the latter technique, the recipient of the encrypted document should have the permission to change the security settings as per the permissions granted at the time of initial encryption).

ALC-ENC-100-007 Certificate to be used for encryption not found in the certificate store (LDAP, truststore, or document).

If using truststore, ensure that the certificate with the input alias is present. If using LDAP, ensure that the certificates exist on the LDAP for the input LDAP URI. If you are using com.adobe.idp.Document, ensure that the document is initialized with a proper certificate file.

ALC-ENC-100-008 FIPS Compliance failure. FIPS compliance check is on and the operation is not FIPS compliant for the given inputs.

Verify that ACRO_6 compatibility is not being used for certificate encryption when FIPS compatibility is desired. Also, verify that the certificate being used for encryption is using RSA algorithm with keysize greater than or equal to 1024 bits and less than or equal to 4096 bits.

ALC-ENC-100-009 The certificate being used for document encryption is already expired at the time of the operation call as per the system time of the server machine.

Provide a valid non-expired certificate as per the notAfter field in the certificate.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Encryption 39

ALC-ENC-100-010 The certificate being used for document encryption is not yet valid at the time of the operation call as per the system time of the server machine.

Provide a certificate which is valid at the current date and time as per the notBefore field in it.

ALC-ENC-100-011 The certificate used for document encryption does not have the correct key usage. Key Usages required are keyEncipherment or dataEncipherment.

Provider a certificate with the correct key usage.

ALC-ENC-100-012 The document being decrypted is not encrypted in the corresponding fashion. For e.g if the document is certificate encrypted and the decrypting is carried out using a password, then an exception with this error code is generated.

Verify that the certificate(password) secure document is not being unlocked using a password(private key).

ALC-ENC-100-013 The credential(private key) to be used for document decrypting could not be retrieved from the truststore alias provided to the decrypting operation.

Verify that the alias provided to the Encryption service for document decrypting exists in truststore.

ALC-ENC-100-014 Internal error. Review the logs for more detailed errors, and contact Adobe Technical Support.

ALC-ENC-100-015 The document input to the encryption operation is reader extended and can not be encrypted.

Provide a non-reader extended document to the EncryptionService.

ALC-ENC-100-016 The operation invoked can not succeed due to insufficient privilege. For e.g. removal of encryption by a recipient not authorized to remove encryption as per permissions granted at the time of encryption.

Ensure that the recipient has the permission required to perform the operation on the encrypted document.

ALC-ENC-100-017 The recipient object input to the operation encryptPDFUsingCertificates has been instantiated with multiple sources of certificate retrieval. Only one is allowed, either Truststore or an LDAP server or a certificate document.

Do not set multiple sources for certificates in the Recipient object. Instead multiple Recipient objects can be used.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference File Provider 40

File Provider

LiveCycle Foundation bootstrappingLiveCycle Foundation bootstrapping is a separate function from the database initialization process performed by LiveCycle Configuration Manager.

ALC-ENC-100-018 The recipient object input to the operation encryptPDFUsingCertificates has been instantiated with no source of certificate retrieval.

Provide one source of certificates in the Recipient object. It could be either com.adobe.idp.Document or an LDAP URL or a truststore certificate alias.

ALC-ENC-100-019 ACRO_9 compatibility while document encryption uses 256 bit AES encryption, which requires JCE unlimited strength jurisdiction policy files to be installed on the JVM.

Install the JCE unlimited strength jurisdiction policy files for your JVM. The files can be downloaded from the vendor internet site.



[FileResultHandlerImpl] Failed to write---------Failure Time----Tue Mar

The following error is written to the application server log when a watched folder is set up in a location where the application server does not have proper permissions to read/write/delete from:

10:59:42,453 INFO [FileResultHandlerImpl] Failed to write---------Failure Time----Tue Mar 20 10:59:42 CST 2007 Job id id ---- null source location ---- null Reasons for failure are ----File Provider Failure null to the failure folder

Ensure that the watch folders are located in a place where the application server has read/write/delete (including create directory) permissions.

FILEPROVIDER.5023 While configuring a watched folder endpoint in Applications and Services in LiveCycle Administration Console, if the specified URL is already in use by a service, this error is logged:

FILEPROVIDER.5023: com.adobe.idp.dsc.service.file.impl.FileProviderRuntimeException: This folder <URL> is already in use by <ServiceA>;

Use a different URL, or remove the existing watched folder endpoint in that URL for the service.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Foundation bootstrapping 41


ALC-TTN-001-000 An exception occurred in the server-side bootstrap code: [{0}]

Review the application server logs for errors. If necessary, take corrective action and retry the database initialization task in LiveCycle Configuration Manager.

ALC-TTN-002-000 JDBC data source look-up failed for resource reference [{0}]. LiveCycle ES data source may not exist or is misconfigured.

Review the application server configuration. See Preparing to Install LiveCycle ES Single Node or Preparing to Install LiveCycle ES Clustering or the Installing and Deploying LiveCycle ES document for your application server.

ALC-TTN-003-000 Table [{0}] could not be created. Verify that the required database permissions are available to LiveCycle ES. The auto-bootstrap code requires CREATE TABLE permissions. Manual bootstrapping through LiveCycle Configuration Manager does not have this requirement.

ALC-TTN-004-000 Auto-bootstrap process has timed out after [{0}] minutes.

Review the application server logs to see what might have caused the timeout. For example: server not responding or cluster members not talking to each other. Restart the LiveCycle ES application to retry the operation. If the error persists, contact Adobe Technical Support.

ALC-TTN-005-000 Auto-bootstrap process failed on another server instance.

Review the application server logs of each cluster member to find the cause of the failure. Restart the LiveCycle ES application to retry the operation. If the error persists, contact Adobe Technical Support.

ALC-TTN-006-000 A SQLException was detected: [{0}] Review the server logs for errors, apply corrections if possible, and try again.

ALC-TTN-007-000 No bootstrapper name was supplied for the manual bootstrap operation.

Issue a bootstrap command with a valid bootstrapper name. If the error persists, contact Adobe Technical Support.

ALC-TTN-008-000 An unregistered bootstrapper name [{0}] was supplied for manual bootstrap.

Issue a bootstrap command with a valid bootstrapper name. If the error persists, contact Adobe Technical Support.






ALC-TTN-009-000 A RemoteException was detected: [{0}]

Review the application server logs for specific errors. If necessary, take corrective action and retry the database initialization task in LiveCycle Configuration Manager.

ALC-TTN-010-000 A bootstrapper instance for key [{0}] was not found in the cache of bootstrappers.

Internal error. Contact Adobe Technical Support.

ALC-TTN-011-000 Bootstrapping failed for platform component [{0}]. The wrapped exception message reads: \n{1}

Review the server logs for specific errors. If necessary, take corrective action and retry the database initialization task in LiveCycle Configuration Manager.

ALC-TTN-012-000 Failed to look up UserTransaction object; caused by [{0}]


ALC-TTN-013-000 An exception occurred while starting, committing, or rolling back a transaction; caused by [{0}].

There may be a problem with the application server configuration, or the bootstrap operation might have taken too long to complete, causing the transaction to time out.

Review the application server logs for specific errors. Take the corresponding corrective action if possible, then retry he database initialization task in LiveCycle Configuration Manager. If the problem persists, contact Adobe Technical Support.

ALC-TTN-014-000 An exception occurred while parsing the version-info.mf manifest; caused by [{0}]

Contact Adobe Technical Support.

ALC-TTN-015-000 Semaphore acquisition deemed failed because [{0}] rows were inserted into the boot table.


ALC-TTN-015-000 Semaphore acquisition deemed failed because [{0}] rows were inserted into the boot table.


ALC-TTN-016-000 Failed to determine database type; manual bootstrap required; caused by [{0}]




ALC-TTN-017-000 Failed to create new InitialContext; caused by [{0}].

There may be a problem with the application server configuration.

Review the application server logs for specific errors. Take the corresponding corrective action if possible, and then retry the database initialization task in LiveCycle Configuration Manager. If the problem persists, contact Adobe Technical Support.

ALC-TTN-018-000 Internal error: The polling query returned a bootstrap message [{0}] that was unexpected.


ALC-TTN-019-000 Failed to record auto-bootstrap result; caused by [{0}]


ALC-TTN-020-000 Failed to determine the current builds bootstrap status: [{0}]


ALC-TTN-021-000 An exception occurred during the poll operation; caused by [{0}]


ALC-TTN-022-000 Invalid task [{0}]. Get a newer LiveCycle Configuration Manager.

ALC-TTN-023-000 Invalid step [{0}] for task [{1}]. Review the application server data source configuration and data source database server. If the problem persists, contact Adobe Technical Support.

ALC-TTN-024-000 Failed to connect to database; caused by [{0}]

Review the application server data source configuration and the database server.

If the error is related to permissions, verify the credentials of the data source and that the specified database user has the necessary database roles or permissions.

ALC-TTN-025-000 Look-up failed for JNDI name [{0}]; caused by [{1}]

A likely cause of this error is that a particular bootstrapper's backing implementation is not deployed, meaning the implementation is missing from the LiveCycle EAR. In this scenario, it is likely that the EAR file contents have been manually tweaked, instead of using LiveCycle Configuration Manager.

Review the application server logs for specific errors. If the problem persists, contact Adobe Technical Support.



ALC-TTN-026-000 Narrow operation failed on object retrieved using JNDI name [{0}]; caused by [{1}]


ALC-TTN-027-000 Failed to create an EJB instance from an EJB home; caused by [{0}]


ALC-TTN-100-000 An exception occurred in the client-side bootstrap code: [{0}]

Internal error. Review the application server logs for specific errors. If the problem persists, contact Adobe Technical Support.

ALC-TTN-101-000 Failed to connect to server. Host [{0}] not found.

Review your host name input and verify that the host name can be resolved (pinged) from the client.

ALC-TTN-102-000 Bootstrap URL is invalid: [{0}] Review your host name and port input.

ALC-TTN-103-000 Bootstrapping request failed on server. Message from server: \n\n{0}\n\n.

Review the application server log for the cause of the error. The LiveCycle Administration Console log may not contain the complete cause exception's trace.

ALC-TTN-104-000 Failed to connect to bootstrap servlet; the requested URL was not found on the server.

Ensure that LiveCycle ES is deployed.

ALC-TTN-105-000 Failed to connect to bootstrap servlet: port [{0}] may be invalid.

Review the port number. Ensure that the application server is running.

ALC-TTN-106-000 A problem with the request has occurred: [{0} {1}]

This error indicates that a 400-class HTTP error code was returned by the application server or a LiveCycle ES server bootstrapper component.

The error message should contain the details to enable more specific diagnosis. If the problem persists, contact Adobe Technical Support.

ALC-TTN-107-000 Failed to establish a valid secure connection to server. Port [{0}] may not be SSL-enabled or certificates may not be valid.

If an HTTPS connection is required, review the application server’s HTTPS/SSL configuration. Otherwise, deselect Use the secure connection (HTTPS) and try again.

ALC-TTN-108-000 SSL error during communication with server: [{0}]

Review the SSL configuration. For information about configuring SSL, see Administering LiveCycle ES.



Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference FDI 45

FDI

ALC-TTN-109-000 Failed to establish a valid connection to server: [{0}]

LiveCycle Configuration Manager is having difficulty establishing a TCP connection to the application server.

Review the LiveCycle Configuration Manager log for details.

ALC-TTN-110-000 The server returned a response indicating an internal server error.


ALC-TTN-111-000 Unexpected URLConnection subtype instance: [{0}]

This is a client-side internal error.

Review the LiveCycle Configuration Manager log file for details, take corrective action if possible, and then run LiveCycle Configuration Manager again. If corrective action is not possible based on the log file message, contact Adobe Technical Support (and include the LiveCycle Configuration Manager log file).

ALC-TTN-112-000 The Bootstrap servlet returned 200, but the first line of the response body did not contain an expected status string. Expected values are [{0}]. The received value was [{1}].

Internal error. Review the application server logs for specific errors. If the problem persists, contact Adobe Technical Support.

ALC-TTN-116-000 Failed to retrieve bootstrapping tasks from the server: [{0}]

Your version of LiveCycle Configuration Manager is recent, but the server you are calling is old and does not support bootstrap task retrieval. If the problem persists, contact Adobe Technical Support.



ALC-FDI-001-301 Input document is not a valid PDF file. Ensure that input document is a valid PDF file.

ALC-FDI-001-302 Input document is not a PDF form. Ensure that input document is a PDF form.

ALC-FDI-001-303 Input data is either null or in a format that is not supported.

Ensure that input data is not null and is in the correct format.

ALC-FDI-001-304 Input data is not in XDP format. Ensure that input data is in XDP format.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference FDI 46

ALC-FDI-001-305 Failed to merge data with PDF form. Contact the system administrator.

ALC-FDI-001-306 Failed to merge the data descriptions. Contact the system administrator.

ALC-FDI-001-307 Processing importData operation on source document.

No action is required.

ALC-FDI-001-308 Processing exportData operation on source document.


ALC-FDI-001-309 Failed to import data to the input PDF document as it has a certifying signature that does not permit any changes.

Form changes are not allowed in the certified PDF form. Please use a different form.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Job Manager 47

Job Manager

Repository


8193 This excerpt indicates what you may see in the error log:

JobManager:getServiceClientFactory():exception:| [com.adobe.idp.um.api.UMLocalUtils] errorCode:8193 errorCodeHEX:0x2001 message:Exception in getting SystemContext at com.adobe.idp.um.api.UMLocalUtils.setSystemContext(UMLocalUtils.java:108) at com.adobe.idp.um.api.UMLocalUtils.getSystemContext(UMLocalUtils.java:66) at com.adobe.idp.jobmanager.ejb.JobManagerBean.getServiceClientFactory(JobManagerBean.java:1245) at com.adobe.idp.jobmanager.ejb.JobManagerBean.doOnMessage(JobManagerBean.java:866) at com.adobe.idp.jobmanager.ejb.JobManagerBean.onMessage(JobManagerBean.java:817)[Remainder of stack trace deleted - very lengthy]

No action is required. When the application server is shut down either intentionally or unintentionally and jobs are currently being processed by Job Manager, the server attempts to reprocess them on startup. If Job Manager starts before User Manager, these exceptions may be thrown as the server attempts to reprocess the job. However, Job Manager tries again after 60 seconds and, assuming User Manager has started in that time, processes the messages appropriately.

SEVERE: JobManagerBean:onMessage:unable to acquire a ServiceClientFactory and/or contact the ServiceRegistry --

JobManager attempts to recover jobs on startup of the application server that were in process during an unexpected shutdown. When this occurs, this message may appear because all the necessary components to complete the job did not properly start.

No action is required. The jobs will try again in 60 seconds, at which point the necessary components should have begun and the job will finish as usual.


ALC-REP-001-xxx Parameter [paramName] cannot be null. Ensure the parameter is not null and retry the call.

ALC-REP-002-xxx Array parameter [paramName] has a null element. Array elements of parameter [paramName] cannot be null.

Ensure that no null elements exist in the array and retry the call.

ALC-REP-010-xxx Resource [resourceURI] is a category and may not be categorized. Categories may not be categorized in other categories.

New categories are created by calling writeResource (a category).

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Repository 48

ALC-REP-011-xxx Resource [resourceURI] is not a category, and it may not categorize other resources.

Ensure you are using a category to categorize a resource.

ALC-REP-012-xxx Value [value] is reserved for future use for property [propertyName].

This value is within the reserved values list for this attribute.

Consult the list and resubmit the request with a non-reserved value. (See ALC-REP-030-xxx.)

ALC-REP-013-xxx Value [value] is not valid for parameter [paramName].

A method received a parameter value that did not meet the preconditions defined in the API documentation.

ALC-REP-014-xxx A resource named [name] is already categorized in this category.

The target category contains a resource with the same name as the resource submitted for categorization. Rename the resource and retry the operation.

ALC-REP-015-xxx A resource exists at URI [resourceURI]. Another resource is using the target URI of a move or copy operation. Use a different name or remove the resource at the target URI.

ALC-REP-016-xxx Resource [resourceURI] is locked by user [ownerUserId].

The resource is exclusively locked by another user. The other user must unlock the resource before this operation will succeed.

ALC-REP-017-xxx No lock token submitted for locked resource [resourceURI].

The resource is locked by the current user, but no lock tokens matching the lock were submitted with the call. Submit the correct lock token and retry the call.

ALC-REP-018-xxx Resource [resourceURI] does not exist, or you do not have sufficient rights to access it.

The requested resource could not be retrieved, either because [resourceURI] does not exist or the user requesting the resource does not have the sufficient rights to access the resource.

ALC-REP-019-xxx Property [propertyName] is immutable. The attribute named [attributeName] cannot be modified by clients.

ALC-REP-020-xxx Failed to increment major version because version [majorVersion.0] already exists.

Failed to update the resource version identified by the ID-based identifier passed to updateResource(…). Use a different resource version or do not attempt to update the major version.



ALC-REP-021-xxx Failed to increment minor version because version [majorVersion.minorVersion] already exists.

Failed to update the resource version identified by the ID-based identifier passed to updateResource(…). Use a different resource version or try update the major version.

ALC-REP-022-xxx Failed to update resource because a version already exists with ownerVersion [ownerVersion].

A version of the same logical resource already has the ownerVersion attribute set to the value of the ownerVersion attribute in the object submitted for update. Change the ownerVersion attribute and resubmit the resource for update.

ALC-REP-023-xxx Resource [resourceURI] is not an application instance.

The method expected the [applicationURI] parameter to resolve to an application. Ensure that the submitted URI resolves to an application, and retry the operation.

ALC-REP-024-xxx Relationships of type Relation.TYPE_MEMBER_OF must be manipulated through calls to removeResource(...) and writeResource(...).

Relation.TYPE_MEMBER_OF is a relationship type managed by the repository and cannot be manipulated directly by clients (only indirectly through writeResource, moveResource, and removeResource). The exception is thrown when Relation.TYPE_MEMBER_OF is passed to a relationship manipulation API (createRelationship, selectVersion, or removeRelationship). Use one of the following APIs instead:

● writeResource

● updateResource

● moveResource

● copyResource

● removeResource



ALC-REP-025-xxx Relationships of type Relation.TYPE_CATEGORIZED_BY must be manipulated through calls to categorize(...) and uncategorize(...).

Relation.TYPE_MEMBER_OF is a relationship type managed by the repository and cannot be manipulated directly by clients (only indirectly through writeResource, moveResource, and removeResource). This exception is thrown when Relation.TYPE_MEMBER_OF is passed to a relationship manipulation API (createRelationship, selectVersion, or removeRelationship). Use one of the following APIs instead:

● writeResource

● updateResource

● moveResource

● copyResourcer

● removeResource

ALC-REP-026-xxx A category may be written only to the /Categories resource collection or one of its child resource collections. The supplied path was [resourcePath].

Change the path to a /Categories resource collection or one of its child resource collections.

ALC-REP-027-xxx A non-category may not be written to the /Categories resource collection or any of its child resource collections. The supplied path was [resourcePath].

Change the path so that it does not point to the /Categories resource collection or any of its child resource collections.

ALC-REP-028-xxx Invalid major.minor version combination: [majorVersion.minorVersion].

A new resource must respect one of the following rules:

● Major and minor version attributes are unspecified.

● Major version must be zero and minor version must be greater than zero.

● Major version must be greater than zero and minor version must be greater or equal to zero.



ALC-REP-029-xxx The parentResourcePath parameter must be a path-based identifier. The supplied value [value] is invalid.

When writing a new resource, a path-based identifier must be specified to identify the parent ResourceCollection. Because ResourceCollections (Libraries, Applications) may have more than one path, path-based identifiers are required to select the correct path. (LiveCycle ES does not know which path to choose if two or more paths for a ResourceCollection exist.)

ALC-REP-030-xxx Values [low-hi] are reserved for future use for property [propertyName]. The supplied value [value] falls in this range.

This value is within the reserved values list for this attribute. Consult the list and resubmit the request with a non-reserved value. (See ALC-REP-012-xxx.)

ALC-REP-031-xxx Invalid lock scope value [value]. Lock scope may only be Lock.SCOPE_EXCLUSIVE or Lock.SCOPE_SHARED.

A client supplied a lock scope value that is invalid.

ALC-REP-032-xxx Invalid lock depth value [value]. Lock depth may only be Lock.DEPTH_ZERO.

A client supplied a lock depth value that is invalid.

ALC-REP-033-xxx Failed to locate a lock for resource [resourceURI]. You do not own the lock, did not supply the proper lock token, or are not unlocking the top level resource for the lock.

Obtain the lock for [resourceUri] or unlock its parent resource collection.

ALC-REP-034-xxx Resource object [resourceURI] is not an instance of BOIObject.


ALC-REP-035-xxx Initialization failed due to [errorMessage] Retry the initialization with all required data.

ALC-REP-036-xxx The object status cannot be changed to updated when only one version of the resource exists.

Call updateResource to update the resource, or use a custom status.

ALC-REP-037-xxx The object status cannot be changed to updated when only one version of the resource exist.

Change the status to latest, or use a custom status.

ALC-REP-038-xxx The object status cannot be changed to latest when the resource is not the most recent version.

Call updateResource to update the resource to latest or use a custom status.

ALC-REP-039-xxx The object status cannot be changed to latest when the resource is not the most recent version.

Call updateResource to update the resource and make it the latest version.



ALC-REP-040-xxx Either a relation with source URI [sourceResourceURI], target URI [targetResourceURI], and a type of [relationType] does not exist, or you do not have sufficient rights to access it.

Verify that the values are correct and that you have access rights to the relation. If the problem persists, contact Adobe Technical Support.

ALC-REP-041-xxx The [path] is not a category path. Category paths must start with /Categories

Modify the path to start with /Categories.

ALC-REP-042-xxx Resource [resourceURI] is share-locked by user [ownerUserId].


ALC-REP-043-xxx Resource [resourceURI] is exclusive-locked by user [ownerUserId].


ALC-REP-044-xxx Two versions of the same resource cannot be made to relate in this manner.


ALC-REP-045-xxx Resource [resourcePath] cannot be moved into the category hierarchy.


ALC-REP-046-xxx Resource [resourcePath] cannot be moved out of the category hierarchy.


ALC-REP-047-xxx The supplied resource name contains the following invalid characters: [characterList]

Verify that the name does not contain the characters reported in the error message. If the problem persists, contact Adobe Technical Support.

ALC-REP-048-xxx Property [propertyName] in namespace [propertyNamespace] is immutable.

You cannot update immutable properties.

ALC-REP-049-xxx Property [propertyName] in namespace [propertyNamespace] cannot be made null or removed.

Set [propertyName] to a non-null value.

ALC-REP-050-xxx Resource URI [resourceURI] must be a path. Ensure that the value of [resouceURI] is a valid path.

ALC-REP-051-xxx [resourceURI] is a system object and cannot be deleted.

Do not try to delete system paths.



ALC-REP-052-xxx Property [propertyName] cannot be added to reserved namespace [propertyNamespace].

You cannot add the property to the reserved namespace.

ALC-REP-053-xxx The path [resourcePath] does not identify a resource or resource collection.


ALC-REP-054-xxx Invalid depth value [value]. Depth can only be DEPTH_ZERO.

Use a valid lock depth.

ALC-REP-055-xxx The destination [resourceURI] is not a resource collection. Resources can only be moved or copied into resource collections.

Verify the [resourceURI] destination paths refer to a resource collection.

ALC-REP-056-xxx The [resourceURI] is a system object and cannot be updated.

You cannot update system objects.

ALC-REP-057-xxx A type mismatch exists: A resource must be updated with a resource of the same type.

Update the resource with resource of the same object type.

ALC-REP-058-xxx User Manager permissions not loaded [errorMessage]. This error is thrown when a User Manager ResourceType does not contain the expected number of permissions. This indicates a major system malfunction that cannot be recovered.

This indicates a major system malfunction that cannot be recovered. Contact Adobe Technical Support.

ALC-REP-059-xxx User access to resource [resourceURI] not allowed for permission request [permissionType] on resource [resourceURI].

An operation was requested on a resource to which the current user does not have sufficient privileges.

Grant the user sufficient privileges for the operation, or switch to an operation that the user does have sufficient privileges to request.

ALC-REP-060-xxx The format of the value of URL parameter [URL] is incorrect. The supplied value is [suppliedURL]; expected [major.minor].

Use a version string in the correct format: [major.minor].

ALC-REP-061-xxx Context deserialization failed and returned a null user context.


ALC-REP-062-xxx The specified source URI is a system resource collection.

You cannot move or copy system paths.

ALC-REP-063-xxx The specified resource ID [resourceID] is not a version of the resource selected for update.

Use a version of the resource that you wish to update. It cannot be a different logical resource.

ALC-REP-100-xxx Caught POFException due to [errorMessage].

Review the wrapped exception for details.

ALC-REP-101-xxx Caught UMException due to [errorMessage].




ALC-REP-102-xxx Caught RemoteException due to [errorMessage].


ALC-REP-103-xxx Caught Exception due to [errorMessage]. Review the wrapped exception for details.

ALC-REP-104-xxx Caught ResourceManagerException due to [errorMessage].


ALC-REP-105-xxx Caught IOException due to [errorMessage].


ALC-REP-106-xxx Caught DSCException due to [errorMessage].


ALC-REP-107-xxx Caught CacheException due to [errorMessage].


ALC-REP-200-xxx No metadata extraction capabilities available for [mimeType].


ALC-REP-201-xxx Failed to instantiate metadata extractor for [mimeType].

Verify that the [mimeType] is correct and that it is supported.

ALC-REP-202-xxx Failed to extract metadata. Verify that the metadata in the resource is valid and matches the MIME type.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Trust Store 55

Trust Store

ALC-REP-203-xxx Failed to parse XMP in data stream. Verify that the metadata in the resource is valid and matches the MIME type.

The type XappstoreUrlDataProviderBean is deprecated

Two warnings are logged in the application server log:

A warning is issued from the EJBDeploy program: ejbModule/com/adobe/url/EJSLocalStatelessXappstoreUrlDataProvider_b1f718de.java(30): The type XappstoreUrlDataProviderBean is deprecated [severity 1]

ejbModule/com/adobe/url/EJSLocalStatelessXappstoreUrlDataProvider_b1f718de.java(31): The method getInputStream(String, byte[], StringBuffer) from the type XappstoreUrlDataProviderBean is deprecated [severity 1]

These warnings indicate that the XappstoreUrlDataProviderBean class and the getInputStream(String, byte[], StringBuffer) method are deprecated.

You can ignore these warnings.



com.ibm.db2.jcc.b.SqlException (only WAS/ DB2/ AIX, Linux)

The SQL exception is caused when the value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use.

The first Sign() process on WebSphere with DB2 on AIX and Linux fails with this message:

The XAResource for a transaction participant could not be recreated and transaction recovery may not be able to complete properly.

The Sign() operation will pass when it is run the second time and subsequent to the second run.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference User Manager 56

User Manager


0x4001 (16385) Generally not used. Review stack trace in logs.

0x4002 (16386) Authenticate call failure over component. This error is also thrown if context is not authorized with permission (historical context usage).

Verify the authorization status.

0x4003 (16387) No such domain exists (historical context usage).

Verify that such a domain exists (historical context usage).

0x4004 (16388) A duplicate domain is being created. Change domain specifics like domainname or domaincommonname.

0x4005 (16389) Non-existent domain. Ensure that the domain specified exists.

0x4006 (16390) Thrown if null details are passed for the domain being created (historical usage) or isUserInRole (roleID) is called without a valid user context.

Review the logs and database.

0x4007 (16391) Not raised. Role reassignment is plain and does not raise exceptions.


0x4008 (16392) Raised during bootstrap operations. No action is required.

0x4009 (16393) Unsupported API. This exception is no longer thrown.


0x400A (16394) Invalid reliant application passed as arguments.

Review the arguments.

0x400B (16395) Relapp with the name preexists. Change the name of relapp.

0x400C (16396) Null relapp name was passed. Pass in a non null name

0x400D (16397) Check for the resourcetype name argument


0x400E (16398) Resourcetype with same attribute preexists.

Review preexisting resource type.

0x400F (16399) Resourcetype with different attribute preexists.

Check preexisting resource type

0x4010 (16400) Null permission arguments have been passed

Check whether Null permission arguments have been passed.

0x4011 (16401) Created permission preexists. Check whether created permission preexists.

0x4013 (16402) Check role name and its mutable status.


0x4014 (16403) Check role name and its mutable status.

0x4016 (16404) Determine whether the argument/details that were passed in are null

0x4017 (16405) The role being deleted is mutable in nature.


0x4019 (16406) Check for existence of role in database.

0x401B (16407) Invalid permission argument or invalid permissionSearchFilter.

Check the arguments.

0x401C (16408) Determine whether the values of arguments passed are null.

0x401D (16409) Each resourcetype has an associated group for default ACL creation. This group could not be created.

Check logs and database.

0x401E (16410) An attempt is being made to remove non-existent permission from role definition.

Check arguments.

0x401F (16411) The role being modified is mutable in nature.

Determine whether the role being modified is mutable.

0x4020 (16412) The role may be non-existent. Verify the role name in the database.

0x4021 (16413) Role assignment does not exist. No longer used.

0x4022 (16414) Local domain check failed. The domain is an enterprise domain.

Verify that the domain is an enterprise domain.

0x4023 (16415) Raised if issuerCN preexists in preferences.

Review the issuerCN.

0x4024 (16416) Authentication failure. The token may have expired.


0x4025 (16417) Used by ServiceClient for invoking component operations. Thrown by ExpiryHandler.

Review the logs and database.

0x4026 (16418) Not authorized. No longer used.

0x4027 (16419) Certification authentication failure. Review the credentials.

0x4028 (16420) The principal with said arguments does not exist.


0x4029 (16421) This error is managed during the database initialization phase.




0x4030 (16422) Failed to split Kerberos result into user/domain.


0x4031 (16423) At least one user should exist in each domain identified in listofdomains during a certificate authenticate call. If certificate mapping points to the second domain, authentication fails with this error message:

None of the Auth Provider could authenticate the user. Authentication Failed and error code: 16423" with base error message being "Exception: Could not find appropriate certificate mapping for Issuer CN

Determine whether the role BASIC_ROLE_ADMINISTRATOR is unassigned. Ensure that at least one user exists for each domain identified in listofdomains or remove the domain from listofdomains.

0x4032 (16424) Unacceptable authentication Token type.


0x2001 (8193) The Job class must implement the Job interface.

This error is seen on JBoss startup when the quartz.jar version has not been updated correctly. Please see the Installing and Deploying LiveCycle ES for Jboss or Upgrading to LiveCycle ES for JBoss for information on ensuring that "quartz.jar" and "commons-collections.jar" have been updated properly in your JBoss environment.

0X4033 The assertion renewal count exceeded the configured limit.

Create a new context for use with the assertion id.

0X4034 The assertion id passed is invalid or the assertion corresponding to that id has expired.

Ensure that the assertion id is valid and has not expired, or pass another valid assertion id for the context.






Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference XMLForm service 59

XMLForm service

LiveCycle Barcoded Forms ES


$$$/com/adobe/xmlformservice/msg.xci.empty.err=could not load XCI file

While deploying the latest qualified XMLForm EAR, you may notice a warning message in WebLogic Administration Console. The message that may appear is as follows: Warning com.adobe.document.XMLFormService> <000000> <$$$/com/adobe/xmlformservice/msg.xci.empty.err=could not load XCI file /opt/BEA9.2/user_projects/domains/Adobe_LiveCycleServer/XMLFormService/default.xci file does not exist or is empty&#8221

This message is only issued the first time you start the application server. Thereafter, the message does not occur. The default.xci file is created the first time the XMLForm service is started.


ALC-BCF-002-001 No image iterator for the input document. The input image format is not supported for decoding.

Provide an image in TIFF format.

ALC-BCF-002-003 IOException: Unable to read the input document to be decoded.

Verify that the input is a valid document.

ALC-BCF-002-004 PDFException: The barcode images could not be extracted from the input PDF.

Verify that the input document is not a dynamic PDF.

ALC-BCF-002-006 Exception in conversion to serializable DOM. Contact Adobe Technical Support.

ALC-BCF-005-006 Error in tokenizer. There is a problem in the data decoded from the barcode.

Verify that the value encoded in the barcode is properly delimited using different field and line delimiters. Ensure that field value does not contain the delimiters.

ALC-BCF-010-001 There is a problem in the data decoded from the barcode. The data does not contain a tokenizable pair for given delimiters.

Verify that the value encoded in the barcode is properly delimited using different field and line delimiters.

ALC-BCF-003-004 Unable to decompress the data from barcode due to a flate decompressor error.

Ensure that the data is compressed using flate compression.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Content Services ES 60

LiveCycle Content Services ES


ALC-CSV-030-000 {0} A generic Content Services exception.

ALC-CSV-030-001 Authentication Failed for User: {0}. Verify the user/password combination.

ALC-CSV-030-002 Unable to locate: {0} in repository. Verify the path/id of the document.

ALC-CSV-030-003 Repository Fault. There was a problem accessing the repository. Review the logs for associated errors.

ALC-CSV-030-004 Invalid Update Version Type attribute {0}.

Please check the value of Update Version Type enumeration constant you are using

ALC-CSV-030-005 Unable to retrieve content from {0}. There was a problem retrieving the content from the Content Services ES repository. Review the logs for associated errors.

ALC-CSV-030-006 Invalid MIME type {0}. Verify the MIME type you are using.

ALC-CSV-030-007 Unable to invoke webscript URL {0}. The webscript URL is invalid. Verify your system configuration.

ALC-CSV-030-008 Not a folder: {0}. Verify the given path/id.

ALC-CSV-030-009 Node: {0} already exists in repository. Verify that the path/id exists.

ALC-CSV-030-010 Access denied for User: {0}. User does not have permissions to perform this operation. Switch to a different user, or change the permissions for the specified user.

ALC-CSV-030-011 Failed to issue a request to Content Services ES.

It is likely that the Content Services ES webscripts are not configured for the correct port. Update the Content Services ES HttpPort property using LiveCycle Administration Console.

ALC-CSV-030-012 The value for QName cannot be null or empty.


ALC-CSV-030-013 The format of date string :{0} is incorrect. Ensure that the date string conforms to the ISO 8601 standard "yyyy-MM-dd'T'HH:mm:ss'Z'".

ALC-CSV-030-014 The version label {0} is invalid for the node. Address the issue identified in the Cause section of the log message.


ALC-CSV-030-015 The node {0} is not versioned. Address the issue identified in the Cause section of the log message.

ALC-CSV-030-100 No Space specified while invoking {0}. You have not specified a space while performing the given operation. Verify the parameters.

ALC-CSV-030-101 No Store specified while invoking {0}. You have not specified a store while performing the given operation. Verify the parameters.

ALC-CSV-030-102 No Node name specified while invoking {0}. You have not specified a node name while performing the given operation. Verify the parameters.

ALC-CSV-030-103 No Node type specified while invoking {0}. You have not specified a node type while performing the given operation. Verify the parameters.

ALC-CSV-030-104 No Node encoding specified while invoking {0}.

You have not specified a node encoding while performing the given operation. Verify the parameters.

ALC-CSV-030-105 No Content(InputStream) present while invoking {0}.

You have not passed the content stream while performing the given operation. Verify the parameters.

ALC-CSV-030-106 No Content type specified while invoking {0}.

You have not specified a content type while performing the given operation. Verify the parameters.

ALC-CSV-030-107 No Node ID or Path specified while invoking {0}.

You have not specified a node path/id while performing the given operation. Verify the parameters.

ALC-CSV-030-108 No Relationship type specified while invoking {0}.

You have not specified a relation type while performing the given operation. Verify the parameters.

ALC-CSV-030-109 No Child Node ID or Path specified while invoking {0}.

You have not specified a child node id/path while performing the given operation. Verify the parameters.

ALC-CSV-030-110 No Parent Node ID or Path specified while invoking {0}.

You have not specified a parent node id/path while performing the given operation. Verify the parameters.

ALC-CSV-030-111 No Source Node ID or Path specified while invoking {0}.

You have not specified a source node id/path while performing the given operation. Verify the parameters.



ALC-CSV-030-112 No Target Node ID or Path specified while invoking {0}.

You have not specified a target node id/path while performing the given operation. Verify the parameters.

ALC-CSV-030-113 No Template/Source Folder specified. You have not specified a Template/Source folder while performing the given operation. Verify the parameters.

ALC-CSV-030-211 There is no LiveCycle ES service available for the conversion of {0}.

The LiveCycle ES service required to perform the conversion is not available. Verify that the service is active and has been deployed on the server. If the problem persists, contact your system administrator.

ALC-CSV-030-212 No data could be retrieved from the provided XML files.

The LiveCycle ES transformation module is corrupted. Ensure that Content Services ES is deployed properly.

ALC-CSV-030-213 Received no response from LiveCycle ES while invoking {0}.

There was problem invoking the given LiveCycle ES service component. Please ensure that component service is deployed and active.

ALC-CSV-030-214 Map does not contain any XML data. The LiveCycle ES transformation mapping XML is empty. Verify that Content Services ES is deployed properly.

ALC-CSV-030-215 Desired conversion could not be performed. There was problem while doing the conversion. Review the logs for more information.

ALC-CSV-030-216 Transformation to {0} is not supported. The transformation to given target format is not supported by Content Services ES.

ALC-CSV-030-217 List of input streams received after conversion is empty. It is likely that there was a problem retrieving the result of the transformation.

Review the logs for any associated errors.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Forms ES 63

LiveCycle Forms ES


ALC-FRM-001-001 The parameter is missing. Specify the parameter

ALC-FRM-001-002 The transformation ID cannot be determined based on the provided inputs. The useragent string may be the cause; it may not be recognized/supported.


ALC-FRM-001-003 The format of the useragent string is invalid.

Verify the useragent value.

ALC-FRM-001-004 Failed to look up the XMLForm service or the Font Manager service.

Verify that these services have started properly.

ALC-FRM-001-005 FDF or XFDF (alone) has been passed in with incompatible clientCache option pass.

Verify that the data is in the correct format.

ALC-FRM-001-006 Failed to load template from the specified URI.

Verify that contentRootURI and formQuery API parameters are correct.

ALC-FRM-001-008 An attempt was made to translate the layout of a PDF or Image.

Review the LiveCycle ES logs for more details.

ALC-FRM-001-010 Format of XDP data is invalid. Verify the format of data.

ALC-FRM-001-011 The options format does not comply with Forms ES expected format.

Update the option.

ALC-FRM-001-012 Invalid value specified for option. Verify the option value.

ALC-FRM-001-013 XMLForm failed to render the form. Verify the format of template.

ALC-FRM-001-014 Forms ES invoked XMLForm but received a failure in response.

Review the log for more details.

ALC-FRM-001-015 Content type of submitted data is not supported.

Verify that data is getting submitted in correct format.

ALC-FRM-001-016 A parse error has been encountered while processing internal XML data. Invalid data may have been passed to the API.

Verify any XML data passed in is well-formed.

ALC-FRM-001-017 Forms ES failed to render the form. Review the log for more details.

ALC-FRM-001-018 The specified file is not available. Update the file path or verify the API parameter values such as the ContentRootURI value.

ALC-FRM-001-019 An invalid URL is specified. Update the URL and verify the API parameter values, such as BaseURL.


ALC-FRM-001-020 The data does not match the data type or the data is corrupted.

Verify and validate the data.

ALC-FRM-001-021 An invalid URI is specified. Update the URI.

ALC-FRM-001-022 An unexpected exception has occurred. Contact the system administrator.

ALC-FRM-001-023 The specified transformation is not supported.

Verify the value of the API parameterformPreference

ALC-FRM-001-024 The environment buffer passed to the API is not correct.

Verify that the environment buffer value is not null.

ALC-FRM-001-025 The request buffer passed to the API is not correct.

Verify that the request buffer value is not null.

ALC-FRM-001-026 The cache directory configuration is not correct.

The cache directory is based on data specified by the Forms ES configuration. Verify the cache configuration.

ALC-FRM-001-027 Failed to lookup the Forms ES service configuration EJB.

The Forms ES service configuration EJB is deployed as part of the LiveCycle ES archive. Verify that all components of the archive deploy successfully.

ALC-FRM-001-028 Caching has been disabled because of unexpected error.

Contact the system administrator.

ALC-FRM-001-029 An unexpected problem has happened Review the log files and contact the system administrator.

ALC-FRM-001-032 Failed to load XCI file. Verify that correct XCI URL is specified in options API parameter.

ALC-FRM-001-033 The options specified are not compatible.

Adjust the options parameter.

ALC-FRM-001-034 Failed to initialize the default values of options.

Verify that Forms ES configuration EJB is initialized properly.

ALC-FRM-001-035 Failed to retrieve the template contents. Verify that FormsQuery and ContentRootURI are specified correctly.

ALC-FRM-001-036 Failed to load updated version of Template.


ALC-FRM-001-037 Failed to load updated version of Template.


ALC-FRM-001-040 The service is not initialized properly. Contact the system administrator.

ALC-FRM-001-041 The Forms service does not support PDF/A transformation.

Use Output service for generating PDF/A transformations.



ALC-FRM-001-042 The Reader Extensions service is not deployed.

To add usage rights to a form, the Reader Extensions service is required. Ensure that Reader Extensions service is deployed.

ALC-FRM-001-043 The format of supplied the PDF form is unsupported.

Ensure that the supplied PDF is an XFA form or a form created in Acrobat.

ALC-FRM-001-045 The Acrobat version passed in the options is not supported.

Ensure that correct Acrobat version is passed in options.

ALC-FRM-001-046 Value of the specified input parameter is null.

Pass non-null value of the specified parameter.

ALC-FRM-001-048 Forms with usage rights cannot be linearized.

Ensure that the Linearized option is not enabled if the form has usage rights applied.

ALC-FRM-001-049 Multiple attachments with the same file name exist.

Ensure that multiple attachments with the same name do not exist.

ALC-FRM-001-050 A null response was received from Forms ES when trying to render the form.

Verify the format of the form design, and see the logs for more details.

ALC-FRM-001-051 An exception occurred while creating credential array.

Review the User Credentials set

ALC-FRM-001-052 An exception occurred while extracting request information from callback invocation.

Verify that valid request information, for example Form Query, Content Root URI, and Timestamp, are being sent.

ALC-FRM-001-053 Unable to make changes to the input PDF document as it has a certifying signature that does not permit any changes.

Verify that the PDF has a certifying signature that does not permit any changes.

ALC-FRM-001-054 The document supplied as input is not a PDF form capable of supporting data merge.

Input a PDF form capable of supporting data merge.

ALC-FRM-001-055 A [PDFSecurity] exception thrown while unlocking the encrypted document.

Verify that the PDF is password protected. Forms cannot render a password protected PDF.

ALC-FRM-001-056 A [PDF Security] exception thrown while getting the document's interactive form (Acroform) dictionary

Verify that the PDF is password protected. Forms cannot render a password protected PDF.



ALC-FRM-001-058 A valid path component cannot be retrieved from the [repositoryURI]. The path component retrieved is null or empty.

When Content Root URI refers to a repository location then it should conform to the format: repository://authority/form location.

For example if Form to Render is set as formName, and Content Root URI is set as repository:/a/b/, then authority is null and form path is resolved as /a/b/formName.

Similarly, if Content Root URI is set as repository:///a/b/, then authority is empty and form path is /a/b/formName.

If Form to Render is set as /formName and Content Root URI is set as repository://a/b, then authority is a and form path is /b/formName.

Ensure the [repositoryURI] value is not null or empty.

ALC-FRM-001-059 An exception occurred when trying to read a resource from repository with an invalid URI.

Verify that the repository content root URI begins with repository:

ALC-FRM-001-104 An error occurred while loading options. Contact the system administrator.

ALC-FRM-001-501 This error is used for INFO logging. No action needed.

ALC-FRM-001-502 Generated snap-in name. No action needed.

ALC-FRM-001-503 This error message returns the number of bytes returned.

No action needed.

ALC-FRM-001-504 This error message is used for logging the XDC name.

No action needed.

ALC-FRM-001-505 This error message is used for logging the context name.

No action needed.

ALC-FRM-001-508 This error message is used for logging the PDF version of the rendered PDF.

No action needed.

ALC-FRM-001-511 This error message is used for logging the method entered while processing.

No action needed.

ALC-FRM-001-512 This error message is used for logging the method exited while processing.

No action needed.

ALC-FRM-001-513 This error message indicates that the Merge/Calculate will not be performed.

No action needed.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Output ES 67

LiveCycle Output ES

ALC-FRM-001-514 Forms ES should have removed the Overlay Data.

No action needed.

ALC-FRM-001-515 Incompatible Form model: Form may render incorrectly. Form has some server side scripts which may not be executed as the value of FormModel is set to Client.

Verify that the form has server side scripts which may not be executed.

ALC-FRM-001-701 The ServiceUtil service is already initialized with service: FormsService. Aborting Cache re-initialization

The cache cannot be re-initialized for the service. Please contact the system administrator

ALC-FRM-001-702 Invalid value for Max Document size in cache, so the default value will be used.

Verify if a valid integer value has been configured for the Max Document size in cache.

ALC-FRM-001-703 An exception occurred while initializing the cache from startup.


ALC-FRM-001-704 An exception occurred while closing the cache.


ALC-FRM-001-705 An exception occurred while reading cache config stream.


ALC-FRM-001-706 An exception occurred while creating cache config stream.


ALC-FRM-001-707 Starting LiveCycle Forms ES. No action needed.

ALC-FRM-001-708 Stopping LiveCycle Forms ES. No action needed.

ALC-FRM-001-801 Forms ES Config EJB could not be initialized.

Please contact the system administrator.



ALC-OUT-001-001 The parameter is missing. Specify the parameter.

ALC-OUT-001-002 The transformation ID cannot be determined based on the provided inputs.

The useragent string may be the cause; it may not be recognized or supported.

ALC-OUT-001-003 The format of the useragent string is invalid.

Verify the useragent value.

ALC-OUT-001-004 Failed to look up the XMLForm or Font Manager service.

Verify that these services started properly.


ALC-OUT-001-005 FDF or XFDF (alone) has been passed in with incompatible clientCache option.

Pass the data in correct format.

ALC-OUT-001-006 Failed to load template from the specified URI.


ALC-OUT-001-010 Format of XDP data is invalid. Verify the format of data.

ALC-OUT-001-011 The options format does not comply with Forms ES expected format.

Update the option.

ALC-OUT-001-012 Invalid value specified for option. Verify the option value.

ALC-OUT-001-013 XMLForm failed to render the form. Verify the format of template.

ALC-OUT-001-014 Forms service invoked XMLForm but received a failure in response.


ALC-OUT-001-015 Content type of submitted data is not supported.

Verify that data is being submitted in the correct format.

ALC-OUT-001-016 A parse error has been encountered while processing internal XML data.

This could be due to invalid data being passed into the API. Verify that XML data passed is well-formed.

ALC-OUT-001-018 The specified file is not available. Update the file path or verify the API parameter values, such as ContentRootURI.

ALC-OUT-001-019 An invalid URL is specified. Update the URL; verify the API parameter values, such as BaseURL.

ALC-OUT-001-020 Either the data is not matched with the data type or it is corrupted.


ALC-OUT-001-021 An invalid URI is specified. Update the URI.

ALC-OUT-001-022 An unexpected exception has occurred.


ALC-OUT-001-023 The specified transformation is not supported.

Verify the value of the API parameter formPreference.

ALC-OUT-001-024 The environment buffer passed to the API is not correct.

Verify that it is not null.

ALC-OUT-001-025 The request buffer passed to the API is not correct.

Verify that it is not null.

ALC-OUT-001-026 The cache directory configuration is not correct.

The cache directory is based on data specified by the Forms ES configuration. Verify the cache configuration.



ALC-OUT-001-028 Caching is disabled because of unexpected error.


ALC-OUT-001-032 Failed to load XCI file. Verify that correct XCI URL is specified in options API parameter.

ALC-OUT-001-033 Unable to extract the XDP from PDF, proceeding with PDF only (Re-render will not occur).

No Action needed.

ALC-OUT-001-034 Meta Data will not be generated, because the file URI is not provided.

Provide a valid URI location for MetaData Spec file

ALC-OUT-001-035 Failed to load the PDF from the given location.

Provide a valid location for the PDF form.

ALC-OUT-001-036 Generic log message. No Action needed.

ALC-OUT-001-103 Failed to load the options required to create property editor.


ALC-OUT-001-104 Failed to load the options (because of parsing error) required to create property editor.


ALC-OUT-001-105 Failed to load the options (because of IO error) required to create property editor.


ALC-OUT-001-106 Failed to load the options (because of parser configuration error) required to create property editor.


ALC-OUT-001-201 Input document is already a flat PDF document.

Ensure that input document is not already flattened.

ALC-OUT-001-202 Document is not a valid PDF document.

Ensure that input document is a valid PDF.

ALC-OUT-001-203 Security issue(s) processing PDF document.

Ensure that input is not a secured document.

ALC-OUT-001-204 Failed to transform the input PDF to non-interactive PDF.

Review the log files for details.

ALC-OUT-001-205 Specified input parameter is null. Ensure that the specified input parameter is not null.

ALC-OUT-001-206 XFAService failed to get the XDP stream from PDFDocument.


ALC-OUT-001-207 Invalid value for the transformation input parameter.

Review the value of the transformation input format.



ALC-OUT-001-208 Invalid input PDF for PDFA transformation. Only XFA PDF with no rights, signature, or certification is allowed.

Ensure that the input PDF document is XFA PDF with no rights, signature, or certification.

ALC-OUT-001-209 Input PDF is not supported for Transformation. Only XFA and Acrobat Form PDF are supported.

Ensure that the input PDF is XFA or Acrobat Form.

ALC-OUT-001-210 Specified input parameter is required. Ensure that the specified input parameter is provided.

ALC-OUT-001-211 Invalid PDF/A revision number. Ensure that the PDF/A revision number is: 1

ALC-OUT-001-212 Invalid PDF/A conformance. Ensure that the PDF/A conformance is A or B.

ALC-OUT-001-301 Failed to process the input XFAF template.




ALC-OUT-001-303 Failed to extract XFA definition from XFA PDF.


ALC-OUT-001-304 Input XFAF document is null. Ensure that a non-null input document is passed.





ALC-OUT-001-401 Metadata is not generated when the destination file URI is not provided.

Provide the destination file URI for generating metadata.

ALC-OUT-001-402 Failed to connect to given queue name. Ensure that it is a valid queue name.

ALC-OUT-001-403 Failed to connect to given server name. Ensure that it is a valid and reachable server.

ALC-OUT-001-404 Unknown error while printing Contact the system administrator.

ALC-OUT-001-405 Malformed URI Review the Printer URI.

ALC-OUT-001-406 Required parameters missing Verify that all the required parameters for printing are sent.

ALC-OUT-001-407 Access denied by the printer. Verify that the user has printer access.

ALC-OUT-001-408 The connection not accepted by the Printer Server.

Verify that the printer does not have too many active connections.



ALC-OUT-001-409 Could not find printer resource for the UNC path provided.

Review the printer configuration.

ALC-OUT-001-601 Failed to load the template that corresponds to the data record as indicated by the sniff rule.

Verify that the default form design and all other form templates specified in the sniff rules are valid.

ALC-OUT-001-603 Failed to extract multiple stream output with non-self-contained files.

If your files are generated in fragments, you should request that a single output stream get a concatenated output stream.

ALC-OUT-001-604 Failed to load the metadata specification file properly.

Ensure that metadata files exists and it should be a well-formed XML.

ALC-OUT-001-605 Failed to load the metadata specification file properly.


ALC-OUT-001-606 No system level meta attributes are defined in the metadata specification. Defaults would be used.


ALC-OUT-001-607 No user level meta attributes are defined in the metadata specification. Only system metadata would be generated.


ALC-OUT-001-608 The record depth in the data file does not match with the record level or record name.

Ensure that record level or record name is given in accordance with the input data file.

ALC-OUT-001-701 ServiceUtil already initialized with service. Aborting cache re-initilaization.

Cache cannot be re-initialized for the service. Contact the system administrator.

ALC-OUT-001-702 Invalid value for Max Document size in cache, default value will be used.

Verify that a valid integer value is used for max document size.

ALC-OUT-001-703 Exception while initializing cache from startup

Examine the logs for details.

ALC-OUT-001-704 Exception while closing Cache Examine the logs for more details.

ALC-OUT-001-705 Exception while reading cache config stream

Examine the logs for more details.

ALC-OUT-001-706 Exception while creating cache config stream


ALC-OUT-001-707 Starting LiveCycle Output ES. No Action needed.

ALC-OUT-001-708 Stopping LiveCycle Output ES. No Action needed.

ALC-OUT-001-801 The Forms ES configuration EJB could not be initialized.




ALC-OUT-001-914 Used for logging. No Action needed.

ALC-OUT-002-001 The parameter is missing. Specify the parameter

ALC-OUT-002-005 An FDF or XFDF (alone) has been passed with incompatible clientCache option Pass.

Change the clientCache option to a compatible option.

ALC-OUT-002-006 Failed to load template from the specified URI.


ALC-OUT-002-008 An invalid attempt to translate the layout of a PDF or Image.

Review the logs for more details.

ALC-OUT-002-010 The format of XDP data is invalid. Verify the format of the data.

ALC-OUT-002-011 The format of the option does not comply with the expected Forms ES format.

Change the format of the option.

ALC-OUT-002-012 Invalid value specified for the option. Verify the value of the option.

ALC-OUT-002-013 Forms ES failed to render the form. Verify the format of form design.

ALC-OUT-002-014 Forms ES has received an invocation failure response.

Review the log file for more details.

ALC-OUT-002-016 A parse error has been encountered while processing internal XML data. This could be due to invalid data being passed into the API.

Verify any xylem-data passed in is well-formed.

ALC-OUT-002-017 Forms ES failed to render the form. Review the logs for more details

ALC-OUT-002-018 The specified file is not available Update the file path or verify the API parameter values such as the ContentRootURI value.

ALC-OUT-002-019 An invalid URL is specified. Update the URL, verify the API parameter values such as the BaseURL value.

ALC-OUT-002-020 The data is corrupt, or does not matched the data type.


ALC-OUT-002-021 An invalid URI is specified. Update the URI.

ALC-OUT-002-022 An unexpected exception has occurred.


ALC-OUT-002-023 The specified transformation is not supported.

Verify the value of formPreference API parameter.

ALC-OUT-002-025 The request buffer passed to the API is not correct.

Verify the request buffer is not null.



ALC-OUT-002-026 The cache directory configuration is not correct. The cache directory is based on data specified by the Forms ES configuration.

Verify the cache configuration.

ALC-OUT-002-028 Caching has been disabled because of an unexpected error.


ALC-OUT-002-029 An unexpected problem occurred. Review the log files, and contact the system administrator.

ALC-OUT-002-032 Unable to load the XCI file. Verify that correct XCI URL is specified in options API parameter.

ALC-OUT-002-033 The options specified are not compatible.

Adjust the options parameter.

ALC-OUT-002-034 Failed to initialize the default option values.

Verify that the Forms ES configuration EJB is initialized properly.

ALC-OUT-002-035 Could not retrieve the form design contents.

Verify that FormsQuery and ContentRootURI are specified correctly.

ALC-OUT-002-036 Failed to load the updated version of the form design.


ALC-OUT-002-037 Failed to load the updated version of the form design.


ALC-OUT-002-040 Forms ES service is not initialized properly.


ALC-OUT-002-042 Reader Extensions ES service is not deployed.

To add usage rights to a form, Reader Extensions ES is required. Ensure that Reader Extensions ES is deployed.

ALC-OUT-002-043 The format of the supplied PDF form is unsupported.

Ensure that the supplied PDF is and XFA form or Acroform.

ALC-OUT-002-045 The version of Acrobat specified in the options parameter is not supported.

Ensure that correct Acrobat version is passed in the options parameter.

ALC-OUT-002-046 Value of the specified input parameter is null.

Ensure the input parameter contains a non-null value.

ALC-OUT-002-048 Forms with rights cannot be linearized. Ensure that the Linearized option is not enabled if the form has usage rights applied.

ALC-OUT-002-049 An existing attachment uses the same file name as the attachment currently being added. The original attachment will be overwritten.

Rename one of the attachments so that they use different file names.



ALC-OUT-002-050 Null response from Forms ES when trying to render the XFA form.

Verify the format of the form design, and see the logs for more details.

ALC-OUT-002-051 An exception occurred while creating credential array.

Review the User Credentials set.

ALC-OUT-002-052 An exception occurred while extracting request information from a callback invocation.

Verify that valid request information, such as Form Query, Content Root URI, and Timestamp, are being sent.

ALC-OUT-002-053 Unable to make changes to the input PDF document as it has a certifying signature that does not permit any changes.

Verify that the PDF has a certifying signature that does not permit any changes.

ALC-OUT-002-054 The document supplied as input is not a PDF form capable of supporting data merge.

Transmit a PDF form capable of supporting data merge.

ALC-OUT-002-055 A PDF security exception is thrown while unlocking the encrypted document.

Verify that the PDF is not password protected. Forms cannot render a password protected PDF.

ALC-OUT-002-056 A PDF security exception is thrown while getting the interactive form (Acroform) dictionary for the document.

Verify that the PDF is not password protected. Forms cannot render a password protected PDF.

ALC-OUT-002-058 A valid path component cannot be retrieved from the repository URI.The path component retrieved is null or empty.

When Content Root URI refers to a repository location then it should be in the form:

repository://authority/form location

For example if Form is set as formName and if Content Root URI is set as repository:/a/b/, then authority is null and form path is resolved as /a/b/formName. Similarly, if Content Root URI is set as repository:///a/b/, then authority is empty, and form path is /a/b/formName.

If Form is set as /formName, and Content Root URI is set as repository://a/b, then authority is a and form path is /b/formName.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle PDF Generator ES 75

LiveCycle PDF Generator ES

ALC-OUT-002-059 An exception occurred while trying to read a resource from repository due to an invalid URI.

Verify that the repository content root URI begins with repository:.

ALC-OUT-002-104 An error occurred while loading options.




ALC-PDG-80000 Internal exception. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-80001 Unable to look up job configuration. Ensure the correct job option name exists in the PDF Generator ES database.

ALC-PDG-80002 Missing extension in file name. Input filenames should have correct extensions indicating the file type.

Correct the missing file extension and try the operation again.

ALC-PDG-80003 An attempt has been made to convert a native document using the ExportPDF API for conversion.

For conversion of native documents to PDF, use createPDF.

ALC-PDG-80004 An attempt has been made to convert a PDF document using the CreatePDF API.

For conversion of PDF documents to other formats, use exportPDF.

ALC-PDG-80005 Conversion failure. Converted doc not found.

Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-80006 Trying to attach source file to a PDFA compatible PDF.

Deselect attach source option or create non PDFA compliant PDF.

ALC-PDG-80007 Trying to apply security to PDF/A, PDF/X1a:2003 or PDF/X3:2003 compliant PDFs

Create PDF/A, PDF/X1a:2003 or PDF/X3:2003 compliant PDFs without security options.

ALC-PDG-80008 PDF version of security exceeds PDF version of job options

Use appropriate job options and security settings so that PDF versions match.

ALC-PDG-80009 The PDF open password and the PDF change passwords are identical.

Select different PDF open and change passwords.


ALC-PDG-80010 Trying to embed job-options in PDF/A, PDF/X1a:2003 or PDF/X3:2003 compliant PDFs

Deselect the option to embed job-options in PDF/A, PDF/X1a:2003 or PDF/X3:2003 compliant PDFs

ALC-PDG-80011 The format type being requested for PDF export is not supported.

Use a supported format type.

ALC-PDG-80012 An operation called without corresponding service being installed.

Install appropriate service.

ALC-PDG-80013 Invalid settings file for HTML to PDF operation.

Add HTML2PDF section to settings file being used for conversion.

ALC-PDG-80014 HTML to PDF conversion failed because of an exception.


ALC-PDG-80015 The caller does not have sufficient permission(s) for invoking the operation.

Ask administrator for permissions.

ALC-PDG-80016 The system cannot convert encrypted files.

Don't give encrypted files for conversion.

ALC-PDG-80017 Image to PDF conversion failure. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-80018 Problem with license, see log for details


ALC-PDG-80019 HTML to PDF failure. Input ZIP file does not contain the index HTML file.

Input ZIP file should contain an index HTML file as a starting point.

ALC-PDG-80020 Input file type is not supported in HTML to PDF conversion.

HTML to PDF supports .htm or .html files. Provide appropriate inputs only.

ALC-PDG-80021 Error while deflating ZIP file. Ensure ZIP file is not corrupt.

ALC-PDG-80022 Unable to build a valid trusted certificate path to requested secure URL.


ALC-PDG-1000 Conversion failed because of an exception.




ALC-PDG-1001 The Job Configuration either cant be obtained or is invalid.

Please provide valid job configuration. If providing job configuration name, ensure it exists in database.

ALC-PDG-1002 There was an error in validating and writing the configuration job options.

Ensure that job-options are correct.

ALC-PDG-1003 Error while creating temporary directories.

Ensure the application server user has valid permissions on the file system.

ALC-PDG-1004 PDF Generator ES configuration service lookup failed.

Contact the system administrator. It is likely that there is an issue with the PDF Generator ES installation.

ALC-PDG-1005 An error occurred while determining the PDF Generator ES product type.


ALC-PDG-1006 You do not have PDF Generator ES Professional version installed, which supports these formats.

Contact administrator for PDF Generator ES professional installation.

ALC-PDG-1007 An error occurred while determining the product license.


ALC-PDG-1008 An error occurred while transforming the application configuration.


ALC-PDG-1009 The service to convert the document could not be looked up.


ALC-PDG-1010 An error occurred while applying watermark to the document.


ALC-PDG-1011 The BMC reported failure in converting the document.

Ensure file is not corrupt and is convertible to PDF using standalone Acrobat.

ALC-PDG-1012 The job options in the configuration could not be parsed.

Provide valid job-options.

ALC-PDG-1013 An error occurred while linearizing and attaching job options to the document.


ALC-PDG-1014 An error occurred while linearizing the document.




ALC-PDG-1015 This file type is not supported. Get a list of supported file types from Adobe Technical Support.

ALC-PDG-1016 PDF Settings are not correct. Ensure using correct PDF settings.

ALC-PDG-1017 Security settings cannot be applied with the Adobe PDF Settings you selected.

Review the compatibilities, or remove password security.

ALC-PDG-1018 You submitted a PDF file for conversion without enabling OCR in file-type settings. This operation is invalid.

Either select OCR option in file-type settings or do not use PDF as input file type in "CreatePDF" API.

ALC-PDG-1019 An error occurred while launching AutoCAD.

Verify whether AutoCAD is installed on the server.

ALC-PDG-1020 An error occurred while launching Microsoft Excel.

Verify whether Microsoft Excel is installed on the server.

ALC-PDG-1021 An error occurred while launching Microsoft PowerPoint.

Verify whether Microsoft PowerPoint is installed on the server.

ALC-PDG-1022 An error occurred while launching Microsoft Project.

Verify whether Microsoft Project is installed on the server.

ALC-PDG-1023 An error occurred while launching Microsoft Visio.

Verify whether Microsoft Visio is installed on the server.

ALC-PDG-1024 An error occurred while launching Microsoft Word.

Verify whether Microsoft word is installed on the server.

ALC-PDG-1025 Conversion failed because of an exception.

If exception message doesn't help, contact the system administrator and report the issue to Adobe Technical Support.

ALC-PDG-1026 Environment variable DISPLAY is not set on the server.

Set the DISPLAY environment variable to point to a valid XServer and restart application server.

ALC-PDG-1027 Job Configuration doesn't have file settings.

Use a valid job-configuration with file type settings corresponding to requested conversion.

ALC-PDG-1028 Invalid transport protocol requested. Only HTTP and HTTPS are supported. Do not use any other protocol.

ALC-PDG-1029 No job configuration specified Specify a valid job configuration.

ALC-PDG-1030 The HTTP request property 'Content-Length' value must be larger than 0


ALC-PDG-1031 Document size is zero. Document size must be larger than zero.



ALC-PDG-1032 Invalid input. Error message self explanatory.

ALC-PDG-1033 Invalid input. Error message self explanatory.

ALC-PDG-1034 Required HTTP header missing. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-1035 Could not connect to PDF Generator ES service.


ALC-PDG-1036 The PDF Generator ES permission(s) have not been initialized.


ALC-PDG-1037 The PDF Generator ES resource(s) have not been initialized.


ALC-PDG-1038 An error occurred while launching Microsoft Publisher.

Verify whether Microsoft Publisher is installed on the server.

ALC-PDG-1039 Microsoft Office was not able to open the document that was submitted for conversion.

Ensure document is not corrupt.

ALC-PDG-9001 Could not find path to the application. Verify that the application is installed and <ApplicationName>_PATH environment variable is set.

ALC-PDG-9004 Could not find path to the application. Verify that the application is installed and <ApplicationName>_PATH environment variable is set.

ALC-PDG-10001 An unexpected internal error occurred. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-10003 Trying to use same password for documentChange and documentOpen.

Use separate passwords for document open and change.

ALC-PDG-10004 Restricted Security requires a documentChange password which is not supplied.

Provide a document change password.

ALC-PDG-10005 Unable to obtain the Conversion COM interface from PDFMaker.

Verify Acrobat is properly installed on the LiveCycle ES server. If problem persists, contact Adobe Technical Support.



ALC-PDG-10006 The security configuration provided was null.

Provide a non-null security configuration.

ALC-PDG-10007 Unable to convert file because there is a pre-existing Acrobat.exe process.

Kill all running Acrobat.exe processes on LC server.

ALC-PDG-10008 Unable to obtain the Security COM interface from PDFMaker.

Verify Acrobat is properly installed on the LiveCycle ES server. If the problem persists, contact Adobe Technical Support.

ALC-PDG-10009 The security configuration provided was null.

Provide non-null security configuration.

ALC-PDG-10010 The conversion has timed out. Increase conversion timeout parameter and retry.

ALC-PDG-10011 Unable to contact PDFMaker. Ensure Acrobat is installed and PDFMaker.dll is registered.

Verify Acrobat is properly installed on the LiveCycle ES server. If the problem persists, contact Adobe Technical Support.

ALC-PDG-10012 PDFMaker reported an error while printing the document.

Verify Acrobat standalone can convert the input file. If so, contact Adobe Technical Support.

ALC-PDG-10013 The JVM reported lack of sufficient privileges while converting the document to PDF.

Contact the system administrator. Sufficient privileges need to be provided to appserver user.

ALC-PDG-10014 The underlying method for converting document to PDF was not found at runtime.


ALC-PDG-10015 The conversion operation timed out before it could be completed.

Increase the timeout parameter and retry.

ALC-PDG-10016 Unable to create temp file for stdin. Verify that the application server user has sufficient permissions to create files on server. Contact the system administrator.

ALC-PDG-11011 The system encountered an unexpected error while processing this request.


ALC-PDG-11012 There was an error looking up a dependent component or a service.




ALC-PDG-11013 Unable to submit job for conversion. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-11014 The chosen security settings are not compatible with the chosen job-options.

Use compatible job-options and security settings for conversions.

ALC-PDG-11015 The specified settings were not found. Settings to be used for conversions should be imported into PDF Generator ES first using LiveCycle Administration Console.

ALC-PDG-11016 An error was encountered while processing the configuration settings.


ALC-PDG-11017 The specified credentials are not authorized to perform the specified action.

Contact the system administrator to obtain sufficient permissions.

ALC-PDG-11018 An invalid job ID was provided. Ensure you provide a valid job-ID. If it is valid, contact the system administrator.

ALC-PDG-11019 The source file you submitted is invalid. Verify that the file is not corrupt and is a supported format.

ALC-PDG-11020 The source file you submitted is not supported by this version of PDF Generator.

Get the supported list of file formats from Adobe Technical Support.

ALC-PDG-11021 WebCapture is not supported by this version of PDF Generator.

Contact administrator to purchase valid licenses.

ALC-PDG-11022 The local file for the SOAP attachment cannot be found.


ALC-PDG-11023 The specified job was not found. It may have been deleted.

Contact the system administrator to ensure the job was not deleted on purpose.

ALC-PDG-11024 The source type you specified is invalid.

Get a list of supported formats from Adobe Technical Support.

ALC-PDG-11025 No document has been provided for conversion.

Provide a non-null input document.

ALC-PDG-11026 Error while doing OCR on the document.

Verify that the document is not corrupt. Try converting the file using standalone Acrobat.



ALC-PDG-11027 Error while converting an OpenOffice document.

Verify that the document is not corrupt. Try converting the file using standalone OpenOffice.

ALC-PDG-11028 Error while converting image to PDF. Verify that the image is not corrupt. If not, report to Adobe Technical Support.

ALC-PDG-11030 Could not convert document as unable to launch OpenOFfice.

Verify that OpenOffice is installed on the server and environment variable OpenOffice_PATH is set.

ALC-PDG-11031 Error while exporting to the selected format.


ALC-PDG-11032 Input PDF is password protected. Do not give password protected inputs.

ALC-PDG-11033 Unable to find the working directory for the current request.

Verify that the application server user has permissions to create files. Report to system administrator.

ALC-PDG-11034 Unable to find the PDFGen.api plug-in file in the Acrobat plugins folder.

Copy PDFGen.api file from the PDF Generator ES installation to the Acrobat plug-ins folder on the server.

ALC-PDG-11035 ExportPDF functionality is only supported on the windows platform.

No action. Cannot use ExportPDF functionality on non-windows platform.

ALC-PDG-11036 Acrobat encountered a problem in processing the input file.


ALC-PDG-11037 Error while converting the input file to PDF using Acrobat.


ALC-PDG-12001 This file could not be converted to PDF. Verify that the input file is a supported format. Contact the system administrator and report the issue to Adobe Technical Support.

ALC-PDG-12011 The supplied PostScript has errors. Use a valid PostScript file.

ALC-PDG-12012 The PostScript interpreter ran out of memory.

Contact the system administrator and get memory increased on server.

ALC-PDG-12013 The PostScript interpreter ran out of disk space.

Contact the system administrator and get disk space increased on server.



ALC-PDG-12014 There was an internal PostScript interpreter error.


ALC-PDG-12015 The PostScript conversion was canceled.

No action.

ALC-PDG-12016 The conversion has timed out. Increase timeout parameter for conversions.

ALC-PDG-12017 Cannot embed job-options inside PDF/A:Draft compliant PDF documents.

De-select the option to embed job-options for PDF/A:Draft compliant PDF documents.

ALC-PDG-12018 The PDF open password and the PDF change passwords are identical.

Use different PDF open password and the PDF change passwords .

ALC-PDG-12019 Trying to apply password-based encryption to PDF/A:Draft compliant PDF documents.

Do not apply password-based encryption to PDF/A:Draft compliant PDF documents.

ALC-PDG-12020 The filename is invalid since it does not have an extension.

Filename should contain extension indicating file type.

ALC-PDG-12021 The filename extension is neither PS or EPS.

Use .ps or .eps files for Distiller service.

ALC-PDG-12501 Runtime error while converting this file.


ALC-PDG-12511 The job data could not be retrieved. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-12512 The job options could not be retrieved. Verify that the job-option name exists.

ALC-PDG-12513 Could not save error message to a file. Verify that the application server user has appropriate permissions to write files on server.

ALC-PDG-12514 Unknown runtime error. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-12515 The lookup for a dependent service failed.




ALC-PDG-12516 A network communication error was encountered.

Ensure network was not broken during conversions. Contact the system administrator and report the issue to Adobe Technical Support.

ALC-PDG-12517 An input/output error was encountered.


ALC-PDG-12518 Unable to create a data buffer from a file.


ALC-PDG-15001 Cannot convert file--Acrobat Professional trial version has expired.

Contact the system administrator and get a valid Acrobat license.

ALC-PDG-15002 Cannot convert file--the system clock has been moved backwards farther than the Acrobat Professional trial license allows.


ALC-PDG-15003 The system cannot open the file. Submit your file again or contact your system administrator.

ALC-PDG-15004 The application cannot open the file and needed to repair it and caused significant modifications to the file.

File is corrupt. Supply a valid file.

ALC-PDG-15005 There was an error processing a page of the document.

Verify that the file is not corrupt and submit file again.

ALC-PDG-15006 One or more files uploaded for collation is protected.

Remove security permissions and try again.

ALC-PDG-15007 A document cannot be inserted into itself.

No action.

ALC-PDG-15008 The system cannot save the document. Verify that the application server user has sufficient file write permissions.

ALC-PDG-15009 Protocol not supported. Contact Adobe Technical Support to get a list of supported protocols.

ALC-PDG-15010 An invalid URL was submitted. Submit valid URLs.

ALC-PDG-15011 An empty document cannot be created.

No action.

ALC-PDG-15012 The system cannot apply Acrobat Security as the Open and Change Security Passwords for the document are unique.

Use different Open and Change security passwords.



ALC-PDG-15013 Acrobat cannot open the file, it may be either corrupt or an unsupported type.

Use a valid input file.

ALC-PDG-15014 File size not supported. The system cannot convert file with page width or height that is beyond the supported maximum of 200 inches. Please reduce the dimensions and submit your file again.

ALC-PDG-15015 Invalid file plot area. The system cannot convert file with this plot area. Please change the plot area to Layout or Extents and submit your file again.

ALC-PDG-15016 The system cannot create a PDF file with bookmarks, links, or Tagged PDF for Chart placed as Worksheets, Macro Sheets, or Dialog Sheets.

Please edit and submit your file again.

ALC-PDG-15017 The system cannot create a PDF file with bookmarks, links, or Tagged PDF when document is a shared workbook.


ALC-PDG-15018 The system cannot convert file that is blank.


ALC-PDG-15019 The system cannot create a PDF file with bookmarks, links, or Tagged PDF when document contains protected worksheets.

Remove protection on the worksheets in the Tools menu, and submit your file again.

ALC-PDG-15020 The system cannot create a PDF file with bookmarks, links, or Tagged PDF when document is a protected workbook.

Remove protection on the workbook in the Tools menu, and submit your file again.

ALC-PDG-15021 The system cannot convert file that contains setting of "Fit to x Pages Wide by y Pages Tall".

Edit in Page Setup dialog and submit your file again.

ALC-PDG-15022 The system cannot convert file that contains worksheets with more than one Print Area.

Clear Print Area and submit your file again.

ALC-PDG-15023 The system cannot convert file that contains worksheets with Print Titles.

Clear Print Titles in Page Setup dialog and submit your file again.

ALC-PDG-15024 The system cannot create a PDF file with bookmarks, links, or Tagged PDF that contain worksheets with Header/Footer size greater than Top and Bottom margins.

Reduce the Header/Footer size in the Page Setup dialog and submit your file again.



ALC-PDG-15025 The system cannot convert file that contains worksheets with different Print Quality settings.

Edit in Page Setup dialog to ensure worksheets don't have different Print Quality Settings and submit your file again.

ALC-PDG-15026 The system has reported that application has encountered a problem.

Please submit your file again. If problem persists, contact your system administrator and report the issue to Adobe Technical Support.

ALC-PDG-15027 The system cannot convert file that contains no printable data.

Please edit file to include some printable area and submit your file again.

ALC-PDG-15028 The system has reported the directory name is invalid.


ALC-PDG-15029 The system has reported that the application finds the file format invalid.

The input file should be in a supported format. You can get a list of supported formats from Adobe Technical Support.

ALC-PDG-15030 A resource error has occurred, there is not enough memory or disk space on the system.


ALC-PDG-15031 The system cannot convert file that contains links to other folders not accessible.

Verify that the links in input file are valid and accessible.

ALC-PDG-15032 An error occurred during Tagged PDF file generation


ALC-PDG-15033 File appears to be corrupted. Please correct and submit your file again.

ALC-PDG-15034 The system cannot convert file that contains macros.

Remove all macros and submit your file again.

ALC-PDG-15035 The system cannot read the file. Verify that the input file is not corrupt.

ALC-PDG-15036 A table in the file has become corrupted.

Select the table and choose Convert Table To Text from the Table menu and submit your file again.

ALC-PDG-15037 The system has reported that Excel cannot find or read the file.

Verify that the input file is not corrupt.

ALC-PDG-15038 The system has reported that Word cannot find or read the file.




ALC-PDG-15039 The system cannot convert password protected or read-only files.

Verify that the input file is not password protected or read-only.

ALC-PDG-15040 A system error has occurred. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-15041 There was an error receiving data from a URL.

Verify that the input URL is valid and accessible.

ALC-PDG-15042 The system cannot convert file that contains Visual Basic project references.

Remove Visual Basic project references from file and submit again.

ALC-PDG-15043 An encoding type is needed when opening the file by Microsoft Word.

Use an input file with supported encoding which can open in Microsoft Word.

ALC-PDG-15044 HTML Import Errors: There are missing files.

Ensure URL/input HTML file is correct and accessible.

ALC-PDG-15045 CRASH: A system error has occurred. File caused program to exit.


ALC-PDG-15046 Publication contains links to data source files created by external applications or mail client not found on our system.

Edit file to remove inaccessible links and submit again.

ALC-PDG-15047 The system cannot convert file that contains links to external database files.

Edit file to remove links to external database files and submit again.

ALC-PDG-15048 The system cannot convert file that contains links to external references.

Edit file to remove external references and submit again.

ALC-PDG-15049 The system cannot create a PDF file with bookmarks, links, or Tagged PDF when "Highlight changes in printed document" is selected.

Edit file and submit again.

ALC-PDG-15050 The system cannot create a PDF file with bookmarks, links, or Tagged PDF.

Use valid settings and submit file again.

ALC-PDG-15051 The system cannot convert file that is protected for editing.

Verify that the file is not protected or read-only.

ALC-PDG-15052 Adobe PDF printer has failed to create a PDF file.

Try to create PDF using standalone Acrobat or report to Adobe Technical Support.



ALC-PDG-15053 The system cannot open the file. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-15054 There was an error found when printing the document.

Try submitting file again. If failure is persistent, contact Adobe Technical Support.

ALC-PDG-15055 CRASH: Program generated errors. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-15056 CRASH: A system error has occurred during the PDF generation.


ALC-PDG-15057 The system cannot locate fonts because they are unavailable or missing.


ALC-PDG-15058 The system cannot export a PDF file that does not allow text extraction.

Provide an input PDF that allows text extraction.

ALC-PDG-15059 The system reported errors that the image path could not be created and thus images will not be generated.

Please change the permissions and submit your file again.

ALC-PDG-15060 The system cannot convert password protected files which do not allow modifications.

Remove password protection and submit file again.

ALC-PDG-15061 The system cannot export untagged PDF file.

Verify that the input PDF file is tagged.

ALC-PDG-15062 The system cannot resolve tags in this document and thus cannot export it.

Verify that the input PDF file is tagged.

ALC-PDG-15063 The system cannot export password protected files.

Remove password protection and submit file again.

ALC-PDG-15064 CRASH: Application is unable to continue because of a hardware or system error.


ALC-PDG-15065 The system has reported that PowerPoint cannot read the file.


ALC-PDG-15066 The system cannot convert the file due to an error.

Submit file again. If problem persists, Contact the system administrator and report the issue to Adobe Technical Support.



ALC-PDG-15067 The system has reported that PowerPoint cannot open the file.


ALC-PDG-15068 The system has reported that PowerPoint has insufficient memory to process the file.

Contact the system administrator and get memory increased on LiveCycle ES server.

ALC-PDG-15069 The system has reported that PowerPoint received an error during conversion.

Verify that the input file is not corrupt. Contact the system administrator and report the issue to Adobe Technical Support.

ALC-PDG-15070 The system cannot create a PDF file with bookmarks, links, or Tagged PDF when the current view does not contain any tasks or resources.

Edit file to create a valid view and submit again.

ALC-PDG-15071 The system cannot print views or reports which have no tasks or resources displayed.

Edit file and submit again.

ALC-PDG-15072 PageMaker cannot convert the file when one or more previous version publications are found in the book list.

Convert all publications to PageMaker 7 and update the book list. Submit file again.

ALC-PDG-15073 The system has reported that Word has insufficient memory or disk space to process the file.

Contact the system administrator to get memory/disk space increased on the server.

ALC-PDG-15074 The system could not load the configuration files for the application window monitoring system.


ALC-PDG-15075 The system could not parse the configuration files for the application window monitoring system.


ALC-PDG-15076 The system cannot open the file because the application is incompatible.

Verify that the input file can be opened in a compatible application version.

ALC-PDG-15077 FrameMaker reports that this document has been damaged.

Verify that the input document is not corrupt.

ALC-PDG-15078 The system could not proceed with the step.


ALC-PDG-15079 One or more OPI image references within an EPS could not be resolved.

Use a valid input EPS file.



ALC-PDG-15080 Cannot convert PageMaker file from a format prior to version 4.0.

Use a later version PageMaker file.

ALC-PDG-15081 PageMaker cannot process publication's links.

Use a valid input PageMaker file.

ALC-PDG-15082 The system cannot convert file because the application found bad table index in the file.

Edit file to make a valid table index and submit again.

ALC-PDG-15083 PageMaker reports that the file cannot be translated to PC and converted to new version at the same time.

Use a valid input PageMaker file.

ALC-PDG-15084 Acrobat was unable to process the page because the Paper Capture recognition service unexpectedly terminated.


ALC-PDG-15085 Adobe product is not registered or activated.


ALC-PDG-15086 The filename has characters outside the system language.

Rename the input file to contain valid characters and submit again.

ALC-PDG-15087 Acrobat was unable to process the file because of insufficient permissions for image extraction.

Remove security from input file and submit again.

ALC-PDG-15088 This document cannot be converted because it contains a read-only embedded font.

Replace the font and submit your file again or contact your system administrator.

ALC-PDG-15089 PowerPoint cannot read the outline from this file. No text converter is installed for this file type.

Install a proper PowerPoint text converter on server and submit again.

ALC-PDG-15090 FrameMaker was not able to open the document.


ALC-PDG-16001 An invalid file path was specified for PDF post-processing.


ALC-PDG-16002 An input/output error occurred while post-processing the PDF document.




ALC-PDG-16003 An unknown/unexpected error occurred during PDF post-processing.


ALC-PDG-16004 Error occurred during native application invocation.


ALC-PDG-19001 An exception occurred in the Element's server.


ALC-PDG-19002 A configuration related error has occurred.


ALC-PDG-19003 The job queue could not be located. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19004 The PDF Generator ES server statistics bean could not be looked up.


ALC-PDG-19005 The settings are not supported for this product type.

Use compatible settings only.

ALC-PDG-19006 An exception occurred while loading the configuration.


ALC-PDG-19007 An exception occurred while committing the configuration.


ALC-PDG-19008 The config file is locked for updating. Please try after some time.

ALC-PDG-19009 The config file could not be parsed. Use a valid config file.

ALC-PDG-19010 The config file has been modified since last load.

Please reload configuration file.

ALC-PDG-19011 The setting is being used by a defined job source.

No Action.



ALC-PDG-19012 A new configuration settings could not be created.


ALC-PDG-19013 A read only configuration settings can not be changed.

Create a new setting instead.

ALC-PDG-19014 Both passwords in the security settings are same.

Use different passwords in security settings.

ALC-PDG-19015 A setting set as default can not be deleted.

Set a different setting as default and then delete.

ALC-PDG-19016 No name for the setting has been specified.

Specify a name for the setting to be saved.

ALC-PDG-19017 The name of the setting cannot contain special characters.

Remove special characters from name and save again.

ALC-PDG-19018 Some Extensions occur for more than one file type.

Ensure each extension occurs for only one filetype in file-type settings.

ALC-PDG-19019 The configuration setting can not be found.

Verify that the setting exists in the PDF Generator ES database.

ALC-PDG-19020 The job options are invalid and not well formed.

Use valid job-options.

ALC-PDG-19021 The settings with this name already exist.

Use a different name for the setting.

ALC-PDG-19022 The job options could not be parsed due to invalid structure.

Edit job-option and correct the structure.

ALC-PDG-19023 The job options could not pass the validation check.

Verify that the job-options are valid.

ALC-PDG-19024 The job options could not be written to configuration.


ALC-PDG-19025 The configuration XML is invalid. Edit the configuration XML and ensure it conforms to schema.

ALC-PDG-19026 The security settings and joboptions to be applied are incompatible.

Use compatible security and joboption settings.

ALC-PDG-19027 The joboptions to be applied are not proper.

Verify that the job-options conform to schema.

ALC-PDG-19028 The URL does not point to a valid Adobe PDF document.

Check the URL target and ensure its a valid PDF.



ALC-PDG-19029 The URL returned a Page not found 404 error".

Verify that the URL is accessible.

ALC-PDG-19030 Invalid value found corresponding to the key.


ALC-PDG-19031 Invalid character found - expected - <.

Use only valid characters in input files.

ALC-PDG-19032 Invalid character found - expected - >.

Use only valid characters in input files.

ALC-PDG-19033 Illegal location for dictionary. PDF file seems to be corrupt. Use a valid file.

ALC-PDG-19034 Unexpected dictionary end, no start. PDF file seems to be corrupt. Use a valid file.

ALC-PDG-19035 Illegal location for array. PDF file seems to be corrupt. Use a valid file.

ALC-PDG-19036 Unexpected array end, no start. PDF file seems to be corrupt. Use a valid file.

ALC-PDG-19037 Unknown character. Input file is corrupt. Use a valid file.

ALC-PDG-19038 Illegal location for the data, expected dictionary.

PDF file seems to be corrupt. Use a valid file.

ALC-PDG-19039 Unknown literal found. PDF file seems to be corrupt. Use a valid file.

ALC-PDG-19040 Unknown failure. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19041 Runtime Error. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19042 The specified value is not valid. Correct the specified value as given in error message

ALC-PDG-19043 The specified value is not valid. Correct the specified value as given in error message

ALC-PDG-19044 Integer value required. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.



ALC-PDG-19045 No joboptions map specified. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19046 No Distiller Params map found. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19047 No PageParams map found. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19048 Unknown data class found. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19049 The configuration is not loaded for editing.


ALC-PDG-19050 Invalid value for change permissions. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19051 Invalid value for print permissions. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-19052 Error in validating security settings changes.


ALC-PDG-19053 New job option settings could not be created.


ALC-PDG-19054 Error in validating initial view setting changes.


ALC-PDG-19055 JobOption settings not found. Verify that the setting exists in PDF Generator ES database



ALC-PDG-19056 Security settings not found Verify that the setting exists in PDF Generator ES database

ALC-PDG-19057 Filetype setting not found Verify that the setting exists in PDF Generator ES database

ALC-PDG-19058 Error in validating filetype setting changes


ALC-PDG-19059 PDFExport is not supported in PostScript version of the product

Contact the system administrator and get a valid PDF Generator ES license to support PDFExport.

ALC-PDG-19060 Encountered error while importing the XMP file.

Verify that the XMP file is valid XMP format.

ALC-PDG-19061 Failed to obtain password from the cipher


ALC-PDG-20001 Corrupt GIF file. Use a valid GIF file and try again.

ALC-PDG-20002 No imageIO readers available. This image file is currently not convertible. If you are running LC server on Windows platform, try the Acrobat conversion route.

ALC-PDG-20003 Corrupt image file. Try a different image file which is not corrupt.

ALC-PDG-20004 The TIFF image header contains a value of the "Photometric Interpretation" field that is not allowed.

Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20005 ycbcr color space not supported yet. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20006 Transparency mask not supported yet. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20007 Incomplete color map in the image. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.



ALC-PDG-20008 LZW with predictor not supported. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20009 JPEG 2000 not supported Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20010 Cannot handle extra samples in compressed data


ALC-PDG-20011 Cannot handle 16 bit compressed data.We need to down sample data as it is not handled properly otherwise


ALC-PDG-20012 Extra samples are only supported for 8 and 16 bit images


ALC-PDG-20013 Only single strip compressed data can be handled


ALC-PDG-20014 Compressed tiled format is not supported


ALC-PDG-20015 Unsupported bits per component Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20016 Unsupported planar configuration Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20017 Required field number is absent Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20018 Unexpected header found in the specified TIFF image




ALC-PDG-20019 Invalid tiff. Root type and value types differ for some field node.


ALC-PDG-20020 Invalid index. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20021 Invalid type. Cannot convert to int. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20022 Invalid type. Cannot convert to int array.


ALC-PDG-20023 Invalid type. Not an ascii type. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20024 Invalid type. Not a rational type. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-20025 Unsupported frame components. We support only 1 or 3.


ALC-PDG-20026 No Marker Sequence found. Alternate route automatically tried. If cannot obtain output, and LC server running on windows, try using Acrobat conversion route.

ALC-PDG-21501 Unknown runtime error. Review the log files and contact the system administrator. If the problem persists, contact Adobe Technical Support.

ALC-PDG-40001 Host name is not set. Specify the host name.

ALC-PDG-40002 Email user name is not set. Email ID is required to be set for the user.

ALC-PDG-40003 Email address is not set. Email ID is required to be set for the user.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle PDF Generator 3D ES 98

LiveCycle PDF Generator 3D ES

ALC-PDG-40004 SMTP authentication failed. Verify that the SMTP server is responding and proper credentials have been set.

ALC-PDG-40005 provider.email_sendmail_service service is not installed.

Contact the system administrator. SendMail service needs to be installed.



ALC-P3D-1 Conversion failed. Contact the system administrator with error message.

ALC-P3D-2 Conversion failed due to error in number of inputs.

Refer to the PDF Generator 3D ES documentation and pass valid inputs.

ALC-P3D-3 Conversion failed due to error in the customization settings. Please check log file for details.

Refer to the PDF Generator 3D ES documentation for details on settings. For further help, contact Adobe Technical Support.

ALC-P3D-4 Conversion failed due to error with the 3D settings. Please check log file for details.

Refer to the PDF Generator 3D ES documentation for valid settings. For further help, contact Adobe Technical Support.

ALC-P3D-5 Conversion failed due to error in log file.

Contact the system administrator and report the issue to Adobe Technical Support.

ALC-P3D-6 Conversion failed due to error in the A3DReviewer application. Please check log for details.

Contact the system administrator to ensure you can do the conversion using standalone Acrobat on LC server. For further assistance, contact Adobe Technical Support.

ALC-P3D-7 Conversion failed because the input CAD file cannot be found.

Ensure the input file exists and is not corrupt. If the problem persists, contact Adobe Technical Support.

ALC-P3D-8 Conversion failed due to error in creating the A3DReviewer document.

Contact the system administrator and report the issue to Adobe Technical Support.

ALC-P3D-9 Conversion failed because the A3DReviewer document is empty.

Provide a non-empty document and try the operation again.

ALC-P3D-10 Conversion failed due to error in removing A3DReviewer document.

Stop the A3DReviewer process instance on the LiveCycle ES server and try again. If problem persists, contact Adobe Technical Support.


ALC-P3D-11 Conversion failed due to error during PDF creation. Please check log file for details.

Contact the system administrator and report to Adobe Technical Support.

ALC-P3D-12 Conversion timed out. Increase the conversion time out setting, and try the operation again.

ALC-P3D-13 Conversion failed because A3DReviewer.exe could not be launched.

Contact the system administrator and ensure that the user has sufficient privileges on the application server to launch processes. Also, ensure you can convert documents on the server using standalone Acrobat.

ALC-P3D-14 Conversion failed because PDFG3dAddin.dll could not be loaded.

Ensure you can convert documents on server using standalone Acrobat. Also, verify that the application server user has sufficient privileges.

ALC-P3D-15 Conversion failed due to unsupported input file type.

Use an input file of a supported type.

ALC-P3D-16 Conversion failed due to incompatibility between A3DReviewer.exe and PDFG3dAddin.dll versions.

Try installing Acrobat 3D again. If problem persists, contact Adobe Technical Support.

ALC-P3D-17 Conversion failed because A3DReviewer.exe is in unstable condition.

Manually stop all running instances of A3DReviewer.exe on the server and then try the operation again.

ALC-P3D-100 Conversion failed. Review the log files. Contact the system administrator and report to Adobe Technical Support.

ALC-P3D-101 Conversion failure because of an exception. Message from Exception: {0}

Review the log files. Contact the system administrator and report the issue to Adobe Technical Support.

ALC-P3D-102 You do not have sufficient permissions to perform this operation.

Contact the system administrator for permissions.

ALC-P3D-103 An exception occurred. Review the log files. If the problem persists, contact your system administrator and report the issue to Adobe Technical Support.

ALC-P3D-104 File type not supported. Get a list of supported file types from Adobe Technical Support.

ALC-P3D-105 File name of the supporting document is missing.

Ensure that you provide all required inputs. Refer to the PDF Generator 3D ES documentation for list of required inputs.



ALC-P3D-106 File name of the supporting document is invalid.

Refer to the PDF Generator 3D ES documentation. Ensure that you provide all required inputs.

ALC-P3D-1000 No settings specified. Could not retrieve default settings.

Contact the system administrator and report the issue to Adobe Technical Support. Default settings should have been retrieved.

ALC-P3D-1036 The PDF Generator ES permission(s) have not been initialized

Contact the system administrator. There are problems with the LiveCycle ES installation.

ALC-P3D-1037 The PDF Generator ES resource(s) have not been initialized

Contact the system administrator. There are problems with the LiveCycle ES installation.

ALC-P3D-1001 The input file extension is not supported.

Get the supported file type extensions from Adobe Technical Support.

ALC-P3D-1002 Invalid settings file. Ensure the settings file is not corrupt and conforms to the schema. You can use LiveCycle Administration Console to download a standard settings file.

ALC-P3D-1003 Invalid settings name. Provide the setting name which is present in the database.

ALC-P3D-1004 Input file is not valid. Provide a non-corrupt, valid input file. Refer to the PDF Generator 3D ES documentation for list of supported types.

ALC-P3D-1005 Input file extension is not supported. Obtain the set of supported file types from Adobe Technical Support.

ALC-P3D-1006 Input file extension cannot be determined.

Input file name should contain an extension to determine the file type.

ALC-P3D-1007 No document has been provided for conversion.

Provide the location to the document which needs to be converted.

ALC-P3D-1009 The service to convert the document could not be looked up.

Contact the system administrator. There is an issue with the LiveCycle ES installation.

ALC-P3D-2000 PDF Generator 3D ES service not installed.

Install the PDF Generator 3D ES service.

ALC-P3D-2001 Insufficient permissions to perform this operation.

Obtain the permissions from the system administrator.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Rights Management ES 101

LiveCycle Rights Management ES

ALC-P3D-3000 Invalid setting name given as input. Verify that the setting exists in the database. You can use the LiveCycle Administration Console to view a list of settings stored in the database.

ALC-P3D-3001 Setting {0} doesn't exist. Verify that the specified setting exists in the database.

ALC-P3D-3002 Setting {0} already exists. A setting with the name specified already exists in the database. Provide a unique name for the new setting.

ALC-P3D-3003 Invalid XML given for import. Ensure the XML is valid and conforms to the schema. Contact Adobe Technical Support to obtain the schema.

ALC-P3D-3004 Invalid XML given for upload. Ensure the XML is valid and conforms to the schema. Contact Adobe Technical Support to obtain the schema.

ALC-P3D-3005 None of the settings has been marked as default.

Indicate which setting is the default.

ALC-P3D-3006 No default setting specified. Provide a default setting.

ALC-P3D-3007 The read-only settings named {0} is not present in the XML configuration.

Setting should be present in the XML configuration.

ALC-P3D-3008 The setting {0} specified as default does not exist in the XML configuration provided.


ALC-P3D-3009 Setting name provided in the XML configuration is not valid.


ALC-P3D-3010 Read-only setting name provided in the XML configuration is not valid.


ALC-P3D-3011 The submitted source file is invalid. Submit a valid source file.



1 (0x1) Generic error. Address the issue identified in the Cause section of the log message.

259 (0x103) Operation failed. Address the issue identified in the Cause section of the log message.


513 (0x201) Authentication failed. Address the issue identified in the Cause section of the log message.

514 (0x202) Authentication was canceled by the user. Address the issue identified in the Cause section of the log message.

515 (0x203) Invalid authentication token. The authentication token expired and the user needs to reauthenticate. Can also occur if a cluster is improperly configured and cache invalidation is not occurring or if the token was corrupted or tampered with.


516 (0x204) Client version missing. Generally should not occur. Ensure that unsupported client is not being used.

517 (0x205) Client version mismatch. A server that is incompatible with the client may be in use.


518 (0x206) User account locked. Generally occurs after too many invalid login attempts.


769 (0x301) Document was revoked. Address the issue identified in the Cause section of the log message.

770 (0x302) User does not have permission to view the content. The policy does not grant access to the user.


771 (0x303) User does not have permission to revoke the content. Address the issue identified in the Cause section of the log message.

772 (0x304) User does not have permission to view audit information on the content.


773 (0x305) User does not have permission to view the document because access to it expired.


774 (0x306) A constant indicating that the client has outdated information and must synchronize with the server or open the document while online before opening the document offline.


775 (0x307) Indicates that the request has been denied because the associated permission has not been granted.




776 (0x308) Invalid revocation reason. The provided revocation reason is invalid.


777 (0x309) Must open online before viewing offline. The offline lease has expired, and the document must be opened while online before it can be opened offline; that is, if offline is still granted on the secured document.


1025 (0x401) Failed to connect to server. The client failed to establish a connection with the server.


1026 (0x402) Failed to communicate with server. Indicates an error occurred while communicating with server.


1027 (0x403) Offline synchronization failed. The client failed to complete synchronization with the server for offline access.


1029 (0x405) No offline permission. The user does not have permission to view the content offline.


1030 (0x406) Must synchronize for offline. The user has not performed a recent offline synchronization.


1031 (0x407) Corrupted security information. Security information in a file is corrupted. Could be the result of intentional tampering or simple file corruption.


1032 (0x408) Internal server error. Generally indicates that a database or other internal problem occurred that is not expected to occur.

Examine the server log for more details about the error.

1033 (0x409) Duplicate entry failure. An attempt was made to add a duplicate of a unique entry. For example, a user may have tried to create two policies with the exact same name in the same policy set.


1280 (0x501) Invalid argument. An invalid parameter was provided, generally in an API call.


1282 (0x502) Bad PDRL format. A PDRL policy was provided that does not comply with the schema.

See the server log for more details.

1283 (0x503) Privacy notification refused. The client refused the privacy notification and thus cannot proceed.




1284 (0x504) Invalid policy. The provided policy was invalid. Address the issue identified in the Cause section of the log message.

1285 (0x505) Bad policy setting. An attempt was made to change a policy setting in a way that was not allowed.


1286 (0x506) Document already revoked. A user is attempting to revoke a document that is already revoked.


1287 (0x507) Document already unrevoked. A user is attempting to unrevoke (reinstate) a document that is not revoked.


1288 (0x508) Must Show Privacy Dialog. Should not appear; it is not used externally.

1289 (0x509) No permission for administrator role. An administrator is trying to access functionality that they are not permitted to access. Some end-user functionality, such as the end-user console is not permitted for administrators for security reasons.

Attempt the operation as a non-administrator.

1290 (0x508) No such ID. An ID has been provided that does not exist (for example, a policy or license ID). This may be occur if a system has been rebootstrapped since a document was secured. In that case, the document or license ID no longer exists in the database.


1291 (0x50B) Mismatched policy encryption settings. The policy encryption settings are invalid. For example, trying to switch a policy on a document from one that does encrypt metadata to one that does not encrypt metadata.


1292 (0x50C) No such license ID. The license ID for a document does not exist. This would likely occur if the server had been rebootstrapped since the file was secured.


1293 (0x50D) Attempt to register a hidden user. External users cannot be registered because an administrator deleted or hide them.


1294 (0x50E) Mismatched anonymous settings. A non-anonymous policy has been updated to become anonymous. Not permitted.


1296 (0x510) Not authorized. A request has been denied because the user is not authorized.




1297 (0x511) Invalid policy XML. The XML used to represent a policy is not valid.


1298 (0x512) Invalid license XML. The XML used to represent a license is not valid.


1299 (0x513) Registration disabled. The external user registration service is disabled.

Enable it in the Rights Management ES administration web application.

1300 (0x514) Admin Duplicate Entry. Attempt to insert a value that already exists.


1301 (0x515) Registration blacklist. The user who is trying to be registered belongs to the registration blacklist.


1302 (0x516) Policy switch not allowed. Switching the policy is not permitted.


1303 (0x517) Policy already deleted. A user is attempting to delete a policy that is already deleted.


1304 (0x518) An HTTPS URL is required. Address the issue identified in the Cause section of the log message.

2100 (0x834) Service is disabled. Address the issue identified in the Cause section of the log message.

2101 (0x835) Invalid policy ownership change. An attempt to change the policy owner that is not allowed.


4353 The E_CREATE_DB exception is caused on Solaris 8 for these reasons:

● You have not installed patch 112438-03.

● The /dev/urandom directory does not exist or is not accessible.

Install patch 112438-03 to your Solaris 8 server.



519 (0x207) A particular version of the client was not allowed to connect to the server because the system administrator has configured the server to disallow that version of the client.

Compare the client-supplied application information against Denials settings in the LiveCycle Rights Management ES XML configuration file. Here are some possible actions that might be indicated by this comparison:

● Update the client software to the most recent version

● Determine whether your client software should use a different installation of LiveCycle Rights Management ES

1040 (0x410) An attempt was made to add the same user as a coordinator of a policy set multiple times.

You cannot add a user as a coordinator of a policy set more than once.

1041 (0x411) An attempt was made to add the same user as a document publisher for a policy set multiple times.

You cannot add a user as a document publisher for a policy set if that user is already a document publisher for that policy set.

1305 (0x519) An attempt was made to invoke an API with the maximum requested results set to zero or less.

Ensure that the maximum results requested is greater than zero.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Workbench ES (JBoss) 107

LiveCycle Workbench ES (JBoss)

LiveCycle Workspace ES


DOCS001 When an ALC-PDG document is opened through Workbench ES on JBoss/MySQL turnkey upgrade of LiveCycle 7.x (LiveCycle Workflow and LiveCycle Form Manager), this error level exception is thrown to the server log: [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DocumentManager].[DocumentManagerServlet]] Servlet.service() for servlet DocumentManagerServlet threw exception java.lang.IllegalStateException

No action is required; the PDF will be opened and displayed properly even though the exception is thrown.

When a PDF is opened in Workbench ES, com.adobe.idp.DocumentManagerServlet throws DOCS001: Unexpected exception. ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

ERROR [DocumentManagerServlet] DOCS001:

Occurs when dragging a SWF file to the Variables view.



ALC-WKS-005-000 Server: Authentication failed: bad username or password (username “{0}”).

Verify that the user described by {0} is still valid and examine the any exceptions that precede this error message in the server log.

ALC-WKS-005-001 Server: Authentication error: a problem occurred while authenticating user “{0}” (error {1}).


Verify that the user described in {0} is valid and examine the Cause clause in the error described in {1}

ALC-WKS-005-002 Server: Authentication error: a problem occurred while creating the default queue for user “{0}”.

Ensure the user described by {0} is still valid and examine any exceptions that precede this error message in the server log.

ALC-WKS-005-003 Server: Using connection properties from {0}. Informational text only. No action is required.

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference LiveCycle Workspace ES 108

ALC-WKS-005-004 Server: Using default connection properties (protocol={0} endpoint={2}).

Informational text only. No action is required.

ALC-WKS-005-005 Server: Could not determine the applications server type.

Informational message. Unable to determine if the application server is Websphere, WebLogic, or JBoss.

ALC-WKS-005-006 Server: An error occurred while retrieving the category list.


ALC-WKS-005-007 Server: Incorrect number of parameters supplied to a fill method ({0} provided {1} expected).


ALC-WKS-005-008 Server: Security exception: the user specified in the fill parameters (oid={0}) did not match the authenticated user (oid={1}).


ALC-WKS-005-009 Server: An error occurred retrieving endpoints for category {0}.


ALC-WKS-005-010 Server: The {0} config property was not set. You must perform the bootstrapping step before using this product.


ALC-WKS-005-011 Server: The copy buffer size (configured in the {0} config property, numeric value is {1}) was not greater than zero.


ALC-WKS-005-012 Server: The requested resource {0} was not found in the repository; HTTP error 404 returned.


ALC-WKS-005-013 Server: The requested resource {0} successfully returned (content type was {1}).


ALC-WKS-005-014 Server: An error occurred while retrieving preferences for user {0}.


ALC-WKS-005-015 Server: An error occurred while updating preferences for user {0}.


ALC-WKS-005-016 Server: An error occurred while retrieving properties for user {0}.




ALC-WKS-005-017 Server: An error occurred while updating properties for user {0} (property {1}).


ALC-WKS-005-018 Server: The content type for the document was unknown.


ALC-WKS-005-019 Server: An error occurred while retrieving favorites for user {0}.


ALC-WKS-005-020 Server: An error occurred while adding favorites for user {0}.


ALC-WKS-005-021 Server: An error occurred while deleting favorites for user {0}.


ALC-WKS-005-022 Server: Failed to forward task {0} to {1}. Address the issue identified in the Cause section of the log message.

ALC-WKS-005-023 Server: Failed to consult task {0} to {1}. Address the issue identified in the Cause section of the log message.

ALC-WKS-005-024 Server: Failed to share task {0} to {1}. Address the issue identified in the Cause section of the log message.

ALC-WKS-005-025 Server: Task {0} could not be located. Events may not propagate correctly to the next user.


ALC-WKS-005-026 Server: Access denied: access permission not assigned to user {0}.


ALC-WKS-005-027 Server: An error occurred while attempting to verify permission for user {0}.


ALC-WKS-005-028 Server: A problem occurred in the Render service. Review the render orchestration for this process.


ALC-WKS-005-029 Server: A problem occurred in the Submit service. Review the submit orchestration for this process.


ALC-WKS-005-030 Server: An error occurred while searching for users with a common name {0}.




ALC-WKS-005-031 Server: An error occurred while getting form data for task {0}.


ALC-WKS-005-032 Server: An error occurred while retrieving attachments and notes for task {0}.


ALC-WKS-005-033 Server: A problem occurred while trying to set the task visibility for task {0}.


ALC-WKS-005-034 Server: A problem occurred while trying to claim task {0}.


ALC-WKS-005-037 Server: A problem occurred while trying to reject task {0}.


ALC-WKS-005-038 Server: Task manager callRenderService failed to produce a document for task {0}.


ALC-WKS-005-039 Server: A problem occurred while retrieving additional information about task {0}.


ALC-WKS-005-040 Server: A problem occurred while trying to retrieve the members in group id {0, form {1}).


ALC-WKS-005-041 Server: A problem occurred while trying to retrieve the members in group id {0} with the name {1}, form {1}).


ALC-WKS-005-042 Server: A problem occurred while trying to retrieve the name of the group for id {0}, form {1}).


ALC-WKS-005-043 Server: An error occurred while searching for groups with a common name of {0}, form {1}).


ALC-WKS-005-044 Server: A problem occurred while trying to abandon task {0}.


ALC-WKS-005-045 Server: A problem occurred while trying to share queueid {0} with userid {1}.


ALC-WKS-005-046 Server: A problem while occurred trying to unshare queueid {0} with userid {1}.




ALC-WKS-005-047 Server: A problem occurred while invoking the Queue Sharing process on behalf of {0}.


ALC-WKS-005-048 Server: An error occurred while adding an attachment.


ALC-WKS-005-049 Server: An error occurred while adding a note titled {0}.


ALC-WKS-005-050 Server: An error occurred while retrieving an attachment or note for task {0}.


ALC-WKS-005-051 Server: An error occurred while updating a note titled {0}.


ALC-WKS-005-052 Server: An error occurred while deleting attachment {0}.


ALC-WKS-005-053 Server: An error occurred while deleting a note titled {0}.


ALC-WKS-005-054 Server: An error occurred while retrieving process variables for process {0}.


ALC-WKS-005-055 Server: An error occurred while retrieving endpoints based on a collection of endpoint IDs


ALC-WKS-005-056 Server: An error occurred while retrieving active process list for user with userid {0}.


ALC-WKS-005-057 Server: An error occurred while searching for groups with a common name of {0}.


ALC-WKS-005-058 Server: An error occurred while retrieving the list of processes from the TypeTaskManagerQueryService.


ALC-WKS-005-059 Server: An error occurred while retrieving the list of process instances for process {0}.


ALC-WKS-005-060 Server: An error occurred while retrieving the list of tasks for process instance with id {0}.




ALC-WKS-005-061 Server: An error occurred while retrieving the list of active tasks for process instance with id {0}.


ALC-WKS-005-062 Server: An error occurred while retrieving the list of assignments for task with id {0}.


ALC-WKS-005-063 Server: No form data-mapping found when rendering the form for task with id {0}. Review your orchestration.


ALC-WKS-005-064 Server: Single sign-on (SSO) failed. Address the issue identified in the Cause section of the log message.

ALC-WKS-005-065 Server: Single sign-on failed. Address the issue identified in the Cause section of the log message.

ALC-WKS-005-066 Server: An error occurred while creating a calendar named {0}.


ALC-WKS-005-067 Server: An error occurred while updating a calendar named {0}.


ALC-WKS-005-068 Server: An error occurred while deleting a calendar named {0}.


ALC-WKS-005-069 Server: An error occurred while getting all calendars.

Examine the exceptions that immediately precede this error message in the server log.

ALC-WKS-005-070 Server: An error occurred while getting all calendar names.


ALC-WKS-005-071 Server: An error occurred while getting a calendar named {0}.


ALC-WKS-005-072 Server: An error occurred while getting the default calendar.




ALC-WKS-005-073 Server: An error occurred while setting the default calendar.


ALC-WKS-005-074 Server: An error occurred while getting the list of unique user keys.


ALC-WKS-005-075 Server: An error occurred while importing calendars.


ALC-WKS-005-076 Server: An error occurred while extracting calendars.


ALC-WKS-005-077 Server: An error occurred while exporting calendars.


ALC-WKS-005-078 Server: An error occurred while getting the list of task notification templates.


ALC-WKS-005-079 Server: An error occurred while saving the list of task notification templates.


ALC-WKS-005-080 Server: An error occurred while getting the list of administrative notification templates.


ALC-WKS-005-081 Server: An error occurred while saving the list of administrative notification templates


ALC-WKS-005-082 Server: An error occurred while retrieving the out-of-office settings for user {0}.

Ensure that the user identified in {0} is valid, and review the server logs for a more detailed message.



ALC-WKS-005-083 Server: An error occurred while saving the out-of-office settings for user {0}.

Ensure that the user identified in {0} is valid, and review the server logs for a more detailed message.

ALC-WKS-005-084 Server: An error occurred while importing and parsing a business calendar file.


ALC-WKS-005-085 Server: An error occurred while importing and transforming a business calendar file.


ALC-WKS-005-086 Server: An error occurred while retrieving a list of business calendar mappings.


ALC-WKS-005-087 Server: An error occurred while updating business calendar mappings.


ALC-WKS-005-088 Server: An error occurred while retrieving the resolution type for business calendar mappings.


ALC-WKS-005-089 Server: An error occurred while updating the resolution type for business calendar mappings.


ALC-WKS-005-090 Server: An error occurred while trying to re-initiate a new Task from Task "{0}".


ALC-WKS-005-091 Server: The associated process is no longer available. You are unable to re-initiate a new Task from the selected Task "{0}".


ALC-WKS-005-092 Server: A problem occurred when calling the submit service to perform a server-side calculate. The task id could not be found.


ALC-WKS-005-093 Server: A problem occurred when calling the submit service to perform a server-side calculate.




ALC-WKS-005-094 Server: An error occurred changing the description for task with id "{0}".


ALC-WKS-005-095 Server: Using the server locale [{0}] because the Accept-Language header was not set.

The browser did not send an Accept-Language header, so the server locale was used by default.

ALC-WKS-007-000 Client: An error occurred during the operation.

This error occurs when the login operation fails.

Examine the corresponding server log file.

ALC-WKS-007-001 Client: Invalid user name or password. Informational text only. No action is required.

ALC-WKS-007-007 Client: Endpoint with endpoint ID {0} is not found. Examine the log for the server error message which caused the problem retrieving the endpoint with the specified ID.

ALC-WKS-007-008 Client: Task with a task id of {0} was not found. Examine the log for the server error message which caused the problem retrieving the task with the specified taskID.

ALC-WKS-007-010 Client: You have uploaded attachment {0}. Informational text only. No action is required.

ALC-WKS-007-011 Client: An error occurred while uploading attachment {0}.

Examine the log for the server error message which caused the problem uploading the attachment.

ALC-WKS-007-012 Client: You have added the note titled {0}. Informational text only. No action is required.

ALC-WKS-007-013 Client: An error occurred adding a note titled {0}. Examine the log for the server error message which caused the problem adding the note.

ALC-WKS-007-017 Client: A communication error occurred during the operation: {0}.

Examine the log for the server error message which caused the problem with the connection. It is likely that the exception occurred as a result of the channel being disconnected.



ALC-WKS-007-019 Client: Your attempt to consult task {0} failed. Examine the log for the server error message which caused the problem with consulting for the task with this taskID.

ALC-WKS-007-020 Client: Your attempt to share task {0} failed. Examine the log for the server error message which caused the problem with consulting for the task with this taskID.

ALC-WKS-007-021 Client: Your attempt to forward task {0} failed. Review the server log file for more detailed information.

ALC-WKS-007-022 Client: Are you sure you want to leave this form? You may have unsaved changes.


ALC-WKS-007-023 Client: Review highlighted form input fields for errors.


ALC-WKS-007-025 Client: An error occurred while retrieving information from the server.

An error has occurred with the Workspace Data Services fill operation. Examine the log for the server error message which caused the client to receive this error.

ALC-WKS-007-026 Client: An error occurred during logout. Your session to the server may still be valid.

Examine the log for the server error message which caused the problem with log out.

ALC-WKS-007-027 Client: An error occurred during the operation (endpoint ID {0}).

Examine the log for the server error message which caused the problem invoking the endpoint.

ALC-WKS-007-030 Client: An error occurred while retrieving categories.

Examine the log for the server error message which caused the problem with the data services fill operation for categories.

ALC-WKS-007-032 Client: An error occurred while retrieving tasks. Examine the log for the server error message which caused the problem with the data services fill operation for tasks.



ALC-WKS-007-033 Client: An error occurred while retrieving queues. Examine the log for the server error message which caused the problem with the data services fill operation for queues.

ALC-WKS-007-034 Client: An error occurred while retrieving search templates.

Examine the log for the server error message which caused the problem with the data services fill operation for search templates.

ALC-WKS-007-035 Client: An error occurred while retrieving users. Examine the log for the server error message which caused the problem with the data services fill operation for retrieving users.

ALC-WKS-007-037 Client: An error occurred while retrieving attachments and notes.

Examine the log for the server error message which caused the problem with the data services fill operation for attachments.

ALC-WKS-007-039 Client: An error occurred during the search. Examine the log for the server error message which caused the client to receive this error.

ALC-WKS-007-040 Client: An error occurred while creating the form (task {0}.

Examine the log for the server error message to indicate if there are any problems with the render service.

ALC-WKS-007-041 Client: An error occurred while retrieving form data (task {0}.

Examine the log for the server error message. This error is typically seen when using flex forms.

ALC-WKS-007-042 Client: An error occurred while saving form data (task {0}.

Examine the log for the server error message. It is likely that this error would occur when a user is saving draft data.



ALC-WKS-007-043 Client: An error occurred while submitting the form (task {0}.

Examine the server log to provide info as to why the submit service failed. Verify whether the LiveCycle ES server is running.

ALC-WKS-007-044 Client: An error occurred while retrieving process instances (process {0}).

Examine the log for the server error message which caused the client to receive this error.

ALC-WKS-007-045 Client: An error occurred while retrieving a search template (id {0}).

Examine the log for the server error message. Also verify the adminui where the search template is defined.

ALC-WKS-007-046 Client: An error occurred while saving preference changes to the server.

Examine the server log to provide info as to why the submit service failed. Check if LiveCycle server is running.

ALC-WKS-007-049 Client: An error occurred while initializing Workspace ES.

Examine the log for the server error message.

ALC-WKS-007-050 Client: A communication error occurred while adding an attachment (task {0}): {1}.

Check whether the file still exists on the file system.

ALC-WKS-007-051 Client: A security error occurred while adding an attachment (task {0}): {1}.

Check the security permissions of the file you are trying to upload.

ALC-WKS-007-052 Client: An error occurred while adding a note titled {0}.


ALC-WKS-007-053 Client: An error occurred while retrieving processes. Examine the log for the server error message which caused the client to receive this error.

ALC-WKS-007-054 Client: An error occurred while retrieving tasks for process instance (process instance {0}).


ALC-WKS-007-055 Client: An error occurred while retrieving the assignments for task (task {0}).




ALC-WKS-007-056 Client: An error occurred while deleting attachment or note for task {0}.

Examine the log for the server error message. Server permissions may have changed.

ALC-WKS-007-057 Client: You have deleted attachment {0}. Informational text only. No action is required.

ALC-WKS-007-060 Client: You deleted the note titled ‘{0}’. Informational text only. No action is required.

ALC-WKS-007-061 Client: An error occurred while deleting a note titled {0}.

Typically this is an Informational message only. No action should be required. If the issue persists, examine the log file and verify that there are no permission errors.

ALC-WKS-007-062 Client: An error occurred while retrieving attachment document {0}.


ALC-WKS-007-063 Client: A communication error occurred while downloading attachment {0}.


ALC-WKS-007-064 Client: A security error occurred while downloading attachment {0}.


ALC-WKS-007-065 Client: You have saved attachment ‘{0}’. Chances are the user doesn't have access to the attachment, or possibly the document is no longer available.

ALC-WKS-007-068 Client: A security error occurred while updating an attachment (task {0}): {1}


ALC-WKS-007-069 Client: Your attempt to remove task {0} from your To Do list failed.

Verify that the log does not contain any permission errors for the Task. It is possible that the user does not have access to the Task.



ALC-WKS-007-070 Client: You successfully removed task {0} from your To Do list.

Verify that your server connection is still valid. The request to update the attachment is trying to connect to a servlet to perform the POST with the new data. The servlet name is "update-task-attachment".

ALC-WKS-007-071 Client: You have submitted task {0}. If you don't have permission to update the attachment, a security error is thrown from the servlet. Examine the log and see if the user doesn't have access to the Task or its attachments.

ALC-WKS-007-072 Client: Task {0} failed to submit. Informational text only. No action is required.

ALC-WKS-007-073 Client: You have completed task {0}. Informational text only. No action is required.

ALC-WKS-007-074 Client: An error occurred while submitting the form.


ALC-WKS-007-075 Client: The attempt to claim task {0} failed. Examine the server log file and see exactly why the cause of the error was thrown.

ALC-WKS-007-076 Client: You have claimed task {0}. Informational text only. No action is required.

ALC-WKS-007-077 Client: You have added {0} to favorites. Examine the logs and see if there was issues within the submit service.

ALC-WKS-007-078 Client: You have removed {0} from favorites. Ensure that Task has not been locked and that you are able to claim it.

ALC-WKS-007-079 Client: An error occurred while retrieving an extended note titled {0}.


ALC-WKS-007-080 Client: An error occurred while trying to unlock task {0}.


ALC-WKS-007-081 Client: You have released task {0}. Informational text only. No action is required.



ALC-WKS-007-082 Client: An error occurred while trying to lock task {0}.

Examine the log for the server error message which caused the client to receive this error. This operation is executed via a Data Service call, verify that the server is still communicating with the client.

ALC-WKS-007-083 Client: You have locked task {0}. Ensure that the task is still available. Review the server log file for a more detailed error message.

ALC-WKS-007-084 Client: An error occurred while trying to return task {0}.


ALC-WKS-007-085 Client: You have returned task {0}. Ensure that you can still access the Task, and that the task is still active to lock.

ALC-WKS-007-086 Client: The list view type {0} is not valid. Informational text only. No action is required.

ALC-WKS-007-087 Client: You have approved task {0}. Informational text only. No action is required.

ALC-WKS-007-088 Client: Approving task {0} failed. Informational text only. No action is required.

ALC-WKS-007-094 Client: At least one item must be selected. Ensure the group id is valid. Review the server log for a more detailed message.

ALC-WKS-007-095 Client: A layout name must be provided. Ensure the group id is valid. Review the server log for a more detailed message.

ALC-WKS-007-096 Client: An error occurred while retrieving process variables for process {0}.


ALC-WKS-007-097 Client: List view layout {0} has been created. Before the operation can complete an item must be selected to act upon.

ALC-WKS-007-098 Client: List view layout {0} has been updated. This message should be removed.



ALC-WKS-007-099 Client: List view layout must have at least one item selected.

Verify that the process is still active. If so, verify that the server is still active and review the server logs for a more detailed message

ALC-WKS-007-100 Client: You saved task {0} to Drafts in the To Do view.


ALC-WKS-007-101 Client: An error occurred while saving task {0} to Drafts.


ALC-WKS-007-103 Client: You have abandoned task {0}. Informational text only. No action is required.

ALC-WKS-007-104 Client: An error occurred while retrieving process variables for task {0}.

Verify that the server is still active and review the server logs for a more detailed message.

ALC-WKS-007-105 Client: An error occurred while trying to obtain the tasks for process id {0}.

Verify that the server is still active and review the server logs for a more detailed message.

ALC-WKS-007-106 Client: An error occurred while trying to obtain the assignments for task {0}.


ALC-WKS-007-107 Client: List view layout {0} has been deleted. Verify that the process is still active. If so, verify that the server is still active and review the server logs for a more detailed message.

ALC-WKS-007-110 Client: The form associated with task {0} has no submit buttons and cannot be submitted.


ALC-WKS-007-111 Client: You have updated attachment ‘{0}’. Informational text. User must login again to continue

ALC-WKS-007-112 Client: An error occurred while updating attachment {0}.

Informational text. Follow instructions.

ALC-WKS-007-113 Client: Task {0} is added to the {1} queue. Informational text only. No action is required.

ALC-WKS-007-114 Client: An error occurred while either sending data to or receiving data from the server.


ALC-WKS-007-115 Client: Queue access for {0} has been granted. Ensure the server is still active and review the server logs for a more detailed message.



ALC-WKS-007-116 Client: Queue access for {0} has been revoked. Informational text only. No action is required.

ALC-WKS-007-117 Client: An error occurred while modifying access to your queue for user {0}.

Ensure the server is still active and check the server logs for a more detailed message

ALC-WKS-007-118 Client: Queue access for {0} has been requested. Informational text only. No action is required.

ALC-WKS-007-119 Client: Queue access to {0} has been removed. Informational text only. No action is required.

ALC-WKS-007-120 Client: An error occurred retrieving endpoints from a list of endpoint IDS.

Verify that both the server and the user are still valid. Review the server logs for a more detailed message.

ALC-WKS-007-121 Client: An error occurred while retrieving group information.


ALC-WKS-007-122 Client: An error occurred while removing your access to user {0}’s queue.


ALC-WKS-007-123 Client: An error occurred while revoking user {0}’s access to your queue.

Ensure that the user is valid, and ensure that the server is still active. Review the server logs for a more detailed message.

ALC-WKS-007-124 Client: An error occurred while requesting your access to user {0}’s queue.


ALC-WKS-007-125 Client: A specified condition is missing a value. Ensure the server is still active, and review the server logs for a more detailed message.

ALC-WKS-007-126 Client: An error occurred while retrieving email settings for user {0}.


ALC-WKS-007-127 Client: An error occurred while trying to retrieve the out of office settings.




ALC-WKS-007-128 Client: An error occurred while trying to save the out of office settings.

Informational text only. Ensure that all conditions defined in the query have an associated value.

ALC-WKS-007-129 Client: An error occurred while importing business calendar: {0}.

Verify that the user has rights to import business calendars. Ensure that the server is still active. Review the server logs for a more detailed message.

ALC-WKS-007-130 Client: An security error occurred while importing business calendar: {0}.

Verify that the user has rights to import business calendars. Ensure that the server is still active. Review the server logs for a more detailed message.

ALC-WKS-007-131 Client: An error occurred while importing business calendar: {0}.

Ensure the server is still active, and review the server logs for a more detailed message.

ALC-WKS-007-132 Client: An error occurred while importing business calendar, bad file name: {0}.


ALC-WKS-007-133 Client: An error occurred while importing business calendar: file is invalid.

Ensure that the user has has rights to import business calendars. Ensure the server is still active and review the server logs for a more detailed message.

ALC-WKS-007-134 Client: Business calendars successfully exported to: {0}.


ALC-WKS-007-135 Client: Business calendars successfully imported from: {0}.

Correct the file name described by {0} and try again.

ALC-WKS-007-136 Client: An error occurred while attempting to get the default business calendar: {0}.

Inspect the business calendar import file that you are trying to import to ensure that its valid. Check the server logs for a more detailed message.



ALC-WKS-007-137 Client: An error occurred while attempting to set the default business calendar: {0}.


ALC-WKS-007-138 Client: An error occurred while attempting to get a business calendar: {0}.


ALC-WKS-007-139 Client: An error occurred while attempting to get all the business calendars: {0}.


ALC-WKS-007-140 Client: An error occurred while attempting to get the business calendar names: {0}.


ALC-WKS-007-141 Client: An error occurred while attempting to update a business calendar: {0}.


ALC-WKS-007-142 Client: An error occurred while trying to call the data service task.getItem call.


ALC-WKS-007-143 Client: An error occurred while trying to get business calendar mappings.


ALC-WKS-007-144 Client: An error occurred while trying to update business calendar mappings.


ALC-WKS-007-145 Client: An error occurred while trying to get list of unique user keys for business calendars.



Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference Web Services 126

Web Services

JBoss


log4j:WARN When running tests by using the Axis WSDL2Java method described in the “Invoking LiveCycle ES Using Web Services” section of LiveCycle ES SDK Help, a warning is presented regarding the logger:

log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle). log4j:WARN Please initialize the log4j system properly.

These errors occur on JBoss, WebSphere, and WebLogic and can be ignored.


WARN [org.jboss.deployment.MainDeployer] Found non-jar deployer

Caused by certain LiveCycle ES JAR files being listed in the class path of the MANIFEST.MF file.

Exception does not affect the LiveCycle ES server processing and can be ignored.

http://www.adobe.com/go/learn_lc_programming_82

Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference JBoss 127

09:03:54,843 ERROR [UNICAST]

The following errors occur on startup of JBoss in a cluster:

09:03:54,843 ERROR [UNICAST] window_size is deprecated and will be ignored; 09:03:54,843 ERROR [UNICAST] min_threshold is deprecated and will be ignored.

Exception does not affect the LiveCycle ES server processing and can be ignored.

errorCode:8193 errorCodeHEX:0x2001

This error is seen on JBoss startup when the quartz.jar version has not been updated correctly:

initialize chainedException:java.lang.IllegalArgumentException: Job class must implement the Job interface.chainedExceptionMessage:Job class must implement the Job interface. chainedException trace:java.lang.IllegalArgumentException: Job class must implement the Job interface.at org.quartz.JobDetail.setJobClass(JobDetail.java:262)at org.quartz.JobDetail.<init>(JobDetail.java:139)at com.adobe.idp.um.util.UMSchedulerUtil.initialize(UMSchedulerUtil.java:254)at com.adobe.idp.um.scheduler.IDPScheduler.initializeScheduler(IDPScheduler.java:101)at com.adobe.idp.um.scheduler.IDPScheduler.onStartService(IDPScheduler.java:70)at com.adobe.service.Service.start(Service.java:145)

Please see the JBoss guide and ensure that "quartz.jar" and "commons-collections.jar" have been updated properly in your JBoss environment.


Adobe LiveCycle ES Error Code ReferenceLiveCycle ES Error Code Reference MySQL 128

MySQL


java.net.SocketException MESSAGE: Software caused connection abort: socket write error

Extended periods of server inactivity when using JBoss Application Server configured with MySQL (the JBoss turnkey). Exception is raised by background processing during internal database management. Its presence is expected: Idle connection with the database times out and causes the TCP/IP connection to close. Exceptions typically occur after 8 hours or more of inactivity in LiveCycle ES.

[Exceptions seen on JBoss/MySQL and start with: java.sql.SQLException: No operations allowed after connection closed. Connection was implicitly closed due to underlying exception/error: ** BEGIN NESTED EXCEPTION **com.mysql.jdbc.CommunicationsException MESSAGE: Communications link failure due to underlying exception: **java.net.SocketException MESSAGE: Software]

This exception does not impact the LiveCycle ES server processing and can be ignored.

129

3 Error Code Reference for Upgrading LiveCycle ES

The error messages in this section are displayed when errors occur during the upgrade process. The error code tables also provide the causes of the error codes and the actions to take. This section will be updated regularly to incorporate new and changed information about how to handle error conditions.

Upgrade errors are available for the following applications, services, and solution components:

● “Upgrading the LiveCycle ES server” on page 130

● “Upgrading repository” on page 133

● “Upgrading LiveCycle Barcoded Forms” on page 136

● “Upgrading LiveCycle Workflow” on page 136

● “Upgrading LiveCycle Workflow 7.2.2 to LiveCycle ES on JBoss/MySQL” on page 138

● “Upgrading LiveCycle PDF Generator” on page 139

● “Upgrading LiveCycle Policy Server” on page 141

● “Upgrading LiveCycle Form Manager” on page 141

● “Upgrading LiveCycle Forms” on page 145

● “Upgrading LiveCycle Print” on page 146

● “Upgrading core components” on page 147

● “Upgrading Font Manager Module” on page 150

● “Upgrading Trust Manager Module” on page 151

● “Upgrading LiveCycle Assembler” on page 156

● “Upgrading LiveCycle Assembler” on page 156

● “Upgrading LiveCycle Document Security” on page 157

● “Upgrading watched folders” on page 159

● “Upgrading Content Repository Connector for EMC Documentum” on page 161

● “Upgrading Content Repository Connector for IBM FileNet” on page 162

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading the LiveCycle ES server 130

Upgrading the LiveCycle ES server


ALC-UPG-001-000 An error occurred: [error description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-001 NamingException: [error description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-002 JmsException: [error description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-003 ClassNotFoundException: [error description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-004 Assembly scripts directory not found: [error description].


ALC-UPG-001-005 Failed to clean working directory: [error description].


ALC-UPG-001-006 Failed to merge one of the compatibility EAR files into [EAR to be merged]: [target EAR].


ALC-UPG-001-007 Failed to parse application.xml of {0}: {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-008 Failed to extract application.xml from {0}: {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-009 Failed to copy [original] to [target]; reason: [description].


ALC-UPG-001-010 Failed to create DocumentBuilder: [description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-011 Database driver not found: [description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-012 Failed to obtain the Install folder for MySQL 4.1. Address the issue identified in the Cause section of the log message.


ALC-UPG-001-013 Failed to obtain the install folder for MySQL 5.0. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-014 Failed to back up the LiveCycle 7.x database: [description].


ALC-UPG-001-015 Failed to restore the Live Cycle 7.x data to the LiveCycle ES database: [description].


ALC-UPG-001-016 Failed to get the database authentication parameters for [databaseName] database.


ALC-UPG-001-017 Failed to retrieve LiveCycle 7.x database character set.


ALC-UPG-001-018 Failed to retrieve LiveCycle ES database character set.


ALC-UPG-001-019 Warning: Failed to set the MySQL 4.1 service start mode to [startModeValue].


ALC-UPG-001-020 Warning: Failed to stop MySQL 4.1 service. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-021 Failed to get working directory. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-501 Executing [pluginName] plug-in. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-502 [pluginName] plug-in execution completed successfully.


ALC-UPG-001-503 [pluginName] plug-in execution failed; error message from plug-in is [message].


ALC-UPG-001-504 Added [{0}] to compatibility EAR files merge list. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-506 Cleaning directory [directoryName]. Address the issue identified in the Cause section of the log message.



ALC-UPG-001-507 Creating directory [directoryName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-508 Copying [directoryName] to working directory. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-509 Merging {0} compatibility EAR files into {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-510 LCM override enabled. LCM will merge compatible EAR files.

Set [{0}] to false to remove override.

ALC-UPG-001-511 Copying {0} to {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-512 Extracting values of display name and description elements from application.xml.


ALC-UPG-001-513 Value of element <display-name> is [value]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-514 Value of element <description> is [value]. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-515 Warning: Step [stepName] completed successfully but returned incomplete progress value of [percentage].


ALC-UPG-001-516 Deploy service components: {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-517 Warning: Character sets do not match. Character set for LiveCycle 7.x database is [nameOfSet]. Character set for LiveCycle ES database is [nameOfSet].


ALC-UPG-001-518 Initializing. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-519 Backing up LiveCycle 7.x database. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-520 Reconfiguring the MySQL 4.1 service to start manually.



Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading repository 133

Upgrading repository

ALC-UPG-001-521 Stopping the MySQL 4.1 service. Address the issue identified in the Cause section of the log message.

ALC-UPG-001-522 Restoring LiveCycle 7.x data to the LiveCycle ES database.


ALC-UPG-001-523 MySQL upgrade task complete. Address the issue identified in the Cause section of the log message.



ALC-UPG-020-000 Internal error: [description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-001 Initialization failed: [description]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-002 Failed to find ObjectRef of AccessControlPolicyFor ClassificationNode.


ALC-UPG-020-003 Caught POFException: [exceptionName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-004 [number] policy associations are on object [urn:{1}]. Expected only one.


ALC-UPG-020-006 Caught UMException: [exceptionName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-007 No policy content found for policy [policyName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-008 Error translating registry permission: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-009 {0} Address the issue identified in the Cause section of the log message.


ALC-UPG-020-501 Skipping bootstrapped object with ID [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-502 Objects processed: {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-503 Registry migration complete. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-504 Processing [{0}], name=[{3}], id=[{2}], objectType=[{1}].


ALC-UPG-020-505 Folder [folderName] has already been migrated. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-506 No transaction to commit. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-507 No transaction to roll back. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-508 File [fileName] is already migrated. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-509 Not migrating ClassificationNode object [{0}] because its classification path [{1}] is null or not under the Appstore classification path [{2}]].


ALC-UPG-020-510 Translating access control policy with ID[{0}] for resource with ID[{1}].


ALC-UPG-020-511 Propagating access control policy with ID [{0}] for resource with ID[{1}].


ALC-UPG-020-512 Using default access control policy for resource with ID [{0}].


ALC-UPG-020-513 Number of objects to migrate: [value]. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-514 Number of objects already migrated: [value]. Address the issue identified in the Cause section of the log message.



ALC-UPG-020-515 Size of ObjectType Id to OID map: {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-516 Number of default objects that do not need to be migrated: {0}.


ALC-UPG-020-517 Null parent path found for resource ID [{0}]. Skipping resource.


ALC-UPG-020-518 Creating a new version at path [{1}] using object ID [{0}].


ALC-UPG-020-519 Invalid content (null content) detected for ebXML repository item ID=[{0}]. Skipping.


ALC-UPG-020-520 Migrating BLOB: {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-521 Target parent path for next writeResource call: {0}.


ALC-UPG-020-522 Current ClassificationNode.name: {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-523 Current ClassificationNode.path: {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-020-524 Converted ClassificationNode.path (Repository path): {0}.


ALC-UPG-020-525 The repository upgrade plug-in did not detect the presence of LiveCycle Form Manager 7.x tables in the LiveCycle ES database.



Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Barcoded Forms 136

Upgrading LiveCycle Barcoded Forms

Upgrading LiveCycle Workflow


ALC-UPG-030-001 Failed to redeploy the LiveCycle Barcoded Forms Decoder Agent QPAC.


ALC-UPG-030-002 Caught IOException; message is [errorMessage]. Address the issue identified in the Cause section of the log message.


ALC-UPG-040-000 Internal error: {0} Address the issue identified in the Cause section of the log message.

ALC-UPG-040-001 Initialization failed: {0} Address the issue identified in the Cause section of the log message.

ALC-UPG-040-002 Caught ServiceRegistryException: [errorMessage].


ALC-UPG-040-003 Caught POFException: [errorMessage]. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-004 Exception Migrating Workflow Templates: [errorMessage].


ALC-UPG-040-005 Exception Migrating Workflow Tasks: [errorMessage].


ALC-UPG-040-006 Caught Raw SQL Exception: [errorMessage]. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-007 User Transaction Already Active: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-008 IO Exception: [errorMessage]. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-009 User Manager Exception processing roles: [errorMessage].


Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Workflow 137

ALC-UPG-040-010 Repository Exception processing LiveCycle 7.x init-form {0}.


ALC-UPG-040-011 Registry Exception processing LiveCycle 7.x init-form{0}.


ALC-UPG-040-012 Parser Exception processing LiveCycle 7.x init-form {0}.


ALC-UPG-040-013 SAX Exception processing LiveCycle 7.x init-form {0}.


ALC-UPG-040-014 Exception processing LiveCycle 7.x init-form {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-501 Migrating: {0} Process Categories. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-502 Service Category: {0} created. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-503 Migrating: {0} Process Types. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-504 Creating: {0} Service. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-505 Service: {0} Created. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-506 Migration completed successfully. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-507 Service configuration exists {0}, skipping creation.


ALC-UPG-040-508 No transaction to commit. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-509 No transaction to roll back. Address the issue identified in the Cause section of the log message.


Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Workflow 7.2.2 to LiveCycle ES on JBoss/MySQL 138

Upgrading LiveCycle Workflow 7.2.2 to LiveCycle ES on JBoss/MySQL

ALC-UPG-040-510 Migrating: {0} Tasks. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-511 Migrating: Task {0} of {1} Tasks. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-512 Updating User: {0} with Role: {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-040-513 LiveCycle 7.x Render and Submit LCA imported, status: {0}.




errorCode:12290 This exception is written to server logs during upgrade of LiveCycle Workflow 7.x:

WARN [com.adobe.idp.common.errors.exception.IDPLoggedException] UserM:GENERIC_WARNING: [Thread Hashcode: 33001201] | [com.adobe.idp.storeprovider.jdbc.DBConnection] errorCode:12290 errorCodeHEX:0x3002 message:commit failure chainedException:java.sql.SQLException: You cannot commit during a managed transaction!chainedExceptionMessage:You cannot commit during a managed transaction! chainedException trace:java.sql.SQLException: You cannot commit during a managed transaction!

You can ignore this error.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle PDF Generator 139

Upgrading LiveCycle PDF Generator


ALC-UPG-050-001 Login information provided for LiveCycle ES may be wrong.

Verify user name and password used.

ALC-UPG-050-002 Failed to create endpoint [endpointName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-003 Problem updating {0} parameters for [endpointName] endpoint.


ALC-UPG-050-004 Failed to change [componentName] configuration properties.


ALC-UPG-050-005 Failed to update preferences for PDF Generator ES. New settings will not be implemented.


ALC-UPG-050-006 Failed to fetch preferences for PDF Generator ES. Failed to migrate old settings.


ALC-UPG-050-007 File [fileName] could not be found. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-008 Exception while updating compatibility layer properties [propertyName].


ALC-UPG-050-009 Failed to rename file [fileName]. Failed to update [fileName].


ALC-UPG-050-010 Failed to decipher password. {0} Address the issue identified in the Cause section of the log message.

ALC-UPG-050-011 Failed to store passkey to new database. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-012 Failed to inject [fileName1] into [fileName2]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-013 Failed to delete [name]. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle PDF Generator 140

ALC-UPG-050-014 Exception occurred while checking for presence of new configuration.


ALC-UPG-050-015 Exception occurred while migrating filetype settings.


ALC-UPG-050-016 Problem in deploying and starting workflow [workflowName].


ALC-UPG-050-017 Problem while reading workflow file [fileName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-021 Task initiated for {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-022 Task completed for {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-023 Task failed while {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-024 Creating temporary directory for PDF Generator ES upgrade at [location].


ALC-UPG-050-025 Failure occurred at step [stepNumber]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-026 Copying file from [directoryName1] to [directoryName2].


ALC-UPG-050-027 Updating {0} from {1} to {2}. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-028 Loading PDF Generator ES configuration from {0}.


ALC-UPG-050-029 Storing PDF Generator ES configuration to {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-030 Connecting to {0} to fetch configuration. Address the issue identified in the Cause section of the log message.


Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Policy Server 141

Upgrading LiveCycle Policy Server

Upgrading LiveCycle Form Manager

ALC-UPG-050-031 Migrating watched folder [name]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-032 Migrating email source [name]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-033 Connecting to {0}:{1}. AppServer : [serverName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-050-034 Endpoint [endpointName] already exists. This endpoint will not be created again.


ALC-UPG-050-035 Checking existence of new configuration. Address the issue identified in the Cause section of the log message.



ALC-UPG-060-001 An unknown error has occurred. Additional details will appear here and/or in the LCM log.




ALC-UPG-070-001 Run-time exception : {0} Address the issue identified in the Cause section of the log message.

ALC-UPG-070-002 Work directory [directoryName] does not exist. LiveCycle Form Manager upgrading cannot be continued.


ALC-UPG-070-003 Failed to locate file [fileName]. LiveCycle Form Manager upgrade cannot be continued.


ALC-UPG-070-004 Failed to create directory [directoryName]. LiveCycle Form Manager upgrade cannot be continued.


Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Form Manager 142

ALC-UPG-070-005 Error occurred when creating an endpoint for init-form {0} with exception: [exceptionName].


ALC-UPG-070-006 Error occurred when creating a favorite in LiveCycle ES for LiveCycle 7.x init-form {0} with exception: [exceptionName].


ALC-UPG-070-007 {0} does not exist and error occurred when creating it.


ALC-UPG-070-008 Error occurred when creating file {0} with exception: {1}.


ALC-UPG-070-009 Error occurred when deleting a preexisting file {0} before copying categories.


ALC-UPG-070-010 No category with UID {0} is found in {1}; therefore, no endpoint can be created for it.


ALC-UPG-070-011 Warning: OID of [{0}] is not found in domain [{1}] when applying ACL to service [{2}] while creating endpoint for init-form [{3}].


ALC-UPG-070-012 Warning: no form name of [{0}] found in repository.


ALC-UPG-070-013 Warning: no category ID of [{0}] found in repository.


ALC-UPG-070-014 Warning: role [{0}] is not found when upgrading Workspace ES roles.


ALC-UPG-070-015 Warning: OID of [{0}] not found in domain [{1}] when upgrading Workspace ES roles.


ALC-UPG-070-016 Warning: UMException thrown when upgrading Workspace ES roles: [{0}].


ALC-UPG-070-017 Warning: assertion fails: {0} != {1} with AssertionError: {2}.


ALC-UPG-070-018 Error occurred when looking for visibility for init-form [{0}] with exception: {1} while creating endpoint for it.




ALC-UPG-070-031 Copying categories.xml for LiveCycle Form Manager is started.


ALC-UPG-070-032 Copying categories.xml for LiveCycle Form Manager is completed.


ALC-UPG-070-033 Migrating critical data for LiveCycle Form Manager.


ALC-UPG-070-034 Migrating critical data for LiveCycle Form Manager is completed.


ALC-UPG-070-035 {0}: Category structure migration is completed. {1} categories in {2} levels are migrated.


ALC-UPG-070-036 {0}: Created an endpoint, ID: {1}, name: {2} for LiveCycle 7.x template {3}.


ALC-UPG-070-037 {0}: Created a favorite endpoint (ID: {1}) for user with ID: {2}.


ALC-UPG-070-038 Creating endpoint for init-form [{0}] is started. Address the issue identified in the Cause section of the log message.

ALC-UPG-070-039 Creating endpoint for init-form [{0}] with categoryID [{1}] of LiveCycle 7.x is completed. The new endpoint is in category [{2}] of LiveCycle ES.


ALC-UPG-070-040 Upgrading role [{0}] for Workspace ES is started. Address the issue identified in the Cause section of the log message.

ALC-UPG-070-041 Upgrading role [{0}] for Workspace ES is completed.


ALC-UPG-070-042 Creating endpoint: [{0}] has [{1}] entries in LiveCycle 7.x category hierarchy.


ALC-UPG-070-043 Start to create endpoint for init-form [{0}] with categoryID [{1}] in category [{2}].




ALC-UPG-070-044 Migrating favorite from init-form [{0}] to endpoint with ID [{1}] is started.


ALC-UPG-070-045 Migrating favorite from init-form [{0}] to endpoint with ID [{1}] is completed.


ALC-UPG-070-046 Upgrading category: [{0} top level entries in [{1}].


ALC-UPG-070-047 Migrating security roles: [{0} assigned to role [{1}].


ALC-UPG-070-048 Migrating security: User or group [{0} with OID [{1}] is assigned to service [{2}] while upgrading endpoint [{3}].


ALC-UPG-070-049 Aggregating security: User or group {0} with OID [{1}] is aggregated to service [{2}] while upgrading endpoint [{3}].


ALC-UPG-070-050 Creating endpoint: [{0}] exists already for service [{1}] with init-form [{2}]; do nothing for this call.


ALC-UPG-070-051 Workspace ES upgrade [{0}]: [{1}] is called but nothing to upgrade. LiveCycle Form Manager may not be installed.


ALC-UPG-070-052 Migrating security info: (data from Repository) user or group [{0}] with OID [{1}] has access to init-form [{2}].


ALC-UPG-070-053 Migrating security info: user or group [{0}] with OID [{1}] is an entry of product between node with path [{2}] and [{3}].


ALC-UPG-070-054 Migrating security info: user or group [{0}] with OID [{1}] is an entry of product on a node with path [{2}].


ALC-UPG-070-055 Migrating security info: open group [{0}] with OID [{1}].


ALC-UPG-070-056 Migrating security info: group [{0}] has user [{1}] with OID [{2}].


ALC-UPG-070-057 Migrating security info: open group [{0}] with OID [{1}] tried. Is it a group? [{2}].



Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Forms 145

Upgrading LiveCycle Forms

ALC-UPG-070-058 Migrating security info: all principals OID = [{0}] in domain [{1}].


ALC-UPG-070-059 Migrating security info: all domain principals OID = [{0}] in domain [{1}].


ALC-UPG-070-060 Migrating security info: OID [{0}] with node {1} within path [{2}] of categories.xml found in domain [{3}] with name [{4}].


ALC-UPG-070-061 Migrating security(WARNING): OID [{0}] with node [{1}] within path [{2}] of categories.xml not found in domain [{3}].


ALC-UPG-070-062 Creating endpoint: init-form [{0}] found in category [{1}] with categoryID [{2}], which is not necessarily the top-level category.


ALC-UPG-070-063 Creating endpoint: looking for visibility for init-form [{0}]. Is it visible? [{1}]. If visibility is false, no endpoint will be created.




ALC-UPG-080-001 Failed to extract {0} file from LiveCycle 7.x build. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-002 Failed to migrate critical data. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-003 Failed to verify LiveCycle Forms installation type. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-021 Collect files for LiveCycle Forms started. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-022 Collect files for LiveCycle Forms completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-023 Collect files for LiveCycle Forms failed. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Print 146

Upgrading LiveCycle Print

ALC-UPG-080-024 Migrate critical data for LiveCycle Forms started. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-025 Migrate critical data for LiveCycle Forms completed.


ALC-UPG-080-026 Migrate critical data for LiveCycle Forms failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-080-027 LiveCycle Forms temporary staging folder created at [location].




ALC-UPG-090-001 Failed to extract {0} files from LiveCycle 7.x build. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-002 Failed to migrate critical data. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-003 Failed to verify Output installation type. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-021 Collect files for Output started. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-022 Collect files for Output completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-023 Collect files for Output failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-024 Migrate critical data for Output started. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-025 Migrate critical data for Output completed. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading core components 147

Upgrading core components

ALC-UPG-090-026 Migrate critical data for Output failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-090-027 Output temp staging folder created at [location]. Address the issue identified in the Cause section of the log message.




ALC-UPG-100-002 Failed to locate directory {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-003 Failed to locate file {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-003 Failed to create temporary directory {0} to extract trust store contents.


ALC-UPG-100-004 Failed to locate {0} in {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-005 Failed to locate temporary directory {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-006 Failed to locate {0}. Entry from user is NULL/EMPTY STRING.


ALC-UPG-100-007 Failed to extract file(s) {0} from archive {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-007 Failed to locate {0}. Entry from user is NULL/EMPTY STRING.


ALC-UPG-100-008 Unexpected J2EE file : {0} is not an EAR/WAR/BAR file.



ALC-UPG-100-009 Failed to create directory {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-010 Problem loading properties from {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-011 Problem injecting file(s) {0} into {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-012 Problem removing {0} from {1} Address the issue identified in the Cause section of the log message.

ALC-UPG-100-013 Failed to delete {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-014 Problem setting LiveCycle ES core configuration properties in file {0}.


ALC-UPG-100-015 Problem copying file {0} to location {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-016 Problem closing file {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-019 Failure occurred at step {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-031 Extraction of LiveCycle 7.x Data Manager Module and Font Manager Module contents initiated.


ALC-UPG-100-032 Extraction of LiveCycle 7.x Data Manager Module and Font Manager Module contents completed.


ALC-UPG-100-033 Task failed while extracting LiveCycle 7.x Data Manager Module and Font Manager Module contents.


ALC-UPG-100-034 Applying LiveCycle 7.x Data Manager Module and Font Manager Module contents initiated.


ALC-UPG-100-035 Applying LiveCycle 7.x Data Manager Module and Font Manager Module contents completed.




ALC-UPG-100-036 Task failed while applying LiveCycle 7.x Data Manager Module and Font Manager Module contents.


ALC-UPG-100-037 Migration of LiveCycle 7.x Data Manager Module and Font Manager Module contents initiated.


ALC-UPG-100-038 Migration of LiveCycle 7.x Data Manager Module and Font Manager Module contents completed.


ALC-UPG-100-039 Task failed while migrating LiveCycle 7.x Data Manager Module and Font Manager Module contents.


ALC-UPG-100-041 Migration of LiveCycle 7.x global document storage (GDS) contents started.


ALC-UPG-100-042 Migration of LiveCycle 7.x global document storage (GDS) directory contents completed.


ALC-UPG-100-043 Adding core configuration properties into LiveCycle ES EAR file.


ALC-UPG-100-044 Injecting files into LiveCycle ES EAR file completed.


ALC-UPG-100-051 LiveCycle 7.x global document storage (GDS) directory location does not exist or contains no files/subdirectories. Therefore, it is not necessary to copy any files.


ALC-UPG-100-052 LiveCycle 7.x global document storage (GDS) directory is identical to LiveCycle ES GDS directory. Therefore, it is not necessary to copy any files.


ALC-UPG-100-053 Copying [fileName] to location [directoryName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-054 Copying [fileName] from {1} to location {2} Address the issue identified in the Cause section of the log message.

ALC-UPG-100-055 Taking existing {0} from current working directory from previous run.



Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading Font Manager Module 150

Upgrading Font Manager Module

ALC-UPG-100-056 Extracting {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-057 Enabling dialog {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-058 Removing {0} from {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-100-059 Setting LiveCycle ES core configuration properties in {0}.


ALC-UPG-100-060 Loading LiveCycle 7.x core configuration properties from {0}.


ALC-UPG-100-061 Setting LiveCycle ES core configuration property {0} to {1}.


ALC-UPG-100-062 Saving LiveCycle ES core configuration properties {0} to {1}.




ALC-UPG-110-001 Failed to extract customer fonts from archive {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-110-002 Failed to locate directory {0} to migrate LiveCycle 7.x customer fonts.


ALC-UPG-110-003 Failed to locate path for customer fonts migration. Entry from user is NULL/EMPTY STRING.


ALC-UPG-110-011 Migration of LiveCycle 7.x customer fonts started. Address the issue identified in the Cause section of the log message.

ALC-UPG-110-012 Migration of LiveCycle 7.x customer fonts completed.


Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading Trust Manager Module 151

Upgrading Trust Manager Module

ALC-UPG-110-013 No customer fonts found. Customer fonts migration is completed.


ALC-UPG-110-021 Extracting customer fonts from file {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-110-022 Copying LiveCycle 7.x customer fonts to location {0}.





ALC-UPG-120-002 Failed to create directory {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-004 Failed to locate directory {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-005 Failed to locate temporary directory {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-006 Failed to locate file {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-008 Failed to extract file(s) {0} from archive {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-009 Unexpected J2EE file : [fileName] is not an EAR/WAR/BAR file.


ALC-UPG-120-010 Problem transforming trust.xml file {0}. Cannot prepare for trust store import.


ALC-UPG-120-011 Problem parsing trust.xml file {0}. Address the issue identified in the Cause section of the log message.


ALC-UPG-120-012 Failed to extract trust store contents from archive {0}.


ALC-UPG-120-013 Failed to find credential record from upgrade UI for alias {0}.


ALC-UPG-120-014 Failed to retrieve trust store contents in working directory. The time estimate to migrate trust store data is unknown.


ALC-UPG-120-015 Failed to verify P12 Record [{0}]. Skipping... Address the issue identified in the Cause section of the log message.

ALC-UPG-120-016 Failed to verify record [{0}] : invalid file format/content. Skipping...


ALC-UPG-120-017 Failed to verify P12 Record [{0}] : possibly invalid password. Skipping...


ALC-UPG-120-018 Failed to locate file [fileName] in the trust store repository.


ALC-UPG-120-019 Problem copying file [fileName] to location {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-020 Problem closing file [fileName]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-021 Import of Credential [{0}] failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-022 Import of Certificate [{0}] failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-023 Import of HSM [{0}] failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-024 Import of CRL [{0}] failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-025 Import of P12 Record [{0}] failed. Address the issue identified in the Cause section of the log message.



ALC-UPG-120-026 Import of MSCAPI Record [{0}] failed. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-027 NULL Certificate file specified in trust.xml record. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-028 NULL Credential File specified in trust.xml record. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-029 NULL CRL File specified in trust.xml record. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-031 Extraction of LiveCycle 7.x trust store contents initiated.


ALC-UPG-120-032 Extraction of LiveCycle 7.x trust store contents completed.


ALC-UPG-120-033 Task failed while extracting LiveCycle 7.x trust store contents.


ALC-UPG-120-034 Migration of LiveCycle 7.x trust store contents initiated.


ALC-UPG-120-035 Migration of LiveCycle 7.x trust store contents completed.


ALC-UPG-120-036 Migration of LiveCycle 7.x trust store contents completed with errors.


ALC-UPG-120-037 Task failed while migrating LiveCycle 7.x trust store contents.


ALC-UPG-120-038 Registering credential names with framework. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-039 Credential name registration successful. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-040 Created trust store shared data directory {0}. Address the issue identified in the Cause section of the log message.



ALC-UPG-120-041 Invoking LiveCycle ES service [{0}], operation [{1}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-042 Preparing CRL [{0}] for import. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-043 Importing CRL [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-044 CRL [{0}] imported successfully. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-045 Migrating trust anchors. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-046 Preparing CER Record [{0}] for import. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-047 Importing CER Record [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-048 CER Record [{0}] imported successfully. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-051 Migrating Credentials. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-052 Preparing P12 Record [{0}] for import. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-053 Importing P12 Record [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-054 P12 Record [{0}] imported successfully. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-055 No password entered for P12 record: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-056 Skipping migration of P12 record [{0}] (deselected by customer).




ALC-UPG-120-057 [{0}] is not DSS credential. Skipping... Address the issue identified in the Cause section of the log message.

ALC-UPG-120-061 Import of Credential [{0}] skipped. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-062 Import of Certificate [{0}] skipped. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-063 Import of HSM [{0}] skipped. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-064 Import of CRL [{0}] skipped. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-065 Import of P12 Record [{0}] skipped. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-066 Import of MSCAPI Record [{0}] skipped. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-067 Trust record [{0}] already exists. Skipping... Address the issue identified in the Cause section of the log message.

ALC-UPG-120-068 Migration of LiveCycle 7.x trust store contents stopped.


ALC-UPG-120-071 Preparing MSCAPI record [{0}] for import. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-072 Importing MSCAPI record [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-073 MSCAPI record [{0}] imported successfully. Address the issue identified in the Cause section of the log message.

ALC-UPG-120-081 NULL Credential alias specified in trust XML record.



Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Assembler 156

Upgrading LiveCycle Assembler


ALC-UPG-140-001 Empty path to Assembler7.ear file. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-002 Failed to create Assembler working directory: [{0}].


ALC-UPG-140-003 Failed to create LiveCycle Assembler 7.x working directory: [{0}].


ALC-UPG-140-004 Failed to unzip Assembler7EJB.jar file from adobe-Assembler7.ear. Entry: assembler7EJB.jar file not found in [{0}].


ALC-UPG-140-005 Failed to unzip server.properties file from Assembler7.jar. Entry: server.properties file not found in [{0}].


ALC-UPG-140-006 Unanticipated exception caught: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-007 Empty path to Assembler7.ear file. Export directory is null.


ALC-UPG-140-008 Java EAR file not found. Java ear == [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-009 Assembler working directory does not exist. mAssemblerWorkingDir == [{0}].


ALC-UPG-140-010 Failed to create Assembler LiveCycle ES working directory: [{0}].


ALC-UPG-140-011 Assembler7to8EJB.jar file not found in [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-012 Failed to create Assembler ejbJarDir working directory: [{0}].


ALC-UPG-140-013 Failed to move file [fileName] to [location]. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Document Security 157

Upgrading LiveCycle Document Security

ALC-UPG-140-014 Stop signal received. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-015 Setting up working directories. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-016 Extracting server.properties file from adobe-Assembler7.ear.


ALC-UPG-140-017 Copying [{0}] to Assembler working directory. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-018 Extracting Assembler7to8EJB.jar file. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-019 Updating Assembler7to8EJB.jar file with Assembler 7 server.properties file.


ALC-UPG-140-020 Repackaging [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-140-021 Task completed. Address the issue identified in the Cause section of the log message.



ALC-UPG-150-100 Found some valid preferences in the trust.xml file. Parsing the file.


ALC-UPG-150-104 No valid preferences found in the trust.xml file. Nothing to do for Signatures upgrade.


ALC-UPG-150-105 Failed to locate Signatures component. Signatures upgrade failed.


ALC-UPG-150-106 Signatures upgrade successful. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading LiveCycle Document Security 158

ALC-UPG-150-107 Signatures upgrade encountered some problems but completed partially.


ALC-UPG-150-108 Signatures upgrade encountered fatal problems. Upgrade failed.


ALC-UPG-150-109 Looking for service {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-150-110 \n {0} Caused by {1}. \n More Info {2}. Address the issue identified in the Cause section of the log message.

ALC-UPG-150-111 Service {0} found in state {1}. Address the issue identified in the Cause section of the log message.

ALC-UPG-150-112 Service {0} not found. Address the issue identified in the Cause section of the log message.

ALC-UPG-150-113 Service {0} successfully configured! Address the issue identified in the Cause section of the log message.

ALC-UPG-150-114 Service {0} could not be configured! Address the issue identified in the Cause section of the log message.

ALC-UPG-150-115 Trying to stop existing Service {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-150-116 Trying to create a new configuration for service {0}.


ALC-UPG-150-117 Creation of new configuration for service {0} succeeded without any problems.


ALC-UPG-150-118 Creation of new configuration for service {0} encountered problems.


ALC-UPG-150-119 Trying to apply the new configuration for service {0}.


ALC-UPG-150-120 Trying to start existing service {0}. Address the issue identified in the Cause section of the log message.


Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading watched folders 159

Upgrading watched folderss

ALC-UPG-150-121 Failed to handle the new configParameter {0} of type {1}.


ALC-UPG-150-122 Skipped modifying {0} the new configuration parameter for old parameter {1}; value of oldParameter is null.


ALC-UPG-150-123 Successfully mapped old configuration parameter {0} with value {1} to new configuration parameter {2} of type {3} and value {4}.


ALC-UPG-150-124 Error while setting up the configuration parameter value for old parameter {0}. Got Exception {1}.


ALC-UPG-150-125 No new parameter name found to correspond with oldParameter name {0}. The old value will be ignored.


ALC-UPG-150-126 Service {0} partially configured. Some configuration parameters may not have been mapped successfully.


ALC-UPG-150-127 Trying to call the start method of the service {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-150-128 Service {0} start function successfully called. Address the issue identified in the Cause section of the log message.




ALC-UPG-160-001 Initialization failed: {0} Address the issue identified in the Cause section of the log message.

ALC-UPG-160-002 Caught POFException: [{0}] Address the issue identified in the Cause section of the log message.

ALC-UPG-160-003 Failure to parse service configuration. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading watched folders 160

ALC-UPG-160-004 Failure to read service configuration. Address the issue identified in the Cause section of the log message.

ALC-UPG-160-005 Failed to create LiveCycle ES endpoint from the LiveCycle 7.x endpoint for path {0}. Possible reasons are {1}.


ALC-UPG-160-006 Invalid default endpoint. Does not have configuration parameters.


ALC-UPG-160-007 Failed to find the job configuration file for watched folder with path {0}. Failed to upgrade the watched folder.


ALC-UPG-160-008 Failed to find the process with name {0} for watched folder with path {1}.


ALC-UPG-160-009 Failed to find the operation {0} for service {1} for watched folder with path {2}.


ALC-UPG-160-100 Failed to find jobConfig file for watched folder with URL {0}.


ALC-UPG-160-101 Watched folder at {0} is already configured for service {1}.


ALC-UPG-160-102 Number of watched folders to migrate are {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-160-103 Number of watched folders migrated are {0}. Address the issue identified in the Cause section of the log message.

ALC-UPG-160-104 Number of watched folders that failed to migrate are {0}.


ALC-UPG-160-105 Upgraded endpoint for watched folder with URL {0} successful.



Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading Content Repository Connector for EMC Documentum 161

Upgrading Content Repository Connector for EMC Documentum


ALC-UPG-201-000 Internal error: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-001 Caught POFException: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-002 Caught IOException: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-003 Caught RepositoryException: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-200 Creation of DB Tables started... Address the issue identified in the Cause section of the log message.

ALC-UPG-201-201 Creation of DB Tables completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-202 Starting Content Repository Connector for EMC Documentum services...


ALC-UPG-201-203 Content Repository Connector for EMC Documentum services started.


ALC-UPG-201-204 Migration of Shared Locks data started... Address the issue identified in the Cause section of the log message.

ALC-UPG-201-205 Processed [{0}] Shared Locks. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-206 Migration of Shared Locks data completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-201-207 Removal of Runtime settings data started... Address the issue identified in the Cause section of the log message.

ALC-UPG-201-208 Removal of Runtime settings data completed. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading Content Repository Connector for IBM FileNet 162

Upgrading Content Repository Connector for IBM FileNet

ALC-UPG-201-209 Cleanup of Preferences data started... Address the issue identified in the Cause section of the log message.

ALC-UPG-201-210 Cleanup of Preferences data completed. Address the issue identified in the Cause section of the log message.



ALC-UPG-211-000 Internal error: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-001 Caught POFException: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-002 Caught IOException: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-003 Caught RepositoryException: [{0}]. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-200 Creation of DB Tables started... Address the issue identified in the Cause section of the log message.

ALC-UPG-211-201 Creation of DB Tables completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-202 Starting Content Repository Connector for IBM FileNet services...


ALC-UPG-211-203 Content Repository Connector for IBM FileNet services started.


ALC-UPG-211-204 Migration of Shared Locks data started... Address the issue identified in the Cause section of the log message.

ALC-UPG-211-205 Processed [{0}] Shared Locks. Address the issue identified in the Cause section of the log message.

Adobe LiveCycle ES Error Code Reference for Upgrading LiveCycle ESLiveCycle ES Error Code Reference Upgrading Content Repository Connector for IBM FileNet 163

ALC-UPG-211-206 Migration of Shared Locks data completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-207 Removal of Runtime settings data started... Address the issue identified in the Cause section of the log message.

ALC-UPG-211-208 Removal of Runtime settings data completed. Address the issue identified in the Cause section of the log message.

ALC-UPG-211-209 Cleanup of Preferences data started... Address the issue identified in the Cause section of the log message.

ALC-UPG-211-210 Cleanup of Preferences data completed. Address the issue identified in the Cause section of the log message.


livecycle es error code reference - adobe - adobe support · pdf fileadobe livecycle es about...

Documents