While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form.  If you then click Save, it again offers to reload the current form.  After clicking “Yes” to reload the form, you may notice that Designer hangs.

Method:
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes

Result:
Designer hangs

Solution

This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.

reference: (183667516/3337854)

If you are importing a multi-page PDF into LiveCycle Designer ES2 to create a form using the “…Flowable Layout > Place Content In > Master Pages” method you may notice that the content of the pages are placed in a single Master page causing overlap.

Solution

This is an issue in LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

reference: (183629724/3337453)

If you are editing older XDP forms from LiveCycle Designer 7.1, or 8,  in Designer ES2, and you have hidden rectangle objects in the form design, you may notice that when selecting these hidden objects in the hierarchy, visible corners suddenly appear on these objects.  These hidden rectangle objects are created automatically when importing Word documents into Designer to create a form.

Reason

The problem is caused by the import from doc/PDF where the edge property for the rectangle is created and set to hidden, but no corners property is created.  When you create a new form in Designer (without importing), the edge and corner properties for a rectangle are always created together and the presence for both usually kept in synch.
It seems that when Designer finds a rectangle without a corner property it creates it automatically with visible corners.

Rectangle in XML after import from word:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
               </rectangle>

Rectangle in XML after selecting it on canvas:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm”/>
               </rectangle>

Rectangle in XML after manually fixing it in Designer (XML Source or Object Palette):
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm” presence=”hidden”/>
               </rectangle>

Workaround

You can change the line style to “solid” and back to “none”, and then the corners property in XML is synchronized (presence=hidden) with the line edge property as expected.

Solution

This is an issue in LiveCycle Designer ES2 and will be fixed in Designer 10 and later versions.  If you require a quickfix for Designer 9 you should contact the enterprise support team.

The logic has now been changed, so that when Designer creates the corner property, it checks if the relevant edge is hidden, and sets the presence for the corners to match.

reference: (183589079/3322036)

If you are using LiveCycle Content Services you may notice the following error message in the server logs when starting the server:

00:05:55,646 ERROR [org.alfresco.service.descriptor.DescriptorService] Error installing embedded license
org.alfresco.service.license.LicenseException: Failed to save license
                at org.alfresco.repo.descriptor.RepositoryDescriptorDAOImpl.updateLicenseKey(RepositoryDescriptorDAOImpl.java:294)
                at org.alfresco.enterprise.license.AlfrescoLicenseManager.setLicenseKey(AlfrescoLicenseManager.java:220)
…
Caused by: org.alfresco.service.cmr.repository.ContentIOException: Failed to create directory for file storage: \\share\Adobe\lccs_data\contentstore\2012\10\26\0\5
                at org.alfresco.repo.content.filestore.FileContentStore.makeDirectory(FileContentStore.java:288)
                at org.alfresco.repo.content.filestore.FileContentStore.createNewFile(FileContentStore.java:234)
                at org.alfresco.repo.content.filestore.FileContentStore.createNewFile(FileContentStore.java:202)
                at org.alfresco.repo.content.filestore.FileContentStore.getWriterInternal(FileContentStore.java:478)
                at org.alfresco.repo.content.AbstractContentStore.getWriter(AbstractContentStore.java:242)
                at org.alfresco.repo.content.RoutingContentService.getWriter(RoutingContentService.java:402)
                at org.alfresco.repo.descriptor.RepositoryDescriptorDAOImpl.updateLicenseKey(RepositoryDescriptorDAOImpl.java:285)
                … 15 more
03:00:00,020 ERROR [org.quartz.core.JobRunShell] Job DEFAULT.indexBackupJobDetail threw an unhandled Exception:
org.alfresco.repo.security.permissions.AccessDeniedException: Access Denied.  The system is currently in read-only mode.

Reason

This error can occur when the user account that started the application server (JBoss/WebSphere/Weblogic) no longer has “write” permissions on the lccs_data shared directory used by content services (alfresco).

During startup sequence, Alfresco tries to create files in lccs_data shared directory, and if it cannot, it starts content services in read only mode.

Solution

Verify the user rights on the shared lccs_data directory, and try to create a folder/file manually.  Restarting the LiveCycle server will usually resolve the problem, but you should investigate the root cause why the user permissions are being lost in your environment.

After updating to LiveCycle Designer ES2 QF4 (9.0.0.2.20110401.1.827986), you may notice that you are no longer able to delete the default value in rich-text fields.  It is possible to edit the value, but when you delete it, the value will re-appear in the field after refreshing.  This only happens for rich-text fields and not standard text fields.

Solution

This is an issue in LiveCycle Designer 9.5 QF4 and has been addressed in later versions, including Designer 10.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

Workaround

You can delete the default value by opening the XML Source tab and removing the value manually.

reference: (183571067/3318438)

If you are using TCP locators in a LiveCycle cluster with ES3 (10.0.2) and have installed a service pack or patches on top of this version, you may notice some errors in the server log similar to the following:

com.adobe.livecycle.cache.CacheRuntimeException: Error loading cache configuration
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.getCacheContainer(GemfireCacheAdapter.java:164)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.createRootRegion(GemfireCacheAdapter.java:853)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.init(GemfireCacheAdapter.java:218)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.<init>(GemfireCacheAdapter.java:207)
at com.adobe.livecycle.cache.adapter.CacheAdapterFactory.getCache(CacheAdapterFactory.java:103)
…
Caused by: com.gemstone.gemfire.SystemConnectException: Attempt to connect to distributed system timed out

If you have a UDP-based cluster caching mechanism, you are not affected by this issue.

Reason

This issue occurs when the Gemfire version on the server is different from the Gemfire version used by the TCP locators.  Gemfire.jar and GemFireVersion.properties are delivered in two different places in the LC installation – 1. Core EAR 2. /lib/caching directory.

Gemfire version 6.5.1.17 was used for LC ES3 (10.0.2).  To address some known issues a new Gemfire version (6.5.1.35) was used in later versions and patches.  This newer Gemfire version was used for the Core EAR, but unfortunately not included for updating the caching directory.

To verify the issue, compare the Gemfire version in the GFLocator.log file for your TCP Locator with the Gemfire version in the Gemfire logs for your application server at the following location:

• JBoss: <adobe_temp_dir>/adobejb_<server_name>/caching/Gemfire.log
• Weblogic: <adobe_temp_dir>/adobewl_<hostname>/caching/Gemfire.log
• WebSphere: <adobe_temp_dir>/adobews_*/caching/Gemfire.log

You will find that Gemfire on the LiveCycle server has a higher version.

Solution

This issue has been addressed in SP2 and later patch versions.

Note: the patch installer will only update the default caching directory (<lc_install_dir>/lib/caching) on the machine where LC is installed.  If you are running LC on various machines, and/or use custom caching directories, you will need to update the 2 Gemfire files for your TCP locators manually.  All TCP locators need to be restarted before starting LC servers.

Workaround

For existing patches you can use the following workaround to fix the issue on your LiveCycle installation.

1. Stop the LiveCycle server(s).
2. Stop the TCP Locator(s).
3. Go to <LC_INSTALL_DIR>/deploy folder.
4. Open adobe-core-<appserver_name>.ear.
5. Go to TCP locator installation directory. Typically the default location is <LC_INSTALL_DIR>/lib/caching.
6. gemfire.jar and GemFireVersion.properties can be found here.
7. Replace the two files above in the TCP locator with the same files from the core ear.
8. Repeat the replacement procedure (steps 5 – 7) for each TCP locator.
9. Start TCP Locator(s).
10. Start LiveCycle server(s) in the Cluster.

Verify the Gemfire versions in GFLocator.log and Gemfire.log files. You should see the same Gemfire version in both files.

reference: (183615151/3327651)

With the latest release of Adobe Acrobat/Reader XI there is a new feature available for structuring text in rich-text fields in XFA-based forms.  You can now add/modify tab-stops in rich-text fields using new UI components.  Adding tab-stops in rich-text fields allows for better formatting and table-like structuring of the text, which is a much requested feature from customers and users.

Instructions

You download the sample file tabstops_richtext_field_dyn.pdf to see how this feature works.

1. Open the sample file in Acrobat/Reader XI.

2. Place the cursor in the large rich-text field.

3. Press CTRL+E on the keyboard to bring up the Form Field Text Properties toolbar.

4. Click the button “More…”

5. You will see the new Tabs dialog where you can create/modify the tabs in the field.

6. From here you can create/modify/delete the defined tab-stops, and change the alignment (Left, Right, Center, Decimal), or the position.

Notes

You can now also use the key combination CTRL+TAB on the keyboard to tab between tab-stops in the rich-text field.

The measurement units for the tab stops are inherited from the units defined in the Preferences (Edit > Preferences > Units & Guides > Page & Ruler Units):

If you are attempting to save an XDP file in LiveCycle Designer ES2, created with an earlier version of Designer (i.e. 7, 7.1 or ES), then it can occur that the Save process never completes, and you must kill the Designer process manually in Task Manager.  If you analyse the files on your local disk, you will notice some tmp files with large file sizes.

Reason

This issue is related to the Data Binding option Allow binding to data not defined by the default data connection.  For some forms that contain data connections, Designer ES2 can get stuck in an endless loop while saving the XDP to an intermediary tmp file.  You will see the tmp file will contain a huge number of repeated entries related to the DataDescription similar to the following:

<DATACONNECTION xmlns:dd=”http://ns.adobe.com/data-description/” dd:additions=”$template(DATACONNECTION)”/>

---

Read the complete post at Adobe LiveCycle Blog.

If you are using LiveCycle Designer ES2 to import Microsoft Word documents from MS Word 2010 or later, you may receive the following error

Word (version XP or onwards) could not be found on the machine

Reason

This error occurs because LC Designer ES2 does not recognise the installation folder for Microsoft Word 2010 or later versions.  LiveCycle Designer ES2 was released before these versions existed and therefore the installation folders were not known/recognised.

Solution

This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.  Ensure you are using the latest QF for Designer ES2, or request the latest from your support representative.

If you require an urgent fix for this issue you can make the following change in the registry:

Note: we cannot provide support for any problems that may arise as a result of modifying the registry.  Only an experienced user or an administrator should attempt this, and a full registry backup should be performed before making changes.

1. For 32-bit Windows:

• Create the following path in the registry:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Word\InstallRoot
• Create a new string value named Path with value C:\Program Files\Microsoft Office\Office14\

2. For 64-bit Windows

• Create the following path in the registry:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot
• Create a new string value named Path with value C:\Program Files (x86)\Microsoft Office\Office14\

You should check the installation folder used in the Path value exists and contains WINWORD.EXE.  You will need to restart LiveCycle Designer for the changes to take effect.

Additional information

This issue is also being discussed in the forums:

http://forums.adobe.com/message/3983628

reference: (183608560/2751566)

If you are using LiveCycle RightsManagement ES2 SP2 (9.0.0.2) to apply policies to documents, and you have selected the option “Encrypt all document contents except metadata” in the policy, you will notice that the metadata is encrypted by mistake.

The option to omit the metadata from encryption can be configured when creating the policy as described below (Unchangeable Advanced Settings > Document Restrictions):

http://help.adobe.com/en_US/livecycle/9.0/rightsMgmtHelp/help.htm?content=000273.html#1604485

---

Read the complete post at David's blog.