Archive for December, 2010

LiveCycle ES2: ALC-FDI-001-305: Operation aborted: Malformed input PDF or data

Issue

 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.

Reason

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.

Solution

This issue has been addressed in LiveCycle ES2 SP1 and later versions.

reference: (181504595/2591446)

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

Acrobat/Reader 9: Privileged locations from Customization Wizard written to incorrect registry keys

Issue

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.

Solution

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.

Additional information

The privileged hosts are written incorrectly to:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\9.0\FeatureLockDown\TrustManager\cTrustedSites

instead of:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\9.0\FeatureLockDown\cTrustedSites

reference: (181708423/2678020)

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

Acrobat/Reader 9: HTTP submit button does not open local files

Information

Security restrictions in Adobe Reader and Acrobat 9 restrict you from opening local files (Excel, Word, and so on) from within a PDF using Javascript (launchURL).  This action poses a security risk for the PDF file, and could allow dangerous files to be opened, and a script to be executed.

In previous versions of Acrobat or Reader (before 9.0), you can point the HTTP Submit button to a file:// URL on a network/local file system. The local file was “downloaded” using the browser’s plug-in. This behavior is not the intention of the HTTP Submit button. So, it’s been locked down in Acrobat and Reader 9 and later.

The HTTP submit button is used to send the form’s data to a server once the form has been filled. The resulting PDF can then be displayed to the user.

To reference or open local files from a PDF, run the PDF file in a privileged context (in the Javascript console or in a batch process). Or, certify the PDF file.  If you are running Acrobat or Reader in a browser context, you could put the local file on a web server and use the HTTP URL.

You can find more information to this security restriction under “app” and then the “methods” tab, and then under the launchURL method:

http://livedocs.adobe.com/acrobat_sdk/9.1/Acrobat9_1_HTMLHelp/JS_API_AcroJS.88.150.html

Extract from the JavaScript Documentation:

Note: Beginning with Acrobat 8.1, file and JavaScript URLs can be executed only when operating in a privileged context, such as during a batch event. File and JavaScript URLs begin with the scheme names javascript or file.

reference: (181917275)

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

LiveCycle ES2: “The embedded font program ‘PZSWZL+CustomSymbol’ cannot be read.”

Issue

When you convert PDF files to PDF/A using LiveCycle ES2, and then validate the files with a PDF validator, you receive the following error:

The embedded font program ‘PZSWZL+CustomSymbol’ cannot be read.

The font PZSWZL+CustomSymbol must be embedded.

Validation in LiveCycle ES2 and Acrobat 8 or 9 validates the PDF/A without errors.  Validation with current validators such as Acrobat X Preflight, or 3 Heights PDF Validator produce the error above.

Solution

This issue is a problem in LiveCycle ES2 (9.0.0.0, 9.0.0.1, and 9.0.0.2) as it should also return an error that the PDF/A is invalid.  This issue is fixed in LiveCycle ES3 (LC10) and later.  There is a patch available for ES2 SP1 and SP2, so contact enterprise support if you require one of these patches.

Additional information

PDF 1.4 recognizes only the following cmaps for TrueType fonts:

  • cmap subtable with platform ID 3 and encoding ID 1 (Microsoft Unicode, also called  [3,1])
  • cmap subtable with platform ID 1 and encoding 0 (Macintosh Roman, also called [1,0])

In this case, the PDF file was using a custom font CustomSymbol that contained a (3, 0) cmap subtable, which PDF 1.4 doesn’t recognize.  Therefore, Acrobat X and other PDF/A validators correctly reported an error when checking for PDF/A-1b compliance (As PDF/A-1b is based upon PDF 1.4).

reference: (181779161/2714061)

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

Acrobat/Reader 9: Error “This document enables Reader capabilities that are no longer enabled…”

Issue

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:

 

Solution

Reader-enable the PDF files again using a later version of the ReaderExtensions server (that is LiveCycle 7, or ES).

Additional information

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:

http://www.adobe.com/products/livecycle/upgrade/readerextensions.html

reference: (181907091)

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