When you use the FormDataIntegration Service in LiveCycle ES2 to merge XML data into a PDF file, you may encounter the following exception:
2010-03-29 14:58:31,885 ERROR [com.adobe.livecycle.formdataintegration.client.ImportFormDataException]
ALC-FDI-001-305: Operation aborted: Malformed input PDF or data.
2010-03-29 14:58:31,964 ERROR [com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker]
An exception was thrown with name com.adobe.livecycle.formdataintegration.client.ImportFormDataException message:
ALC-FDI-001-305: Operation aborted: Malformed input PDF or data. while invoking service FormDataIntegration
and operation importData and no fault routes were found to be configured.
This exception occurs only for certain PDF files and other XML datasets cause the same error in the PDF file. However, you can use the same data XML in other PDF files without error. There are no visible problems in the PDF file, and no problems reported by Preflight.
This error occurs because of a bug in our Gibson library. Gibson doesn’t correctly handle a rich text field with an empty body element as value.
This issue has been addressed in LiveCycle ES2 SP1 and later versions.
When you use Customization Wizard 9 to configure the installation for Adobe Reader or Acrobat 9, hosts for privileged locations are written to the wrong registry location. Therefore Acrobat or Reader won’t recognize them at runtime and these sites will not be trusted. You could see the Yellow-Message-Bar warning about untrusted site access if these hosts are referenced from a PDF file.
This issue is resolved in Customization Wizard 10, so privileged locations are written correctly in Acrobat and Reader X. Adobe doesn’t issue patches for Customization Wizard, so there’s no way to fix this issue retrospectively for Acrobat or Reader 9. As a workaround, you can change the keys manually in the registry. Or, you can enter the values directly in the enhanced security settings in Acrobat or Reader preferences.
The privileged hosts are written incorrectly to:
When you open PDF files that are Reader-enabled using Reader Extensions server (version 5 or 6) in Reader 9 or later, you receive the following error:
Reader-enable the PDF files again using a later version of the ReaderExtensions server (that is LiveCycle 7, or ES).
This error occurs because Adobe Reader 9 no longer supports the ubiquity technology provided by ReaderExtensions server version 5 or 6.
Extract from: http://en.wikipedia.org/wiki/Adobe_Acrobat
“Adobe Reader 9 drops support for Adobe Reader Extensions 5 and 6 which permit Adobe Reader client software to save changes to filled-in forms in PDFs. Adobe Reader Extensions 6.1 and newer are still supported. Legacy PDFs are still viewable, however they open with the warning “This document enables Reader capabilities that are no longer enabled in this Reader version.”
This change in discussed in the Reader Extensions upgrade information on adobe.com: