Posts in Category "General"

Acrobat/Reader 9: properties toolbar doesn’t work in docked mode


When you try to edit a rich-text field in Acrobat or Reader 9 with the properties toolbar in docked mode, the toolbar is dimmed or displays “No current selection.


Undock the properties toolbar and use it in floating mode.

Additional information

This issue occurs if the properties bar was already docked when you opened the document. If you open the properties toolbar and dock it after opening the document, then it works only for the current document. In Acrobat X and Reader X, it is no longer possible to dock the properties toolbar in the user interface, so this issue cannot occur there.

reference: (181750120/2615060)

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

Acrobat/Reader: suppress the dialog after signing a PDF with a PenPad


 If you are using a PenPad to sign PDF documents in Acrobat or Reader you will receive the following dialog after successfully signing the document:

You may wish to disable this dialog permamently to avoid it displaying to the end-users.


 You can allow the dialog to appear once, and the users can then select the checkbox “Do not show this message again“.  Alternatively you can add a registry key which will disable this dialog permanently:

HKCU\Software\Adobe\Adobe Acrobat\10.0\AVAlert\cCheckbox\cppklite\isignDone REG_DWORD, 1

reference: (181681026/2662231)

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

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


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).

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:

“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

reference: (181907091)

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

Acrobat/Reader 8: Typewriter tool deactivated after each use


The Typewriter tool in Acrobat or Adobe Reader 8 is deactivated after each text entry that you make in a PDF file. You have to select the Typewriter tool for each text entry you make.

In Acrobat and Reader 7, the Typewriter tool remains active until you manually deactivate it, or select another tool.


Update to Acrobat or Reader 9.  The typewriter tool has been fixed and will remain active.

reference: (181558742/1553038)


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

Acrobat/Reader 8.1: crash when using the spell checker


If you are using the spell checking tool with Adobe Reader 8.1.x you may experience an application crash and error message like the following:

The crash usually occurs when you enter text in a text field that is not already in the dictionary. You then right-click on the text field to bring up the spell checking context menu:

Without selecting any of the options in the spell checking menu, you click another field on the form. Then the crash occurs.


This crash has been fixed in Reader 8.2.x and in Reader 9.  Upgrade to these, or later versions to solve this issue.

reference: (181290014/2495783)

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

Acrobat/Reader 8: PDFs rendering or behaving differently

If you have upgraded from Adobe Reader 7 or earlier to Adobe Reader 8 or later, you notice some differences in the PDF behavior. For example,

  • Form events not fired in the same order, or with the same frequency (particularly the layout:ready event). As a workaround, you can move the script to another event in Designer (for example, form:ready).
  • Text is shifted or clipped
  • PDF field values are modified (particularly checkbox and radio-button values)
  • Tabbing order is different (read-only fields are included in the tabbing order). As a workaround, set the field property in Designer to “protected” instead of “read-only“.

These differences result from a change in the rendering engine in Adobe Reader 8 and later.  The rendering engine was redeveloped to improve performance of large dynamic forms (100+ pages). The rendering engine in Adobe Reader 8 and later uses direct or AGM rendering. Some of  the changes mentioned above (form events, tabbing order) are side-effects of the rendering engine modifications, and others (text-clipping, field values) are product issues. The side-effects have known workarounds as outlined above, whereas the product issues have been addressed in the subsequent versions of Reader (8.2, and 9.3).

If you encounter other issues not mentioned above, and you want to restore the behavior from Adobe Reader 7, you can use a compatibility flag. The flag instructs the rendering engine to use the legacy engine from version 7.  Place the following flag in the XML source:


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

How to load dynamic images in a PDF file using Adobe Reader/Acrobat 8+


When you change the href property in a PDF form at runtime, images no longer load dynamically in Adobe Reader/Acrobat 8 and later versions.


Here are some suggested workarounds used in different situations to get avoid this issue:

  • Solution 1: Embed the images in the form as hidden objects.
  1. Add the image to the form in Designer, and set its presence to “hidden” in the object panel.
  2. Then set the image field’s presence to “visible” on the “initialize” event, or the “click” event of a button.
  3. Repeat for each image that you want to use on the form.

Note: This solution is only applicable when you use a few images. This solution affects performance, but if the images are in a compressed format, the effect can be minimized.

  • Solution 2: Upload the images as attachments.
  1. Do one of the following to upload the images as attachments:
    • Use the attachment panel in Acrobat (View > Navigation Panels > Attachments > Add).
  2. Update the value of the image field using script at runtime to point to the attachment. (See the “Opening and saving attachments” section in the Javascript scripting guide)
  • Solution 3: Use either a web service or a database connection.
  1. Configure a web service or database connection to return a string that contains Base64-encoded image content. (To build a web service or a database connection is complex and requires some custom coding, so it is out of the scope of this blog entry.)
  2. Open the form in Designer and go to the “Data View.”
  3. Add a new Data Connection.
  4. Select OLEDB Database, or WSDL file. (Press the Help button on this dialog in Designer to get more context help on how to configure each data source.)
  5. Add an image field to the form.
  6. Go to the Object panel and set the Binding for the image field to the return object from the web service or database.
  • Solution 4: Use the Privileged folders functionality in Acrobat 9+.
  1. Put all the images in a folder on a network share, available to all computers that access the form.
  2. Open the enhanced security settings in Acrobat/Reader 9 (Edit > Preferences > Security (Enhanced)).
  3. Add a folder path or the host name where the images are stored. The folder path tells Acrobat/Reader 9 that the path for the images is exempt from the enhanced security settings.

Note: Only try this solution after approval from your system administrator. You are essentially disabling some of the security features of Acrobat or Reader, which are there to prevent potential hacker attacks.

Additional Information

There were a few reasons for this change in the security settings:

a) A form could point to a “file://” URL for data mining purposes.
This condition allows for potential hacking as external parties see where the pictures are stored, and the names of the files on your computer. For example, they could see that the pictures were stored under My Documents\Pictures and that all had names like PIC000xx.JPG.

b) PDF documents are supposed to be self contained.
Pointing to an “ftp://” or “http://” URL to load an image dynamically breaks that promise. When a user certifies a document for example, the user certifies that the content of the document is safe. However, if the document dynamically loads an image, that image file stored on some web server can be changed without breaking certification. But, the meaning of the document can be different.

Consider the following situation where the content of the PDF reads:

You owe me:


…but could be changed to…

You owe me:


….just by changing the image on the server.

c) The same issue could appear with a signed document.
If you sign the document, you are signing the form in its current state and agreeing to the content as it stands. If the image on the server changes afterwards, the signature would still be valid. As some Adobe customers use signatures in legally binding workflows, Adobe cannot allow the content to change without reflecting that in the PDF or the signature.

The strategy moving forward is to have encapsulated PDF files remain true to the PDF specification. If you find another workaround to allow the images exist outside the PDF, it is also likely that Adobe would disable it in some future version of Reader and Acrobat.


You could change the href property in Reader up to version 8.0. But from 8.1 onward the security was tightened and potential security holes, like this one, were closed.

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