adobe livecycle es update 1 install instructions and fixed

1

Adobe LiveCycle ES Update 1 Service Pack 4Install Instructions and Fixed Customer Issues

Service Pack 4, Version 8.2.1.4July 2011

Copyright 2011 Adobe Systems Incorporated. All rights reserved.

Contents“Purpose of this service pack” on page 1

“Known issues” on page 1

“Installing the service pack” on page 1

“Installing the service pack when upgrading to the LiveCycle ES server” on page 8

“Issues addressed in this service pack” on page 11

Purpose of this service packThis service pack provides general fixes to Adobe® LiveCycle® ES (Enterprise Suite) Update 1. (See “Installing the service pack” on page 1.)

Known issuesFor a complete listing of the known issues in LiveCycle ES, see LiveCycle ES Release Notes, which was updated for Service Pack 4.

Installing the service packThis service pack contains patches for Adobe LiveCycle Designer ES, Adobe LiveCycle Workbench ES, and LiveCycle ES server.

“Preparing to install the service pack” on page 2

“Installing the service pack for Workbench ES” on page 2

“Installing and configuring the service pack for LiveCycle ES server” on page 2

These instructions assume that you have installed LiveCycle ES 8.2.1.

Note: If you are upgrading from LiveCycle 7.x, or your LiveCycle ES 8.0.1 deployment was upgraded from LiveCycle 7.x, follow the instructions in “Preparing to install the service pack” on page 2 and then continue with “Upgrading to LiveCycle ES and applying Service Pack 4” on page 8.

www.adobe.com/go/learn_lc_releaseNotes_82

Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Preparing to install the service pack 2

Preparing to install the service packNote: Use any MD5 encryption utility to verify that the lces82_service_pack_4_[appserver].tar.gz or

lces82_service_pack_4_[appserver].zip file has downloaded properly. The checksum number is posted on the Adobe download site.

Before you install this service pack, ensure that your environment is backed up. Further, before you install this service pack, ensure that you have sufficient free disk space available:

● Installing SP4 for Designer ES requires 25.6 MB.

● Installing SP4 for Workbench ES requires 200 MB.

● Installing SP4 for LiveCycle ES server requires 4 GB.

Installing the service pack for Workbench ESThere are two methods used to incorporate Workbench ES functionality into your LiveCycle ES environment:

● Default integrated development environment

● As a plug-in to an existing Eclipse 3.2.2 or 3.3.1 environment

➤ To install the service pack for Workbench ES:

1. Ensure that Workbench ES is not running.

2. Install the service pack for Workbench ES by running adobe_livecycle_workbench_8_4_patch.exe. This step opens a wizard that guides you through the installation.

3. On the Welcome screen, click Next.

4. On the Patch Installation Location screen, verify that the default location displayed is correct for your existing installation, or click Browse to select the alternate folder where Workbench ES is currently installed, and then click Next.

5. On the Service Pack Summary screen, review the information and, if it is correct, click Next. (Click Back to correct any errors that occurred.)

6. On the Service Pack Summary (continued) screen, review the information and, if it is correct, click Install. (Click Back to correct any errors that occurred).

7. On the Service Pack Installation Completion screen, click Next to apply the updates.

8. When the Service Pack Installation Completion screen refreshes to indicate a successful installation, click Finish to exit the wizard.

9. Start Workbench ES, select Help > About, and then verify that Version 8.2.1.4 displays on the splash screen. Version 8.2.1.4 confirms the service pack update.

Installing and configuring the service pack for LiveCycle ES serverPerform the following procedures to install the LiveCycle ES service pack for LiveCycle ES server:

● Install the service pack (see “To install the service pack for the LiveCycle ES server:” on page 3).

Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Installing and configuring the service pack for LiveCycle ES server 3

● Configure and deploy LiveCycle ES for the service pack (see “(Turnkey Custom and manual) To perform configuration or deployment tasks using LiveCycle Configuration Manager:” on page 5).

Note: Ensure that Adobe LiveCycle Configuration Manager is not running before you start the service pack install wizard.

Note: Ensure that you take full backup before installing Service Pack.

➤ To install the service pack for the LiveCycle ES server:

Note: You must stop the JBoss and MySQL services before running the LiveCycle ES service pack installer (for JBoss Turnkey Installation only).

1. If you are installing on UNIX , you must set the executable permissions on the installation file. For example, to set the permissions for the Linux installation file, at the command prompt, type:

chmod 755 x86_linux_adobe_livecycle_8_2_patch.bin

2. Run the executable file appropriate for your operating system. This step opens a wizard that guides you through the installation:

● (Windows) x86_win32_adobe_livecycle_8_2_patch.exe

● (Linux) x86_linux_adobe_livecycle_8_2_patch.bin

● (AIX) powerpc_aix_adobe_livecycle_8_2_patch.bin

● (Solaris) solaris_sparc_adobe_livecycle_8_2_patch.bin

3. When prompted, select the language to use for the installation and then click OK.


5. On the Service Pack Installation Location screen, verify that the default location displayed is correct for your existing installation, or click Browse to select the alternate folder where LiveCycle ES is currently installed, and then click Next.

6. On the Service Pack Summary screen, review the information and, if it is correct, click Next. (Click Back to correct any errors.)

7. On the Service Pack Summary (continued) screen, review the information and, if it is correct, click Install. (Click Back to correct any errors.)


Note: Allow the service pack installer to complete the service pack updates. Typical time to apply the patch updates is approximately 5 minutes; however, it may take as many as 15 minutes (depending on the resources that are available on your system). You may check installation log at [installation directory]\patch\SP4\patch.log for installation related errors.

9. When the Service Pack Installation Completion screen refreshes to indicate a successful installation, ensure that Start LiveCycle Configuration Manager is selected and then click Finish to exit the wizard.

➤ (WebLogic and MySQL combinations only) Update scheduled invocations:

If your current LiveCycle ES environment has events that are scheduled to trigger automatically, or if you cannot guarantee that all users are logged off and may trigger events during the update process, you


should stop those events before you run LiveCycle Configuration Manager. This avoids having the events start up during the configuration for LiveCycle ES 8.2 and subsequently cause errors.

Stand-alone LiveCycle ES environments that do not rely on scheduled events are not likely to need to perform the following tasks (for example, stand-alone Reader Extensions ES, PDF Generator ES, and Rights Management ES installations). Also, if your environment uses only short-lived processes (such as those run by Forms ES and Reader Extensions ES), then you will probably not perform the tasks in this section.

1. Log in to LiveCycle Workbench ES and click Window > Show View > Components.

2. Scroll to the SchedulerService, and right click it and select Stop Component.

3. Log out of Workbench ES.

4. Log in to WebLogic Administration Console at http://[server_ip_address]:7001/console.

5. Navigate to Services > Messaging > JMS Servers > IDPJMSServer.

6. In the Change Center (top left of your screen), click Lock & Edit.

7. Scroll to the bottom of the Configuration tab and click Advanced.

8. Check Consumption Paused at Startup and then click Activate Changes in the Change Center.

9. Navigate to Services > Messaging > JMS Modules > IDPJMSModule, select adobe_JobManagerQueue and click the Control tab.

10. Select IDPJMSModule!adobe_JobManagerQueue and select Pause from the Consumption drop down.

11. On the next page, verify that you want to pause consumption by clicking Yes.

12. Repeat steps 9 to 11 for the adobe_PECommandQueue and adobe_PEDCommandQueue destinations.

13. Start LiveCycle Configuration Manager for LiveCycle ES 8.2 and configure as required.

14. After completing the LiveCycle Configuration Manager configuration, log in to LiveCycle Workbench ES, and click Window > Show View > Components.

15. Scroll to the EventManagement service, right click it, and select Stop Component.

16. Scroll to the SchedulerService, right click it, and select Start Component.

17. Scroll to the EventManagement service, right click it and select Start Component.

➤ (Turnkey Express Mode) To perform configuration or deployment tasks using LiveCycle Configuration Manager:

Note: If you are continuing directly from the installation process, go to step 4 of this procedure.

1. Start the application server.

2. Start LiveCycle Configuration Manager by navigating to the [LiveCycleES root]/configurationManager/bin directory and entering the following command:

● (Windows) ConfigurationManager.bat

● (Non-Windows) ./ConfigurationManager.sh


3. When prompted, select the language to use for the installation and click OK.


5. On the Upgrade Selection screen, ensure that Upgrade LiveCycle 7.x is not selected, and then click Next.

6. On the Turnkey Mode screen, select Express Mode.

7. On the Solution Component screen, keep the defaults and click Next.

Depending on the solution components you have installed, you may see additional configuration screens. Refer to the F1 help for detailed information for these screens.

8. On the Express Mode screen, click Start and then Next when the operation is finished.

9. On the LiveCycle ES Samples Import screen, select or deselect Skip LiveCycle ES Samples Import and click Next to proceed.

10. After the tasks have completed, log in to LiveCycle Administration Console by typing the URL http://[host name]:[port]/adminui in a web browser.

11. Restart the application server.

➤ (Turnkey Custom and manual) To perform configuration or deployment tasks using LiveCycle Configuration Manager:

Note: If you are continuing directly from the installation process, go to step 4 of this procedure.

1. Start the application server.

2. Start LiveCycle Configuration Manager by navigating to the [LiveCycleES root]/configurationManager/bin directory and entering the following command:

● (Windows) ConfigurationManager.bat

● (Linux, UNIX) ./ConfigurationManager.sh

3. When prompted, select the language to use for the installation and click OK.


5. On the Upgrade Selection screen, ensure that Upgrade LiveCycle 7.x is not selected, and then click Next.

6. (Turnkey only) On the Turnkey Mode screen, select Custom Mode and click Next.

Note: See “(Turnkey Express Mode) To perform configuration or deployment tasks using LiveCycle Configuration Manager:” on page 4 for updating using Turnkey Express Mode.

7. On the Solution Component screen, keep the defaults and click Next.

8. Perform the task in the table below that applies to your configuration. For more information, see the Installing and Deploying LiveCycle ES or Configuring LiveCycle ES Application Server Clusters document that applies to your application server and configuration.



Note: In a clustered configuration, restart each application server instance of the cluster.

10. Log in to LiveCycle Administration Console, select About, and then verify that the patch version is “SP4”.

Configuration Task

● JBoss Application Server (turnkey)

● WebLogic Server (turnkey)

● Stand-alone WebLogic Server (non-turnkey)

● Stand-alone WebSphere Application Server

● On the Task Selection screen, select the following tasks and then click Next:

● Configure LiveCycle ES

● Deploy EARs

● Initialize LiveCycle ES database

● Deploy the LiveCycle ES components

● Validate the LiveCycle ES component deployment

● (Optional) Import the LiveCycle ES Samples

Caution: If you have run LiveCycle Confriguration Manager before installing Service Pack 4, do not select the tasks to configure the application server or to validate the application server.

If this error appears in the application server log file, it can be safely ignored: UMConstants.ErrorCodes.E_RESTYPE_PREEXISTS_WITH_SAME_ATTRIBUTE

● Stand-alone JBoss Application Server (non-turnkey)

● JBoss Application Server cluster

● WebLogic Server cluster

● WebSphere Application Server cluster

● On the Task Selection screen, select Configure LiveCycle ES and then click Next to configure the LiveCycle ES EAR files for the service pack.

● Exit LiveCycle Configuration Manager and then manually undeploy the existing LiveCycle ES EAR files.

● Manually deploy the new LiveCycle ES 8.2.1.4 EAR files. EAR files are located at [installation directory]\configurationManager\export

● Return to LiveCycle Configuration Manager and, on the Task Selection screen, select the following tasks:


● Deploy the LiveCycle ES components,



Note: If you have run LiveCycle Confriguration Manager before installing Service Pack 4, do not select the tasks to configure the application server or validate the application server.

Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Troubleshooting Service Pack 4 7

➤ Post-configuration tasks

IBM FileNet services may not be in started state after installing and configuring Adobe LiveCycle ES Service Pack 4. To start these services from Administration Console:

1. In LiveCycle Administration Console, click Services > Applications and Services > Service Management.

2. On the Service Management page, select Connector for IBM Filenet from the "Category" drop down and then click Filter. All the IBM Filenet services are shown.

3. Select the check box beside all the service for IBM FileNet and then click Start.

Troubleshooting Service Pack 4 While configuring WebLogic Server on a Japanese OS using LiveCycle Configuration Manager, you may encounter the following error:

Error [ALC-LCM-140-102] Failed on 'Starting Target Server' Failed to start LCServer1

The following workaround resolves this issue:

● At the error, either close LiveCycle Configuration Manager (to restart the process) or leave it open (to return to the current screen) and proceed to step 2.

● Stop and restart “LCServer1” using WebLogic Administration Console.

● Restart or return to LiveCycle Configuration Manager again and proceed with the configuration.

On a WebSphere Application Server, you may encounter transaction time-out issues at the default settings. If, after you restart your application server, LiveCycle ES does not work, perform the following procedure.

➤ To correct transaction timeout issues on WebSphere Application Server:

1. Review the log files for timeout errors or warning messages about the Global and Font directories.

2. If messages exist, open WebSphere Administrative Console, Servers > Application Servers and, in the right pane, click the server name.

3. Under Container Settings, Container Services > Transaction Service.

4. Increase the Total transaction lifetime timeout and Maximum transaction timeout values, click OK and then click Save directly to the master configuration.

Note: The values required depend on your environment. You must adjust these settings until the appropriate values are found.


Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Installing the service pack when upgrading to the LiveCycle ES server 8

➤ To revert your LiveCycle 8.2 server installation to pre-Service pack 4 state

1. Access the [LiveCycle ES root]\patch\SP4\FilesAddedDuringServicePack_RemoveOrReplaceToRevert.txt file and complete the following steps:

● Delete the files listed in FilesAddedDuringServicePack_RemoveOrReplaceToRevert.txt from your existing LiveCycle ES installation.

● Replace the folders listed in this file with the corresponding folders from the backup copy at [LiveCycle ES root]\patch\SP4\backup_SP4.

2. Replace the files in the following directories under [LiveCycle ES root] with files from the backup copy at [LiveCycle ES root]\patch\SP4\backup_SP4:

● configurationManager

● deploy

● LiveCycle_ES_SDK

● plugins

Note: For more information, refer to the patch logs at [LiveCycle ES root]/patch/SP4/log.

3. After restoring the [LiveCycle ES root]/configurationManager directory, delete the EAR files in the [LiveCycle ES root]/configurationManager/export directory.

4. (Optional) If you don’t require the SP4 patch files, delete the [LiveCycle ES root]/patch/SP4 directory.

Installing the service pack when upgrading to the LiveCycle ES server

Follow the instructions in this section if you are upgrading from LiveCycle 7.x to LiveCycle ES or if your current LiveCycle ES deployment was upgraded from LiveCycle 7.x.

Apply the service pack by performing the steps in the section that applies to your situation:

● “Upgrading to LiveCycle ES and applying Service Pack 4” on page 8

● “Applying the service pack to an upgraded LiveCycle ES” on page 9

● “Installing the service pack for Workbench ES on an upgraded LiveCycle ES” on page 10

Note: It is recommended that you install latest service pack available for LiveCycle 7.x before upgrading to the LiveCycle ES server.

For information about system requirements and upgrade conditions, see Preparing to Upgrade to LiveCycle ES from 7.x.

For information about using LiveCycle Configuration Manager to configure, upgrade, and deploy LiveCycle ES, see Upgrading to LiveCycle ES for JBoss, Upgrading to LiveCycle ES for WebSphere, or Upgrading to LiveCycle ES for WebLogic.

Upgrading to LiveCycle ES and applying Service Pack 4Perform the following procedure to upgrade a LiveCycle version 7.0.x, 7.1 or 7.2.2 deployment to LiveCycle ES and apply the LiveCycle ES service pack. Ensure that you take full backup before installing Service Pack.

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

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

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

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

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

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

Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Applying the service pack to an upgraded LiveCycle ES 9

➤ To upgrade to LiveCycle ES:

1. Install LiveCycle ES 8.2 by following the instructions in the Upgrading to LiveCycle ES document for your application server. (See the "Installing the Solution Component Files" section.) Do not start LiveCycle Configuration Manager.

2. Apply Service Pack 4 to the newly installed files by following steps 1 through 9 of the “To install the service pack for the LiveCycle ES server:” on page 3 procedure.

3. Run LiveCycle Configuration Manager as instructed in the “(Turnkey Custom and manual) To perform configuration or deployment tasks using LiveCycle Configuration Manager:” on page 5 procedure.

4. Complete the configuration, upgrade, and deployment by following the instructions in the "Configuring LiveCycle ES for Deployment" section of the Upgrading to LiveCycle ES document for your application server.

Note: On the LiveCycle Server Information screen, you must enter the fully qualified path to the application server in the Local Application Server Root Directory field; otherwise, a “Class not found” error will occur during data migration.

Applying the service pack to an upgraded LiveCycle ESPerform the following procedure to apply the LiveCycle ES service pack to a LiveCycle ES deployment.

➤ To apply the service pack to an upgraded LiveCycle ES server:

1. Determine the location of the current LiveCycle ES global document storage directory (GDS). (If you changed the location when you upgraded from the one used in LiveCycle 7.x, it will be reset to the LiveCycle 7.x location when you run LiveCycle Configuration Manager after you apply the patch. You will need to reapply the change that you made when you upgraded to LiveCycle ES.)

2. Apply the service pack to the newly installed files by following the steps 1 through 9 of the “To install the service pack for the LiveCycle ES server:” on page 3 procedure in this document.

3. Start LiveCycle Configuration Manager as instructed in the “(Turnkey Custom and manual) To perform configuration or deployment tasks using LiveCycle Configuration Manager:” on page 5 procedure.

Note: On the LiveCycle Server Information screen, you must enter the fully qualified path to the application server in the Local Application Server Root Directory field or a “Class not found” error will occur during data migration.

4. On the Upgrade Task Selection screen, select only Upgrade from LiveCycle 7.x and Apply LiveCycle 7.x configuration to LiveCycle ES.

Note: If you are patching Adobe LiveCycle Rights Management ES only, do not select Upgrade from LiveCycle 7.x (or the related subtasks).

5. On the Task Selection screen, select the following task options:

● Configure LiveCycle ES

● Deploy EARs (if you are deploying to WebSphere or WebLogic; otherwise, you can manually redeploy the EAR files by following the instructions in the Upgrading to LiveCycle ES relevant document.)


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


Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Installing the service pack for Workbench ES on an upgraded LiveCycle ES 10

● Deploy the LiveCycle ES components



Note: Do not select the tasks to configure the application server or validate the application server,

6. Complete the configuration, upgrade, and deployment of the patched EAR files by following the instructions in the LiveCycle Configuration Manager wizard and in the “Configuring LiveCycle ES for Deployment” section of the Upgrading to LiveCycle ES document for your application server.

Note: If the LiveCycle ES 8.2.1 SP4 EAR files do not deploy, manually undeploy the LiveCycle ES EAR files for the components you are updating according to the documentation. Next, restart the application server before you run LiveCycle Configuration Manager again.

7. Log in to LiveCycle Administration Console, select About, and then verify that the patch version is “SP4”.

8. Restart your application server.

Installing the service pack for Workbench ES on an upgraded LiveCycle ESThere are two methods used to incorporate Workbench ES functionality into your LiveCycle ES environment:

● With Eclipse 3.2.2 as part of an integrated development environment

● As a plug-in to an existing Eclipse 3.2.2 or 3.3.1 environment

Caution: (WebSphere Application Server only) If your Workbench ES installation is for LiveCycle ES running on a WebSphere Application Server that was upgraded from LiveCycle ES 7.x, you must perform additional configurations described in “To configure an upgraded Workbench ES installation on WebSphere Application Server:” on page 11.

➤ To install the service pack for Workbench ES:

1. Ensure that Workbench ES is not running.

2. Install the service pack for Workbench ES by running adobe_livecycle_workbench_8_2_patch.exe. This step opens a wizard that guides you through the installation.


4. On the Patch Installation Location screen, verify that the default location displayed is correct for your existing installation, or click Browse to select the alternate folder where Workbench ES is currently installed, and then click Next.

5. On the Service Pack Summary screen, review the information and, if it is correct, click Next. (Click Back to correct any errors that occurred.)

6. On the Service Pack Summary (continued) screen, review the information and, if it is correct, click Install. (Click Back to correct any errors that occurred.)


Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Issues addressed in this service pack 11


8. When the Service Pack Installation Completion screen refreshes to indicate a successful installation, click Finish to exit the wizard.

9. Start Workbench ES.

10. In the LiveCycle ES Adding New Server screen, do the following tasks and then click OK:

● In the Server Type box, select the appropriate application server.

● In the Server Port Number box, enter the appropriate SOAP port number for your installation.

● Under LiveCycle 7.x Support, ensure that Enable EJB connections for LiveCycle 7.x QPACs is selected.

11. Start Workbench ES, and then verify that the Version 8.2.1.4 displays on the splash screen. Version 8.2.1.4 confirms the service pack update.

➤ To configure an upgraded Workbench ES installation on WebSphere Application Server:

1. To obtain an appropriate Java 5 JRE navigate to IBM Development Package and click IBM Development Package for Eclipse.

2. Install the downloaded JRE on the computer that hosts your Workbench ES installation.

3. Open the [Workbench ES install location]/Workbench/workbench.ini file in a text editor and make the following changes:

● After the -vmargs line, add the line -vm "[path to downloaded JRE]\java.exe" (for example add -vm "D:\ibm_sdk50\jre\bin\java.exe").

● Find and delete the line -XX:MinHeapFreeRatio=20.

4. Save the edited workbench.ini file.

Issues addressed in this service packLiveCycle service packs are cumulative. If you install Service Pack 4 you will install all the fixes included with Service Pack 1, Service Pack 2 and Service pack 3. This service pack addresses the following customer-reported issues for LiveCycle ES 8.2.1.1, 8.2.1.2, and 8.2.1.3.

● “Service Pack 1” on page 11




Service Pack 1

Upgrade● Issues with Adobe Flex® and Adobe Flash® components accessed over SSL after upgrade to

LiveCycle ES 8.2.1.

http://www.ibm.com/developerworks/java/jdk/eclipse/

Adobe LiveCycle ES - Service Pack 4 Installation InstructionsService Pack Installation Instructions Service Pack 1 12

Database● Oracle® installation requirements add unnecessary database components with the transaction

template.

● Using the date on a parameterized query on a JDBC service causes a ClassCastException error.

Application server● IIOP-enabled EJBs running on WebLogic Server pass large objects slowly, causing significant

performance degradation.

Acrobat and Adobe Reader● Navigating through disabled form fields in Adobe Acrobat® or Adobe Reader® 9 generates a

warning message.

● Dynamic form scripts from Acrobat 7.x do not work after saving in Acrobat 8.

LiveCycle Configuration Manager● LiveCycle Configuration Manager fails to completely deploy EAR files for WebSphere Application

Server.

● LiveCycle Configuration Manager cannot deploy the adobe-livecycle-websphere.ear file to a WebSphere Application Server running on a localized French, German, or Japanese Windows operating system.

LiveCycle Designer ES● Aligning radio buttons on multiple pages causes Designer ES to fail.

● Form properties in a TDS template file do not persist when creating a new XDP template based on the TDS template.

● Case-sensitivity in the Data View Window is not respected after creating a data connection via an XML file.

● Changing the panel display rules causes data loss (the first row of a table with a repeater grid does not display).

● Very slow playback response time of the QTP 9.2 automation tool.

LiveCycle Foundation● Changes to the SMTP authentication causes problems with the SendWithDocuments service due to

configuration cache issues.

● The invoke_Status call in a web service never returns a “completed” status after PDF Generator ES encounters an expired SAML token error.

LiveCycle Output ES● Using xfa.layout.absPageCountInBatch with lazy loading turned on returns an invalid page count.

● generatePDFOutput fails when operating on a form submitted using 9.

LiveCycle Assembler● Assembler with an improper permission bit in the master password removes security when creating

a PDF.

● The PageOverlay element of Assembler changes the PDF version when overlaying PDF documents that are version 1.3 or earlier.


LiveCycle PDF Generator ES● PDF Generator ES creating a PDF from a Microsoft Word document modifies a footer containing the

file name to “native-in.doc”.

● Add PDF Generator ES support for email header formats sent by the iPhone.

● PDF Generator ES fails when using Notepad as a native application on a Japanese language operating system.

● Changes to PDF Generator ES PDF settings are not immediately reflected in a converted PDF.

LiveCycle Reader Extensions ES● Reader Extensions ES login fails to authenticate after upgrade.

LiveCycle Rights Management ES● Maximum password length for Rights Management ES is inconsistent with User Management.

● Unsatisfactory handling of duplicate items in the New Policy Set screen.

● All edits to a policy are lost if the edited policy name duplicates an existing policy name.

● Inconsistent behavior when setting dates on the Rights Management ES Documents page.

● Incorrect transition order path displayed on the Rights Management ES Delete Policy Set(s) screen.

● Cannot edit user details of an invited user whose email address is more than 50 characters.

● Microsoft Office files protected by Rights Management ES Extension for Microsoft Office/CATIA are vulnerable to malicious falsification.

● Content protected by Rights Management ES Extension for Microsoft Office/CATIA can be copied and pasted without permission through an open Microsoft Office Clipboard window.

LiveCycle User Management● After deleting a group from a user, the inherited role from the group cannot be deleted.

● When removing principals from group objects, the list of remaining principals (at the bottom of the page) is not updated.

● Unable to remove more than 10 users at once from a group.

● Editing a role fails and deletes the role being edited.

● Enhancement added to obtain a list of users and groups belonging to a specified group.

LiveCycle Workbench ES● Workbench ES running on a Vista Business 64-bit operating system crashes repeatedly.

● Workbench ES changes route lines in a process diagram following a save action.

● Links on the LiveCycle ES start page of Workbench ES do not launch the correct targets.

LiveCycle Workspace ES● When setting an “out of office” task, selecting an invalid duplicate name presented in the Find User

list causes an error.

● Workspace ES cannot display toast messages (workspace-toast.swf is missing).


Documentation● Inconsistent information provided for the LiveCycle ES installer screen Application Server

Configuration Details in the Installing and Deploying LiveCycle ES Using Turnkey (for JBoss or WebLogic) guide.

● Incorrect information about LDAP configuration in the Installing and Deploying LiveCycle ES guides.

● Insufficient information in the Installing and Deploying LiveCycle ES guides about configuring LiveCycle 7.x compatibility using LiveCycle Configuration Manager.

● Incorrect information about SSL configuration in the Administering LiveCycle ES guide.

● No information describing library dependencies for XMLForms in the Hardening and Security for LiveCycle ES guide.

● Insufficient information in the Preparing to Install LiveCycle ES guides about activating native applications before using PDF Generator ES to convert native documents to PDF.

● Insufficient information in the Help about converting zipped HTML pages to PDF.

● Help does not display for the “Deploy 7.x compatibility DSC” topic, which is accessed from the LiveCycle Configuration Manager Upgrade Task Selection screen.

● Incorrect information about switching policies for documents in the Rights Management ES Help.

● Insufficient information about supported file types in the PDF Generator ES Help.

● Error code ALC-PDG-010-012 is missing in the LiveCycle ES the Error Code Reference guide.

Localization issues● The Help [Next Step] accessed from the final installation screen (Japanese) has incoherent content.

● Several wrong translations in the Japanese version of the Rights Management ES Help.

Service Pack 2

Installation issues● Incomplete JBoss 4.2.0 installation source files.

LiveCycle Configuration Manager● LiveCycle Configuration Manager fails on WebLogic on Japanese OS.

LiveCycle Administration Console● Remote UNC path for GDS to a shared server location is not accepted.

LiveCycle Barcoded Forms ES● Cannot decode TIF files that have upper or mixed case characters in the filename extension.

● Unable to decode a PDF file.

LiveCycle ES Connector for IBM FileNet● A customer's client is not able to start PE Connectors service.

LiveCycle Designer ES● Copying or pasting a “globally” bound floating field will crash Designer ES.


● Designer ES embedded in Workbench ES crashes when a fragment is dragged and dropped from file system to the hierarchy section of a form being designed.

● XDP with broken WSDL connection freezes Workbench ES.

● Modifications to a schema does not update the source.

● Designer ES crashes when trying try to drag a fragment onto a subformSet.

● Border's presence remains hidden if the appearance was none, and is now changed to custom.

● Radio Buttons in a Form Object Collection should be locked if a Signature Field is signed and is assigned with all fields in that Collection.

● Designer ES crashes when you try to Copy a subform in this form.

● When scripting for the calculate event, the field's value in UI is auto set to “calculated-read only”, but field's access is still open.

LiveCycle Digital Signatures ES● Failed to add HSM Credential due to incorrect format.

LiveCycle Forms ES● Buttons do not appear with Workspace ES when using Firefox 3 using LiveCycle ES samples.

● French format for date not working with guide.

● Schema with complex type showing errand value when adding instance.

● Read-only custom check box on Panel becomes read-write on Form Guide during runtime.

● Support for Dynamic Binding of drop-down lists as in PDF for Guides.

● Attributes being saved as elements in additional instances of subform.

● Custom XMP element not generated.

● Forms ES HTML error messages.

● RenderPDFForm generates uncompressed PDF files.

● <p> tag should not be present inside <label> on NoScriptXHTML rendition using Forms ES.

● The <label> element in HTML output is rendered after the <input> control to which it relates.

● XDP fragments with “&” in the filename cause ALC-XTG-102-001: [2348] Cannot resolve url:

● Data is not merged into drop-down when rendered as XHTML in Safari.

● Enhancement to remove the tabIndex property from fields when only the Form body is called for (outputType=0).

LiveCycle Output ES● Image printing problem in PCL on Output ES (ASAP).

● Some words in Hebrew get reversed after flattening PDF using transformPDF.

● toImage not respecting ImageOptionSpecs.

● Customer’s PDF fails during flattening in 8.2.

● A particular page in a PDF file cannot be converted to PNG format using ConvertPDFService.

LiveCycle Assembler● Assembler throws a NullPointer exception when PDF created using iText library is passed through

Assembler as file1.


● Assembler fails in overlaying text string on a large PDF file.

● Page links in original TOC are broken after inserting pages.

Livecycle PDF Generator ES● PDF conversions for valid TIFF fails a few times, after invalid TIFF is tried.

● Some of the custom fonts do not get resolved when Microsoft Office 2007 Word document is converted to PDF using .

● Excel file does not convert in PDF format. Error ALC-PDF-010-012 is produced.

● Bookmarks on Word file do not get converted when Japanese string is in file property.

● PDFG intermittently stops processing files from the watched folder.

LiveCycle Process Management ES● Wrong dates appearing for stalled processes in LiveCycle Administration Console.

● Process shows UNKNOWN state in LiveCycle Administration Console.

● Sorting by “Process Completion Date” in Workspace Tracking works inconsistently.

LiveCycle Reader Extensions ES● Reader Extensions Flex App requires Accessibility enhancements.

LiveCycle Rights Management ES● Behavior defects after creating a domain with 50 double-byte characters.

● Kerberos authentication involving trust relationship between multiple domains fails.

● Find direct group member.

● Workspace ES error “Connection handle has been closed and is unusable” - Production issue.

● Custom SPI unexpected behavior for cross-domain relationships.

● Issue encountered while copying and pasting within the protected file with change permission. See “Unable to copy content into a PowerPoint 2003 file...”

● Mouse cursor cannot be changed to a black cross when a protected Excel file is opened.

● The shortcut key function is not available with Office 2003 and it is not followed by Windows design guide.

● revokeLicense returns error while the same user can through .

● User’s policy does not respect off line view permissions.

● Exception occurs when specifying a large value in maxResult in RightsManagementService.getPolicies.

● Vulnerability: java script can be executed in email field of create policy screen.

● OCSP server's revocation info is not embedded during sign/certify operation.

LiveCycle Workbench ES● External API to retrieve Process ID from invocation ID is not available.

● XDP with broken WSDL connection freezes Workbench ES.

LiveCycle Workspace ES● Group Queue ToDo list does not update automatically.


● Workspace ES and Firefox 3 (compatibility issue).

● (Firefox 3 only) Complete button does not show up in REInterop workflow test cases when using Adobe Reader 8 or 9.

● New line character is not evaluated when a rendered form is saved as a draft and then reopened.

● Workspace ES user-search when forwarding a task is case-sensitive.

● Custom Fields do not get populated when a User Logs in the first time into Workspace ES and navigates to the Group Queue.

● Duplicate Queues created in Workspace ES when assigned-to Group does not exist and is created.

● Workspace ES not launching forms in IE when using the http://[serveraddress]:[serverport]/workspace?startEndpoint=[process_name].[endpointname] URL to start a process directly.

● A visible variable that is exposed as a column header in Workspace ES ToDo list is not updated properly.

● Authentication error: a problem occurred while creating the default queue for user “{0}”.

● Task cannot find form data in Workspace ES.

● ToDo list grid will display with multiple empty rows - Production issue

● Workspace ES is not updating ToDo list.

Documentation Issues● BAM component's check box will be in LiveCycle Configuration Manager (see article # KB408266.)

● Field format “rich text” not supported in HTML is not specified in product documentation.

Service Pack 3

Installation issues● TCP locator fails to start on Microsoft Windows Server 2003 64-Bit Standard Edition.

● A restart is necessary to propagate the changes made to one node in the trust store to the other nodes.

● After memory problems, a running user action is observed to have no task associated with it.

● A customer’s application server consistently returns SpyJMS exceptions.

● UMCacheService fails while starting up.

Upgrade issues● A customer encounters a NullPointerException while upgrading a process from LiveCycle 7 to

LiveCycle ES.

LiveCycle Configuration Manager● LiveCycle Configuration Manager fails with an error message at the database initialization step.

LiveCycle Administration Console● The <entry key="configInstance" and value=<domain name> entries do not get

deleted from config.xml when the corresponding LDAP domain entries are removed using .

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


● Failure to retrieve the canonical name of a group.

LiveCycle ES Connector for IBM FileNet● When a PDF file generated with LiveCycle ES is saved to a FileNet repository, the properties assigned

to the file prevent Adobe Reader from opening it.

● Failure when attempting to store a file in a FileNet repository using the connector.

● Failure to create a version of a document that already exists in the FileNet repository at the specified path.

● Performance issue with the LiveCycle FileNet repository connector.

LiveCycle Designer ES● Performance of is poor when adding a table of 10 rows and 11 columns to the collection.

● Designer ES crashes when a specific PDF file is imported into it.

● Designer ES crashes when objects in the form hierarchy are moved.

● Designer ES aborts unexpectedly when a customer form is loading.

● Designer ES crashes with an OutOfMemory error when an attempt is made to modify the custom tabbing order for a form.

● Designer ES crashes when an attempt is made to resize a text field on a customer form.

● A runtime error is encountered when running a guide using Flash debugger.

● A form does not have the correct traversal node and related attributes specified. The correct reading order, therefore, is not established from the tagged structure.

LiveCycle Digital Signatures ES● A customer is unable to use a workflow process to sign a PDF document that has been rendered

from digitally-signed XML data.

● An exception occurs when Java API is used to add a signature field to a PDF document.

● Unable to verify a signature with Online Certificate Signature Protocol (OCSP).

LiveCycle Forms ES● Repeater Accordion layout: When a subform containing an exclusion group is repeated, the layout

of the repeated subform is clipped at the exclusion group. Only the content above the exclusion group is repeated.

● generateTabIndex and styleGenerationLeveloptions need to be exposed for processFormSubmission.

● When rendering XDP as HTML using Forms ES 8.2.1.x, the presence property does not work as expected.

● When a customer’s PDF form is merged with its XML data, the imported data appears clipped.

● If an XDP template is rendered as a form guide and contains both an image and a form bridge, the rendering of the PDF fails in the background.

● An OutOfMemoryError is returned during the execution of the formsClient.processFormSubmission method when the submitted form has a large attachment (size greater than 20 MB).


● Root Cause Analysis: XMLForms repeatedly crashes on a node of a customer’s WebSphere cluster. This error is encountered when any form, including the default templates shipped with FormsIVS, is rendered as a PDF. A server restart does not resolve the issue.

● When rendering XDP as HTML/XHTML, the script to change the access property of a protected field does not work for the DateTimeField object.

LiveCycle Output ES● CIFS printing in Output ES prints extra characters and glyphs at the end of the output.

● CIFS printing in Output ES doesn’t support NTLMv2 network authentication.

● Conversion to PDF/A fails for forms having Hebrew text with the Arial font.

● Add the facility to print via Output ES without requiring all printers and print servers in the LiveCycle ES trust store to be declared.

● When an XFAF form is flattened using transformPDF, the size of the converted PDF is thrice the size of the form.

● If an XFAF form has an image whose relative path is specified, that path is not resolved when the form is rendered as a non-interactive PDF.

● A customer XFAF forms gets corrupted after flattening. Some of the text objects in the form do not appear in their correct locations. When an XFAF form is flattened using the transformPDF service, the converted non-interactive PDF does not have any data for the fields in the form whose font size is set to zero.

LiveCycle Assembler● Add support for server-side conversion to PDF/A-1b of documents having custom XMP schema

data.

● Assembler returns a PDFInvalidDocument exception when a customer tries to combine a particular PDF document with other PDF documents.

● The Assembler service fails to overlay a text string on a heavy PDF file.

● Inconsistent PDF/A validation results using LiveCycle ES 8.2.1 SP2 and Acrobat 9.1 Preflight.

● When empty strings are passed for Subject and Title in metadata, the current values of these elements are not emptied.

● Processing PDF files with an incorrect CreationDate format in the XMP metadata causes an error during Assembler run.

● Issues with Assembler while extracting attachments from a PDF. java.lang.NullPointerException and ZipException “incorrect data check” are encountered.

Livecycle PDF Generator ES● An “Unable to contact PDFMaker” error occurs inexplicably after several successful PDF to XML (or

.txt) conversions.

● PDF Generator ES does not consistently convert bookmarks settings in Microsoft Word documents.

● PDF/A 1bRGB compliance mismatch between PDF Generator ES and Acrobat.

● Error while trying to convert a Microsoft PowerPoint document having restricted fonts to PDF using PDF Generator ES and Microsoft Office 2007.

● TOC links are broken when a Microsoft Office 2003 document is converted to the PDF using PDF Generator ES.


● PDF Generator ES does not properly recognize all Turkish characters during OCR (optical character recognition).

● When Acrobat Image Conversion is used to convert TIFF files to PDF/A, the PDF/A compliance preflight test fails with an error message.

● Conversion of data in the PRO/E (Pro Engineer wildfire) format using PDF Generator ES 3D fails. PDF Generator ES logs erroneously indicate that the conversion was successful.

● A customer process fails when trying to access a subprocess that has an XML file as an input.

LiveCycle Process Management ES● Process variables values are retrieved from the process template and not from the process table.

Consequently, Workspace ES shows only the latest changes in the variable contents.

● Custom workspace login over SSL (https) fails with the following error message: “An error occurred while initializing Workspace ES.”

● When adding more than 30 notes, the alignment of the column “Added by” does not remain consistent.

● A custom component service fails to expose a web service endpoint.

● A customer is unable to submit a form opened in Workspace ES in the following scenarios:

● The form was forwarded by an AssignTask service.

● The form contains a required field.

● At least one attempt was made to submit the form with a required field empty.

LiveCycle Rights Management ES● Usability issue concerning Rights Management ES and 3D PDF: If a watermark overlays a 3D object,

it is difficult to click the 3D object.

● Storage space concerns: A new entry accumulates in the tb_job_instance table every time a policy protected file is opened.

● An exception is encountered while attempting to insert a duplicate key in an object.

● The [VIEW DOCUMENT] event is recorded twice in Rights Management ES when a user with insufficient permissions attempts to open a policy-protected PDF file.

● Microsoft Word 2007 crashes when a user tries to exit it after applying a policy to a .docx file and saving the file to a network share.

● When applying permissions via the encryption service API, using the .PASSWORD_EDIT_EXTRACT permission is not sufficient for exporting data from the PDF.

● An attempt to open a Word document stored on a Microsoft SharePoint 2007 portal returns a “Plug-in Installation Required” error even when the required Rights Management Office plug-in is already installed.

LiveCycle Workbench ES● Corrupted image in the process properties causes the Properties dialog box to not appear.

● An OutOfMemoryError is encountered when a customer tries to open the Components view in Workbench 7.x.

● The regular expression (.*)+\.csv$ does not seem to work with the FindFiles operation in Workbench ES 8.2.1. Workbench ES 8.2.1 uses DOS wildcard expressions such as “*.csv”.


● The configuration parameters for a process are cleared when it is saved. Consequently, submission activities are stalled unless the configuration parameters are added again using .

● An exception is encountered when an attempt is made to invoke the email service in Workbench ES configured for the Gmail SMTP server.

● The Email Receive operation fails with a connection error if one of the messages being retrieved has an invalid reply-to address.

● An exception start point does not work.

LiveCycle Workspace ES● Complete and some other Workspace ES buttons disappear intermittently.

● Cards disappear from the ToDo list when the call is made through a URL such as http://<server-name>:8080/workspace/Main.html?taskId=<id>.

● An intermittent security exception is encountered while logging in and logging out of Workspace ES as different users.

● The memory consumed by Microsoft Internet Explorer when using Workspace ES is not released.

LiveCycle ES SDK● The revokeLicense() method returns an error, even when the same user can successfully revoke

their document using the web interface.

● The error “Bad surrogate pair in string” is returned when a Japanese character is used in a string-length function.

● Add support for securing server-side web service calls for two-way SSL between trusted servers using X.509 certificates.

● Web service calls placed by LiveCycle ES to the customer back-end system seem to block threads, not releasing them to the pool.

● The renderPDFForm method appends “$FS_TIMESTAMP=1236785187538” to the file description.

● HTTPS is not supported while creating a BLOB datatype from a remote URL.

Documentation Issues● The documentation needs to mention that no tags are saved for forms with a flowable layout even

when the Save option in the form properties is set to “Generate Accessibility Information (Tags) for Acrobat (default)”.

● LiveCycle ES 8.2 documentation mentions the supported version of WebLogic Server as 10.1 MP1 instead of 10.0 MP1, which is the correct supported version.

● The Designer ES documentation needs to state that only one transparency color is supported for PNG images.

● The ReadMe file was updated to specify that SSO does not works for a domain when there are multiple domains on a LiveCycle ES server and SSO is enabled for all of them.

● The Programming with LiveCycle ES guide needs to be updated.

● The documentation for the Forms sample DataExtractionandUpdateDB at [LC HOME]\ LiveCycle_ES_SDK\samples\Forms\DataExtractionandUpdateDB asks the user to set the value of the Output variable. This step is not required.

Users should refer to the LiveDocs documentation for the sample instead of the documentation provided with the sample.

http://livedocs.adobe.com/livecycle/8.2/samples/wwhelp/wwhimpl/js/html/wwhelp.htm?&accessible=true


Service Pack 4

Installation issues● [Ref # 2742538] (Linux only) In console mode, LiveCycle 8.2.1 Service Pack 3 installer copies files

inconsistently.

● [Ref # 2801929] An com.adobe.idp.dsc.registry.OperationNotFound exception appears while deploying the new version of a custom component from a LiveCycle Archive (LCA) and as a result the custom component fails to deploy.

Upgrade issues● [Ref # 2396102] When you apply Service Pack 3, Administrator account for JBoss service on

Windows is changed to a local system account.

LiveCycle Administration Console● [Ref # 2591145] The LiveCycle Administration Console slows down while accessing Process

Management stalled operations.

● [Ref # 2754533]Processes are not updated in the LiveCycle Administration Console if the task is submitted from Workspace. The following exception appears in the logsorg.quartz.JobExecutionException: java.lang.Exception: com.thoughtworks.xstream.mapper.CannotResolveClassException: EventServiceContent : IDPSchedulerService_Worker-15Class name EventServiceContent from package not found. [See nested exception: java.lang.Exception: com.thoughtworks.xstream.mapper.CannotResolveClassException: EventServiceContent : IDPSchedulerService_Worker-15Class name EventServiceContent from package not found.]

● [Ref # 2584992] The Skip option in the drop-down list is not displayed when a user attempts to choose a process variable when setting up a search template in LiveCycle Administration Console.

● [Ref # 2525640] LiveCycle Administration Console slows down while accessing Process Management tasks.

LiveCycle User Management● [Ref # 2673031] New user passwords do not take effect even though the user receives a

password-update confirmation. This issue affects all users changing their password using the LiveCycle Administration Console.

● [Ref # 2612659] Issues with implementation of single sign-on(SSO) authentication result in the user being logged on with the credentials of another user.

LiveCycle Foundation

● [Ref # 2816557] Users observe some hung threads on the LiveCycle Server and the server requires a restart to complete processing. This happens when workflow DSC makes excessive and unnecessary updates to the cache every time a workflow is invoked. The objects cached are of type TemplateCacheEntry.

● [Ref # 2482259] Users observed that it could take few hours to process some events after installing quick fixes QF3.19. The tasks are completed but the associated actions stay in RUNNING state.

● [Ref # 2794054] The Quartz scheduler refers the wrong JVM property to determine if Quartz needs to be started in the clustered mode. The scheduler looks up the


-Dadobe.cache.cluster.locators property instead of the -Dadobe.cache.cluster-locators property.

● [Ref # 2588506] The expected output variable <elements maxOccurs =”1” minOccurs=”0”> does not appear in the Web Services Description Language (WSDL) automatically generated by LiveCycle on creating a process.

● [Ref # 2421650] Users encounter an exception while performing orchestration tests.

● [Ref # 2756140] Namespaces and SetValue QPACs in processes running under LiveCycle 7.x compatibility mode sometimes result in the stalling of the server.

● [Ref # 2756143] Users encounter an error while accessing files and folders from a repository if the file names or folder names contain spaces.

● [Ref # 2754535] User request to render a form from Output ES using a .NET front end application may sporadically fail. The following exception appears in the server logs:org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequired (com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.TransactionCallback)throws com.adobe.idp.dsc.DSCException, causedBy: com.adobe.idp.DocumentError: The document pointing to the file "path" has expired. Consider increasing the document disposal timeout.

● [Ref # 2404564] Users encounter The document pointing to the file XXX has expired.Consider increasing the document disposal timeout error message while creating a LiveCycle Archive (LCA) and the LCA creation fails.

● [Ref # 2826794] Joining fields of different data types in a database may cause significant degradation in performance of LiveCycle Workspace.

● [Ref # 2637783] On Linux, the ProcessPurge tool does not accept the special character “*” as a filter.

● [Ref # 2436822] The repositoryClient.searchRelated() API bypasses the Access Control List(ACL), making objects available to all users irrespective of the user rights settings, thus posing a risk.

● [Ref # 2612579] Terminating a child process using the LiveCycle Administration Console stalls an already completed action of the calling parent process.

● [Ref # 2832552] Some iterative customer processes, that repeatedly generate events as part of processing loop, iterate more times than expected that results in too many events and notifications.

● [Ref # 2430807] All the white spaces are removed from the subject line and the body of an email if the email is sent using the e-mail DSC’s Send with document task.

● [Ref # 2756138] Users cannot open, add, or edit an FTP component after migrating from LC7 to LCES 8.2.1.2.

● [Ref # 2756590] Secured server-side web service calls with X.509 certificates, for bi-directional SSL between trusted servers, not supported by LiveCycle.

● [Ref # 2404371] When using the “Add Item” component against the IBM Content Manager component in Workbench, repeating attributes are not displayed in the metadata list.

● [Ref #2545109] The IBM content Manager 8.4 attribute named ORIFNAME is not populated when the content is added through LiveCycle.


● [Ref #2514234] When the sendWithMapOfAttachments() method of the EmailService is used, all the attachments have the Content-type application/octet-stream instead of application/Document. Thus, the receiving process skips to import the attachments.

LiveCycle Designer ES ● [Ref # 2591130] An issue that resulted in a java.lang.LinkageError error while connecting to

WSDL through LiveCycle Designer data connection is resolved.

LiveCycle Forms ES● [Ref # 2872257] When an image is used more than once in a form, the form fails to render and Read

Timed Out exception is returned.

● [Ref # 2589023,2589023, 25890193] Data buffer overflow in Adobe Acrobat and Adobe Reader's BMP, JPEG, PNG, GIF formats could lead to memory corruption on server and compromise LiveCycle Forms ES security.

● [Ref # 2872262] When an Acrobat form is flattened, the Font object applies the font.strikeOut property on a table field. This is not the intended operation in a customer script.

● [Ref # 2338524] When a customer's Acrobat form is merged with XML Data, the imported data appears clipped.

● [Ref # 2415064] Intermittently, some customer forms rendered as HTML do not work as intended. For example, drop down lists are populated from hidden fields on the form.

● [Ref # 2447891] Data in the forms is not maintained when forms saved in Acrobat version 9 are opened with Acrobat version 8, or vice-versa.

● [Ref # 2740856] The Read-only entries in a drop-down list are modified when navigating through XHTML forms.

● [Ref # 2450819] Forms and validations are not displayed in frames when BorderValidation is specified in the option string.

LiveCycle PDF Generator ES● [Ref # 2630727] The conversion of a Microsoft Word file to PDF fails if the source file has long style

names.

● [Ref # 2291832, 2301279, 2408299, 2301279, 2291823] Processing PDF files with an incorrect CreationDate format in the XMP metadata causes an error during Assembler run.

● [Ref # 2630727] The page size of the PDF file is altered when converting a .TIFF file to the PDF format.

● [Ref # 2423503] Large TIFF image files appear cropped after they’re processed through LiveCycle PDF Assembler or PDF Generator ES.

● [Ref # 2679516] LiveCyle throws an exception when converting certain PDF files to the PDFA format using DocConverter. The document conversion fails.

LiveCycle Assembler● [Ref # 2782718, 2791333] LiveCycle Assembler freezes while merging multiple PDFs that contain

bookmarks and footers.

● [Ref # 2304465]The user encounters an error DDXM_W10001: Could not update metadata on out.pdf.com.adobe.internal.pdfm.metadata.MetadataException: PDFM_S10004: Metadata operation close failed while assembling a PDF that contains footers.


● [Ref # 2787822, 2757214] Some customer PDFs are assembled into a corrupted PDF. The Insufficient data for an image error message is encountered while browsing the assembled PDF.

● [Ref # 2356403] An Expected 'trailer': 9245 error message appears while assembling PDF’s. The Assembling happens without any error if PDF’s are re-saved using Adobe Acrobat.

● [Ref # 2356403] The user encounters message This PDF form requires a newer version of Adobe Acrobat.on opening PDF with Adobe Acrobat Reader 9.2 or 9.3.2. This may happen if PDF contains XFA Java Script.

● [Ref # 2754469] A customer form gets corrupted after flattening. Some of the text in the PDF appears displaced.

● [Ref # 2505452] LiveCycle throws an ArrayIndexOutOfBound exception when assembling a PDF file that has been created from a Microsoft Word file with long style names.

● [Ref # 2774616] A new font subset is added to every page in the assembled PDF thereby increasing the size of the PDF significantly. This happens when page numbering in Assembler embeds a new font for each page of the document.

● [Ref # 2438897] Users encounter "Font not embedded" and various other error messages while converting HTML document to a compliant PDF/A-1b format.

● [Ref # 2856853] The <No Header> operation fails while removing the header of a document. The headers are not removed.

● [Ref # 2671725] When a flattened PDF file is opened, Adobe Acrobat and Adobe Reader display a warning that prompts the user to download a newer version of the software.

● [Ref # 2774613] When header is removed from PDF file using <No Headers/> command, the size of the converted PDF is double the size of the original PDF.

LiveCycle Output ES ● [Ref # 2799319] In some of the XDPs, the vertical height of the diagonal lines was not equal to the

height of the row. It happened where some custom user scripts were used along with Output services to render XDP’s.

Livecycle PDF Generator ES● [Ref # 2446161] User encounters an invocation error while configuring watched folders when the

work files in watched folders are not picked-up by LiveCycle for processing.

● [Ref # 2451058] If the result column of the Watched Folder endpoint configuration is left blank, then the work files are processed from the watched folders. However, the data is not auto-purged from the staging folders.

● [Ref # 2754532] If Password Security is enabled while converting Microsoft Word or PS files to the PDF format, the Fast Web View is turned off in the converted file.

● [Ref # 2871776] LiveCycle Barcode Forms service may fail to decode barcodes from a TIFF image where the TIFF image is generated by scanning a printed AcroForm.

LiveCycle Process Management ES● [Ref # 2497849] After installing Service pack 3, items assigned via group queue do not appear in

Workspace without Refreshing or logging out and logging back in.

● [Ref # 2475077] Multiple instances of a process are invoked on initializing a single instance of the process during event throw and receive. The number of instances of a process is equal to the


number of versions of the process. For example, if a process has three versions, then three instances of the process are created.

● [Ref # 2659755] LiveCycle throws a 'Task not found' error when users open a group task using the URL in the task assignment email for tasks that have been completed.

● [Ref # 2581179] Documents with the word attachments in the document name open in the desktop application instead of the relevant browser window.

● [Ref # 2581534] Workspace ES freezes if the Claim and Open” button is clicked multiple times in Workspace. Users are not able to access anything in Workspace other than the PDF form.

● [Ref # 2527924] LiveCycle Workspace throws an exception, AssertionId [ID Number] is not valid, every time a user logs out. This may happen if sso session has expired.

● [Ref # 2776029] Unterminated String Constant error while opening a form in Workspace and the form fails to render. This happens after applying quick fix 3.115.

● [Ref # 2410460] Workspace attachments do not appear when a task is opened from a group. This happens when the process uses the Assign Task service to assign the task to group queue.

● [Ref # 2432943] If a table in a form guide contains a large number of rows, Workspace may fail to save the form guide as a draft.

● [Ref # 2385244] The Delete button appears while adding an exception in the Managing Out of Office section of the Workspace preferences page.

● [Ref # 2645245] Users encounter a No task found for task ID error when opening an attachment passed by another user. This happens when the XPath evaluation returns NULL for the variables that include a collection and variable of other types.

● [Ref # 2645297] Error message Error 500--Internal Server Error may appear when you search for processes by task ID when the process name is empty or NULL.

● [Ref # 2583832] The ShareTask service returns an exception if its calling event refers to a task that is already complete.

● [Ref # 2583934] Users encounter a NullPointer exception while using the LiveCycle 7 createtask()method in LiveCycle ES.

● [Ref # 2756151] When you run LiveCycle 7.x processes that have branches containing forms in LiveCycle 7.x compatibility mode, some of the forms in Workspace do not display data properly.

● [Ref # 2583968] Users encounter an UnknownValue exception when the TaskManager.addAttachment() method is called.

● [Ref # 2585165]Updated properties of search templates are not reflected in Workspace.

● [Ref # 2485021] Users encounter an Inbox account is used by the other endpoint. Each endpoint must have different Inbox accounts error while creating multiple email endpoints pointing to diffrerent users.

● [Ref # 2477889, 2852389] Users encounter an error message An error occurred submitting the form. (ALC-WKS-007-074) on submitting forms opened from a mini-card. Even though the data is saved to drafts, the form is not submitted.

● [Ref # 2581582, 2561619] The drop-down list of To-Do tasks is not updated to reflect a claimed task if the last claimed task belongs to a different process.

● [Ref # 2459388] Users are not prompted to either confirm or cancel discarding an unfinished task when switching to another task on the mini-card.

● [Ref # 2505645] Form data is lost when the web browser stops responding. This issue occurs despite the user having saved the data as a draft.


● [Ref # 2756148,2591151] The list of processes that were initiated by a user in a previous Workspace session is not alphabetically sorted when the user logs back on to a new session.

● [Ref # 2756172] Users do not receive process assignment notifications when a process is assigned to a group consisting of more than 10 users.

● [Ref # 2755596] Process modifications saved as an LCA in the stage environment are not reflected when the LCA is imported into the production environment. This happens if the version number of the edited process is not incremented.

● [Ref # 2673605] (org.jgroups.protocols.CAUSAL$CausalHeader) is already in map; please make sure that all magic keys are unique error message and JGroups fails to initiate when Workspace is launched.

● [Ref # 2632975] Users encounter a com.adobe.idp.workflow.dsc.service.ProcessManagerService exception while using the ProcessPurge tool to purge completed and terminated processes.

● [Ref # 2763442,2763990] Completed processes that have QPACs in compatibility mode are incorrectly listed as running.

● [Ref # 2756134] Task completion dates are reset to the server migration date when migrating from LC 7.0 to ES 8.2.1.2.

● [Ref # 2591135] javax.ejb.TransactionRolledbackLocalexception is thrown when AttachFileToTask QPAC is used in LiveCycle compatibility mode.

● [Ref # 2849119] A user process using the default Submit service to send the form and data to the server creates enormous amount of data in GDS. The data never gets deleted although it is tagged as DeleteMe.

LiveCycle Workspace ES● [Ref # 2437987] Possible post-authentication redirection to unintended URLs could compromise

Workspace ES security.

● [Ref # 2473547] Tabs on the search template definition page stop responding on deleting any template.

● [Ref # 2591132, 2591140] Some of the words in the preferences view of the Workspace ES were not translated correctly into French.

● [Ref # 2477886] Users encounter a Cannot access a property or method of a null object reference error message while returning a received task. The task appears as returned if the exception window is cancelled.

● [Ref # 2581556] User encounters The attempt to claim task has failed. error while claiming an already claimed task and a duplicate tasks appear in the queue. This may happen if the group queue is not updated immediately after another user has claimed the task.

● [Ref # 2501646] LiveCycle throws a ClassCastException exception when loading a task list into the workspace.

● [Ref # 2363028] Due to duplicate user entries in the database, tasks do not appear in Workspace after migration from LiveCycle 7.x to LiveCycle ES Update 1.

Content Services ES and Contentspace ES● [Reference #2512154] Dynamic PDF forms in Contentspace ES are not searchable. However, static

versions of these forms are returned in search results.


LiveCycle Workbench ES● [Ref # 2756130] Users encounter a SAXParseException exception while migrating from

LiveCycle 7.x processes to LiveCycle 8.2.

● [Ref # 2541583] The user observed that, in Workbench, the editor dialogue box appears twice when editing SetValue properties. This happens when user is migrating from LiveCycle 7.x to LiveCycle ES.

● [Reference #2756123 ] An Out Of Memory error is encountered when a customer tries to view third-party Quick Process Action Components (QPACs) in the LiveCycle 7.x Components view in Workbench ES. The customer has tried, without success, to resolve this issue by increasing the value of -Xmx from 1024 to 2048.

● [Reference #2436805] Workbench caused out of memory issues on the LiveCycle server when Components are refreshed a few times.

● [Reference #2630041] Workbench fails to import or open a workflow because of negative coordinates.

LiveCycle Services ● [Ref # 2852561] The certifying signature breaks when another signature is applied to the

document. The following error message is observed:

“Document Certification is Invalid. The document has been altered or corrupted since the Certification was applied.”

● [Ref # 2790023] An error is encountered while rendering an XML form in the "Pattern Matching Rules" mode.

● [Ref # 2487366] Enhanced security features of Acrobat Reader 8 and 9 causes issues with displaying SHA-1 Hash fingerprint.

● [Ref # 2651705] LiveCycle throws an error <faultcode>soapenv:Server.userException</faultcode> <faultstring>org.xml.sax.SAXException: No deserializer for {http://www.w3.org/2001/XMLSchema}anyType</faultstring> when running a 'testQueryMultipletoXML' soap request and fails to execute the request.

● [Ref # 2393020] WebDav sessions time out very frequently, resulting in prompts for the user to log back in.

● [Ref # 2393703] File creation is disrupted on Content Services when renaming the file using setContentAttributes and a custom-provided map.

LiveCycle Core

● [Ref # 2657416] LiveCycle throws GDS expiration errors in the Administration UI and 'DuplicateApplicationException' exception when deploying LCAs in LCM.

Documentation● [Ref # 2676186] The product documentation does not state that the data store helper class needs

to be configured as MicrosoftSQLServerDataStoreHelper when using the SQL Server JDBC driver v1.2.

● [Ref # 2847228] When using DB2 for your LiveCycle ES2 database, the maximum permitted length of the space name is 50 characters (25 if unicode or non- ASCII characters are used).


Enhancement (Added Feature)● [Ref # 2754530] Users are provided with the facility to access the printers on a different domain

although there is no trust relation between the domains.