Archive for October, 2010

LiveCycle ES2: barcode visible in PDF file converted to Postscript

Issue

When you use the ConvertPDFService toPS2() operation to convert PDF documents to Postscript in LiveCycle ES2, barcodes are appearing in the PostScript file which were hidden in the original PDF. This issue can occur especially if you used the legacyToSimplePSFlag to convert static documents directly, without flattening them first.

Solution

This issue is a bug in LiveCycle ES2 SP1 and SP2 and has been resolved in a patch.  Contact Enterprise Support if you require this patch for ES2 SP1 or SP2.  Adobe plans to fix this issue in the ES2 SP3, later versions.

You need to set GenerateServerAppearances=true to in the Form render settings when rendering the PDF forms and use the legacyToSimplePSFlag in the PSOptionsSpec for the Postscript conversion to work.

Additional information

 The problem only occurs for pre-generated PDF files which are then merged with XML data on the server side.  The document flow is as follows:

  1. XDP template gets rendered to PDF.
  2. The PDF can then be merged with data on the server, filled and signed by the user.
  3. The PDF is converted to PostScript.

In the input PDF, the barcode value is empty and hidden as expected. When the PDF is converted to Postscript with ES2 SP1, the barcode gets assigned a default value of “123456789…” Therefore, the barcode becomes visible on the resulting PostScript file.  The Postscript file from LC7 works correctly and the barcode remains hidden.

reference: (181754483/2702011)

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

Acrobat/Reader: International registry keys being accessed too many times

Issue

When you open a PDF file in Adobe Acrobat/Reader you may notice that the client reads the following registry keys repeatedly:

HKEY_USERS\…\Control Panel\International\sDecimal

HKEY_USERS\…\Control Panel\International\sThousand

The result of reading these keys if often BUFFER OVERFLOW.  It’s unnecessary for Acrobat/Reader to access these registry keys multiple times when opening a single PDF file. If you’re using Terminal Server environments, where only one client services multiple users, this issues can lead to performance degradation.

Solution

Update to Adobe Acrobat/Reader 9.4 or X.

Additional information

It’s common for a BUFFER OVERFLOW to occur when reading registry keys on application startup. This error doesn’t necessarily point to a memory issue in Acrobat/Reader. Adobe Acrobat/Reader 9.4, X and later have been updated to access these keys only once when opening a PDF file. The number of BUFFER OVERFLOW events is therefore also reduced.

 reference: (181470806/2596701)

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

Reader 9.1: registry persmissions modified causing issues with Internet Explorer

Issue

Installing Reader 9.1 modifies Registry permissions for key HKEY_CLASSES_ROOT\Interface\{34A715A0-6587-11D0-924A-0020AFC7AC4D} from “Full Control” to “Read“.  This modification prevents a successful installation in enterprise environments where customized installer files are used. The mentioned key is a part of the Internet Explorer installation and applications that work with the web browser events use it.

The Access Control List for this key before installation is as follows:

BUILTIN\Users=Read

BUILTIN\Power Users=Special

BUILTIN\Administrators=FullControl

NT AUTHORITY\SYSTEM=FullControl

CREATOR OWNER=FullControl

Following installation it has been changed to:

BUILTIN\Administrators=Read

NT AUTHORITY\SYSTEM=FullControl

Everyone=Read

Solution

Upgrade to Adobe Reader 9.4 or Adobe Reader X.  Do a full installation of one of these versions to apply the fix.

As a workaround, you can modify the MST file with Customization Wizard to prevent the permissions on this key being changed.

reference: (181120121/2356114)

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