LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

Issue

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)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.5/10 (10 votes cast)

LiveCycle Designer ES2: Unable to save old XDPs with external data binding option

Issue

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)”/>

Solution

This issue has been fixed in LiveCycle Designer ES3 and later cumulative QuickFixes for Designer ES2.  You should ensure you are using the latest QF for Designer ES2, or contact your support representative.

Workaround

Removing the data connection will allow the file to be saved, and also disabling the option in the form properties Allow binding to data not defined by the default data connection.  Also putting the sample XML data/schema file used to create the data connection into the same folder as the XDP, opening the XDP, refreshing the Data connection, will then allow to save properly.

reference: (183464630/3296440)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 5.5/10 (2 votes cast)