Posts in Category "General"

Acrobat 10.1.4 crash using LiveCycle RightsManagement ES2 Extension for Microsoft Office

If you are using the Adobe LiveCycle RightsManagement ES2 Extension for Microsoft Office with Acrobat/Reader 10.1.4 then you may experience an application crash in Acrobat/Reader.  You will see the following error in the Eventviewer log:

Event Type:    Error
Event Source:    Application Error
Event Category:    None
Event ID:    1000
Date: …
Time: …  
User: … 
Computer: …
Faulting application acrobat.exe, version, faulting module acrobat.dll, version, fault address 0x00021212.


This is an issue with Acrobat/Reader 10.1.4 affecting compatibility with this LiveCycle plugin.


This issue is fixed in Acrobat/Reader 10.1.5 and later versions.

reference: (3322093)

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

Acrobat 10.1.4: Acrobat/Reader hangs while scanning


If you are scanning documents with Acrobat/Reader 10.1.4 using any mode (Grayscale/Color/BW),  Acrobat/Reader may hang when scanning is about to complete.


This is an issue in the 10.1.4 update and will be addressed in future versions.  It is also being discussed in our forums:


Install the patch for Acrobat and Reader 10.1.4 (Windows only).

  • Log in to your Windows computer as an Administrator.
  • Click the following link to download the patch file:
  • When prompted “Do you want to open or save this file?,” click Open.
  • Extract the file using a ZIP tool to a location on your local computer.
  • Double-click the AdobeAcrobatReaderPatch10.1.4_3314564.exe file to begin the update.
  • When a prompt notifies you that the update is complete, restart your computer.


 Install the patch for Acrobat and Reader 10.1.4 in silent mode (Windows only).
  • Log in to your Windows computer as an Administrator.
  • Click the following link to download the patch file:
  • When prompted “Do you want to open or save this file?,” click Open.
  • Extract the file.
  • Open the command prompt “As Administrator.”
  • Type the path to the patch file executable, and add the -silent flag on the command line. For example:
    AdobeAcrobatReaderPatch10.1.4_3314564.exe -silent
    Silent mode suppresses all dialog boxes so you do not get a message indicating that the update is complete. The executable creates a log file “AcroPatchApplication1014.log” in the temp directory (%temp%).
  • When the update is complete, restart the computer.

reference: (3314564)

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

Acrobat XI: new tab-stop feature available for rich-text fields


With the latest release of Adobe Acrobat/Reader XI there is a new feature available for structuring text in rich-text fields in XFA-based forms.  You can now add/modify tab-stops in rich-text fields using new UI components.  Adding tab-stops in rich-text fields allows for better formatting and table-like structuring of the text, which is a much requested feature from customers and users.


You download the sample file tabstops_richtext_field_dyn.pdf to see how this feature works.

1. Open the sample file in Acrobat/Reader XI.

2. Place the cursor in the large rich-text field.

3. Press CTRL+E on the keyboard to bring up the Form Field Text Properties toolbar.

4. Click the button “More…”

5. You will see the new Tabs dialog where you can create/modify the tabs in the field.

6. From here you can create/modify/delete the defined tab-stops, and change the alignment (Left, Right, Center, Decimal), or the position.


You can now also use the key combination CTRL+TAB on the keyboard to tab between tab-stops in the rich-text field.

The measurement units for the tab stops are inherited from the units defined in the Preferences (Edit > Preferences > Units & Guides > Page & Ruler Units):

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

Acrobat/Reader X: how to set the default font and font size in the Typewriter tool


If you are using the Typewriter tool in Acrobat/Reader you may notice that the default font and font size changes according to the font style already used in the PDF document.  The default font for the Typewriter tool should be set each time you finish using the tool and close Acrobat/Reader.  You may wish to reset/set the default font and font size to some custom value.


You can set the commenting font and font size in the “Commenting” section in the Preferences.

You can also select the “Comment” Tab between “Tool” and “Share”, right-click on the comment in the “Comments List” that has your desired font setting, and then select “Properties…”.  Check the box that says “Make properties default” and click OK.


If this still does not work, then you can set the default font and font size in the registry.  Please note that editing the registry can lead to corruption on your system and should only be attempted by experienced users or administrators.

We cannot provide support for any issues that may occur due to editing the registry, so we would recommend to do a full registry backup before making any changes.

To change the font:

1. Close Acrobat/Reader
2. Start—>Run—>Regedit
3. Navigate to: HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0\Annots\cAnnots\cFreeText_003aFreeTextTypewriter\crichDefaults\cfontFamily
4. Click the cfontFamily key on the left.
5. Double-click the a0 key on the right.
6. Change the a0 value to the font name you require.
7. Save

To change the font size:

1. Close Acrobat/Reader
2. Start—>Run—>Regedit
3. Navigate to: HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0\Annots\cAnnots\cFreeText_003aFreeTextTypewriter\crichDefaults
4. Double-click the dtextSize key on the right.
5. Change the dtextSize value to the font size value you require.
6. Save

Additional information

In Adobe Acrobat, if you want instructions to enable the Typewriter tool you should refer to the following post:

In Adobe Reader, if you cannot find the Typewriter tool you should refer to the following post:

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

Acrobat: “Insufficient data for an image” error after updating to 10.1.4 or 9.5.2


If you have updated Adobe Acrobat/Reader to the current version 10.1.4 or 9.5.2 then you may encounter the following error when opening some PDF files:

“Insufficient data for an image”

The PDF will open, but the contents may appear blurred, or not display at all.


This error occurs due to a problem in the Adobe Acrobat/Reader functionality used to display scanned documents and/or documents containing JP2K images.


This issue has been fixed with the latest version of Reader XI now available (  We are actively working on a solution for previous versions and expect to have a fix available for Adobe Acrobat/Reader 10.1.x and 9.5.x in Q1 2013.
Update (08 Jan 2013): this issue has now been fixed in the latest updates for Adobe Acrobat and Reader 9.5.3 and 10.1.5 available from the Adobe site:
Reader updates
Acrobat updates


Changing the zoom settings should allow you to see the contents of the document.  Try reducing the Zoom factor, or click the button to “Fit one full page to window”.

You can make this change persistent (to avoid changing for every document) in Edit > Preferences > Page Display > Zoom > Fit Page.

You can also try saving the PDF again in Acrobat using the PDF Optimizer to optimize the PDF file using Standard settings, or the Reduced Size PDF option.

For those looking to roll-back to a previous version of Adobe Acrobat/Reader to avoid this problem, you can find archived versions here:

Further Information

This issue is being discussed in detail in the following forum threads:

reference: (3312912/3312904)

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

Adobe Reader cannot open Protected Mode due to a problem with your system configuration.


If you are starting Adobe Reader and have Protected Mode enabled, you may encounter the following dialog:

“Adobe Reader cannot open in Protected Mode due to a problem with your system configuration. Would you like to open Adobe Reader with Protected Mode disabled?”


This dialog appears when protected mode cannot be started due to environmental settings on your computer.  It can occur due to anti-virus software conflicts, and/or conflicts with accessibility tools or smart card software and drivers.


1. Unsupported configurations:

  • Installing Reader on a mapped network drive.
  • Running Reader on WinXP when the OS is installed in a public folder.
  • Launching Reader in XP-compatible mode on Vista and Win7.
  • Launching Reader by right clicking AcroRd32.exe and choosing Run As.
  • Using PKCS#11 smart cards in signature workflows. Some cards can work in the presence of custom protected mode policies. For a workaround, see below.
  • Collaborating in real time using the Collaborate Live feature.
  • Certain configurations of anti-virus software that have not yet white-listed AcroRd32.exe. See Anti-virus software conflicts below.
  • JS-invoked processes: Launching a process through JavaScript is not allowed with Protected Mode enabled.

2. Antivirus software conflicts:

By default, Adobe Reader X runs in Protected Mode. In certain situations Reader experiences compatibility issues with anti-virus software when that software intercepts some system calls for the Reader sandbox. In these cases, Reader could fail to open or crash after displaying an incompatible-configuration dialog.

For example, Protected Mode is known to be incompatible with:

  • Some Symantec Endpoint Protection configurations. Adobe recommends that users update to Symantec Endpoint Protection 11.0 RU6 MP2 or higher.
  • McAfee VirusScan Enterprise for certain actions in Reader. Known actions include the following:
    • Clicking Help or a Weblink from an embedded Flash widget such as a Portfolio navigator (Fixed 10.1).
    • Launching of some IME tools. Note: Disabling Buffer Overflow Protection can provide a workaround for many McAfee users.
    • Reader sometimes removes a user’s cached credentials when signing out of which could be an issue for a multiuser machine. Fixed 10.1.2 with MVE 8.8.

Adobe is working with anti-virus companies to resolve these problems.

3. Accessibility

For XP only: Accessibility features sometimes doesn’t work. The Read Out Loud feature is unsupported. Therefore, screen readers such as JAWS, Windows Eyes, and Windows Narrator aren’t always able to read PDF content. Much of the Accessibility menus involving things like quick check, change Reading options are removed. Keyboard navigation is not implemented.

Note: When a screen reader like JAWS, Window-Eyes, or Narrator is running when Reader is started for the first time on XP, Protected Mode is disabled. On Vista and Windows 7, screen readers do work normally.

4. P11 smart card workaround

The installation of some smart cards doesn’t work for Reader X users when in Protected Mode. Because Protected Mode sandboxes certain processes that make system calls, smart card installation can fail or result in the “unsupported configuration” dialog appearing. However, a simple workaround is available. Install the smart card software with Protected Mode turned off as follows:

  • Disable Protected Mode by going to Edit > Preferences > General and deselecting Enable Protected Mode at startup
  • Restart Reader
  • Install the smart card software according to the provider’s instructions
  • Re-enable Protected Mode
  • Restart Reader

5. Windows Permissions

You should also check the permissions on the Adobe Reader installation folder.  Protected mode will only work on Windows when the group “BuiltIn\Users” has the following permissions on the Reader installation folder (for a default installation C:\Program Files (x86)\Adobe\Reader 10.0):

  • Read & execute
  • List folder contents
  • Read

Further Information

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

Acrobat/Reader: how to automatically check the installed version


In enterprise environments it is often required to provide some kind of health check application to check the pre-requisites (i.e. installed apps and versions) on client machines.  This provides an automated way of checking that the client machine is correctly setup for use in business workflows that rely on certain installed applications such as Adobe Acrobat/Reader.


You can use Javascript to detect and read the Adobe Acrobat/Reader browser plugin version:

You can use the Windows GUID from the Registry or the MSI API to read the Reader client version:


reference: (183022625)

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

Acrobat 10.1.2: “Adobe acrobat has stopped working” when using Preflight


If you are using the Preflight feature in Adobe Acrobat Pro 10.1.2 you may encounter an application crash accompanied by the following error:

“Adobe acrobat has stopped working”

Crash details:

Problem Event Name:    BEX
Application Name:    Acrobat.exe
Application Version:
Application Timestamp:    4f02e85c
Fault Module Name:    StackHash_0a9e
Fault Module Version:
Fault Module Timestamp:    00000000
Exception Offset:    00000001
Exception Code:    c0000005
Exception Data:    00000008
OS Version:    6.1.7600.
Locale ID:    2057
Additional Information 1:    0a9e
Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
Additional Information 3:    0a9e
Additional Information 4:    0a9e372d3b4ad19135b953a78882e789


This is an issue with the Acrobat Pro 10.1.2 update on Windows only and has been fixed in the 10.1.3 update.  It does not occur on Acrobat Std or Reader editions, and does not occur on Mac OS.


1. Open Acrobat.

2. Choose Help > Check for Updates.

Acrobat will install the update automatically.

You may also download and install this update manually from the website below:

Acrobat updates (for Windows)


  1. Log in to your computer as an Administrator.
  2. Click the link to download the  file.
  3. Unzip the file to extract the executable AdobeAcrobatPatch10.1.2_cpsid_92893.exe.
  4. Close Acrobat if it is running.
  5. Do one of the following to run the AdobeAcrobatPatch10.1.2_cpsid_92893.exe file:
    1. Double-click the AdobeAcrobatPatch10.1.2_cpsid_92893.exe file.
    2. Run the AdobeAcrobatPatch10.1.2_cpsid_92893.exe file in silent mode by specifying the -silent flag on the command line. Open the command prompt ‘As Administrator’ to avoid UAC prompt dialog.
      Example: <path to AdobeAcrobatPatch10.1.2_cpsid_92893.exe> -silent
  6. Once the process is completed, you receive a prompt stating the result of the operation.
    Note: When run in silent mode, all dialog boxes are suppressed. No success message or error message appear.
  7. A log is created in the temp directory (%temp%) with the name AcroPatchApplication1012.log. (The changes sometimes only take effect after you restart your computer)

reference: (3089118)

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

Acrobat/Reader: Some special characters are not escaped in XML submission to a HTTP URL


If you are using XFA forms to submit/export data in XML format from Acrobat/Reader, you may notice that some of the special characters (<>”&’) are not being escaped in the XML output. This can lead to problems if this XML is then to be parsed server-side or used by custom applications.


The XML data submitted/exported from Acrobat/Reader escapes characters like & (ampersand) > (greater than) and < (less than), but not ” (quote) or ‘ (apostrophe).  Custom applications may encounter problems when trying to parse XML data containing apostrophe or quote characters, if they are expecting these characters to be escaped like for <, > and &.

There are 5 predefined entity references in XML (

&lt;  < less than
&gt;  > greater than
&amp;  & ampersand
&apos;  ‘ apostrophe
&quot;  “ quotation mark

Note: Only the characters “<” and “&” are strictly illegal in XML. The greater than character is legal, but it is a good habit to replace it.

So the XML specification recommends to replace only “<“, “&” and “>”.  It does not require quote and apostrophe characters to be escaped for element values.  Therefore all conformant XML parsers should be able to handle this.

Quotes and apostrophes only need to be escaped if they occur in an attribute value surrounded by the same single or double-quote character.  In this case, Acrobat/Reader will escape the quote or apostrophe characters as required.


You can use a regular button with script like “{cURL: url, cSubmitAs:”XML”});” to submit data in XML format to a specific URL.

reference: (182809204/3054499)

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

Acrobat: Syntax problem: Indirect object has object number not preceded by an EOL marker


If you are using Acrobat Preflight or LiveCycle DocConverter to validate PDF/A documents you may encounter the following error after validation:

Syntax problem: Indirect object has object number not preceded by an EOL marker


The PDF standard stipulates that a PDF contains lines, each of which will be terminated with a CR, a LF, or both.

If you analyze the Preflight report you will be able to see which object is causing this error.

In this case Preflight is complaining that there is no EOL marker before the “1 0 obj”.

Open the PDF in an advanced editor like Notepad++ and check the CR and LF characters on all the lines surrounding the “1 0 obj”.

There are EOL markers (CR and/or LF) surrounding the “1 0 obj” object.  This must be caused therefore by a problem in the cross-reference table in the PDF file.  If you scroll to the bottom of the file in Notepad++ you will see a table similar to the following:

0 11
0000000000 65535 f
0000000017 00000 n
0000000115 00000 n
0000186286 00000 n
0000000182 00000 n
0000000340 00000 n
0000000485 00000 n
0000186388 00000 n
0000186599 00000 n
0000189276 00000 n
0000190175 00000 n

This is the cross-reference table which allows direct access to all objects in the PDF file (like the index in a book).  The first line is a summary of the table (starts with object 0, and contains 11 objects).  The rest of the lines make up the index of those 11 objects.  Lets analyze the line entry for object 1 (0000000017 00000 n).  The value 17 is the number of bytes from the start of the PDF file where the object 1 should be located.  The other values (00000 and n) are the generation number and a flag to tell if the object is in use or free (more info on these objects here:

So we know that the object 1 should start after 17 bytes in the PDF file.  However if you use Notepad++ to select the bytes up to position 17 you will see that it refers to the position after the “NUL” object, and before the EOL markers (CR LF):

Note the selected text and the byte count in the status bar “(17 bytes)”.  It should be pointing to the start of the next line where the “1 0 objCRLF” entry is located (i.e. byte 19).


Our recommendation here is to ensure you use Adobe tools (e.g. Acrobat/LiveCycle) to create your PDF files.  The PDFs generated with Adobe software will have a valid structure and will comply with the PDF standards (PDF, PDF/A, PDF/X etc…).

In this case the PDF was generated with an external tool and this resulted in the incorrect entry in the cross-reference table.  Although we would not advise such manual modifications in your PDF file content, you can fix such an issue by manually changing the cross-reference table entry from 17 to 19 bytes so that the “1 0 obj” object is correctly indexed.  The PDF structure is then correct and Preflight can validate the PDF/A.

reference: (182711898/3002114)

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

Acrobat X: how to enable the Typewriter tool

Acrobat X:

If you have been using the Typewriter tool in previous versions of Acrobat/Reader you will notice it is no longer available under the Tools menu in Acrobat/Reader X.

The Typewriter tool has been renamed to “Add or Edit Text Box” and relocated in Acrobat X following extensive research by our product teams.  A lot of people were having issues trying to find these tools in previous versions.  Particularly with the younger generation, some did not even know what a typewriter was.

      To locate/use the Typewriter tool in Acrobat X:

      1. open a PDF

      2. click on the “Tools” menu on the right-hand side

      3. expand “Content”

      4. click “Add or Edit Text Box”






A new feature in Acrobat/Reader X allows you to add commonly used tools to the Quick Tools bar.  If you right-click on the “Add or Edit Text Box” button, and select “Add to Quick Tools”, then you will see the icon appear on the toolbar as follows:

Note: If you are using Adobe Reader, the “Add or Edit Text Box” tool is not available until you enable the PDF with extended rights.  You should check this post to ensure the PDF file has the correct rights enabled for editing.  Once the PDF is setup correctly, the tool will show up directly on the toolbar, or under the Extended menu.

Acrobat XI:

If you are using Acrobat XI then you can watch the following video to see how to enable the typewriter tool:

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

Adobe Reader: How to use Adobe Reader to fill PDF forms or type text on a PDF file


If you are using Adobe Reader you will notice that you are unable to write/save content in PDF files.

Adobe Reader is a PDF reader provided free-of-charge and does not allow users to “write” content in PDF files by default. In order to make and save changes to a PDF file, you need a license for Adobe Acrobat, or LiveCycle Reader Extensions. Changes that normally require Adobe Acrobat include: entering text, saving a PDF form, and adding comments.


PDF authors can use either Adobe Acrobat or Reader Extensions Server to enable individual PDF files with specific privileges to allow Adobe Reader write and save content into the PDF files. If you/your organization has a license for Adobe Acrobat or Reader Extensions Server, you can apply these privileges to the PDF file before distributing it, so that users can open it in Adobe Reader to write the content.

You can use one of the following solutions to enable the PDF files:

Solution 1: Enable the Typewriter tool for Adobe Reader.

  1. Enable the Typewriter tool on the PDF.
    • With Adobe Acrobat:
      Note:You must have at least one Acrobat Professional client installed.

      1. Open the PDF in Acrobat Professional.
      2. Follow instructions depending on Acrobat version:
        • Acrobat (8 or 9): choose Tools > Typewriter > Enable typewriter tool in Adobe Reader, or Advanced > Extend Features in Adobe Reader.
        • Acrobat X: choose File > Save As >Reader Extended PDF > Enable Adding Text in Documents.
      1. Save the PDF.
    • With Reader Extensions Server:
      Note:You must have a Reader Extensions server installed in your organisation.

      1. Go to the ReaderExtensions server portal (http://[servername]:[port]/ReaderExtensions).
      2. Upload the PDF file.
      3. Apply the commenting right to the PDF.
      4. Save the resulting PDF to your computer.
  2. When you now open the same PDF in Adobe Reader, you will have a new tool available under Tools > Typewriter (Reader 8/9), or Tools > Add or Edit Text Box (Reader X).
  3. You can use this tool to type characters on top of the PDF content.

Here is a video tutorial showing how to use the Typewriter tool on a PDF:

Note: The typewriter tool is only available for static PDF files, not for dynamic files, as it is part of the commenting functionality. Imagine if you lay down a comment on a certain part of the PDF and then the PDF structure changes dynamically and shifts the content down a page to accomodate a new subform. The comment/typewriter text would no longer be pointing to the same position.

Solution 2: Enable the usage rights on the PDF in Acrobat.

Note: You must have at least one Acrobat Professional 8, or later, client installed.

  1. Open the PDF in Acrobat Professional.
  2. Choose Advanced > Enable Usage Rights in Adobe Reader (Acrobat 8/9), or File > Save As >Reader Extended PDF > Enable Additional Features (Acrobat X).
  3. Save the PDF.
  4. When you now open the PDF in Adobe Reader you will be able to fill the form and save the data.

Solution 3: Enable the appropriate rights on the PDF using Reader Extensions Server.

Note: You need to have a Reader Extensions Server installed in your organisation.

  1. Go to the ReaderExtensions server portal (http://[servername]:[port]/ReaderExtensions).
  2. Upload the PDF file.
  3. Select the Usage Rights you wish to apply to the PDF (you need Form Fill-In if you wish to complete the PDF form fields and save the data, or the Commenting right to use the Typewriter tool).
  4. Save the resulting PDF to your computer.
  5. Open the resulting PDF in Adobe Reader and you will be able to fill and save it.

Note: Reader Extensions server is a LiveCycle product to be deployed in an enterprise environment, and for this reason, may not be cost-effective if you only want to enable a handful of forms or PDFs.

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

Acrobat/Reader: how to disable the “Reading Untagged Document” dialog


When you open a PDF document in Acrobat/Reader you may encounter the following dialog:

You may want to disable this dialog from appearing as it can effect your productivity if it appears for every document you open.


Accessibility tools like screen readers are used to read the contents of PDF files displayed in Acrobat/Reader.  Screen readers rely on the documents tags to read the contents of the document.  This dialog appears when Acrobat/Reader detects that screen reader software is installed and informs the user that the document has no tags (and therefore cannot be read by any screen reader).  The dialog is used to then create tags for the document so that it is accessible.

Windows itself has screen readers installed by default in certain versions and these may be activated causing this dialog to appear.  We have also received reports that other non-Accessibility software and device drivers cause this dialog to appear, as the software and drivers incorrectly use some system flags usually reserved for Accessibility tools.


We are working with Accessibility software vendors to find a more reliable way of registering such software to ensure Adobe Acrobat/Reader correctly detect it.  The goal is to avoid Accessibility functionality being launched in Acrobat/Reader due to the mis-use of the system flags by non-Accessibility software.

In the meantime you can use one of the workarounds below to avoid this issue.


You can prevent this dialog from appearing in a number of different ways:

1. Always use the default settings and create tags for the document

In this case you should just select the option “Always use the settings from the Reading preferences (Do not show this dialog again)”.  The options defined in the Acrobat/Reader Preferences under the Reading section will be used to create tags for each PDF file (that do not already contain tags) opened in Acrobat/Reader.

2. Disable the confirmation dialog in the Preferences

You can also disable this “Readung untagged document” dialog in the Reading Preferences by un-checking the option Edit > Preferences > Reading > “Confirm before tagging documents”.  This option writes the following registry key which could also be used for enterprise deployments:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\Accessibility]


You can also disable the Accessibility Setup-Assistant dialog using the following registry key:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\Accessibility]


3.Remove the Accessibility plugins from Acrobat/Reader

If you do not require any accessibility features in Acrobat/Reader and you have not been successful disabling the dialog using the methods above, then you can always close Acrobat/Reader and remove the Accessibility.api and ReadOutLoud.api from the plugins folder.  You should keep a copy of these plugins in another folder as a backup.  When you restart Acrobat/Reader it should no longer display this dialog.

reference: (182470670/1877982)

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

Configuring Adobe Reader help files for offline use


If you are using Adobe Reader 9 or greater, you may have noticed that the help files are now only available online with an active internet connection to  In Adobe Reader 8 the help files were available within the product itself on your local machine and you did not need an internet connection.

If you do not have an active internet connection on the computers where Adobe Reader 9 and greater is installed, then you will not be able to access the help documentation, and will receive a 404 error in the browser.  This can occur for large enterprises where some machines are not allowed to have an open internet connection for security and data protection reasons.


There are 2 different solutions or workarounds to this issue:

1. Create a local PDF file containing the Help content.

You can reference this PDF file locally, or put the PDF file in a central location where all of your users can access it, i.e. on a network location, or on your internal web server. Here are the example PDF files for Adobe Reader 9 in English and German:

Adobe_Reader_9.0_Help.pdf (English)

Adobe_Reader_9.0_Hilfe.pdf (German)

Note: To create PDF files of the Adobe Reader 9 Help for other languages, go to the Help page for your language on (use a computer where you have Adobe Acrobat installed). Use the Acrobat Web capture plug-in to export the page as a PDF. Then, use Acrobat to fix the links in the PDF file and correct any structural issues.

For Reader X the help documentation is now available online in PDF format, so you can just download the PDF file from:

2. Re-construct the online Help documentation for Adobe Reader within your organization’s intranet environment.

You can deploy the Adobe Reader help pages on your internal web server where everyone in your organization can access them using a browser.

Download the .zip file below and extract it, maintaining the folder structure. Deploy the files to an internal web server. These Help files are available in English and German.

Addendum: Use Customization Wizard to tune the Adobe Reader installation.

In an enterprise environment you may want to configure Adobe Reader for all users to point to the custom Help documentation automatically. You can use the script in this solution to disable the standard Help menu item in Adobe Reader, and replace it with a custom Help menu item pointing to the help documentation from solution 1 or 2 above.

For solution 1 (local PDF file): create a custom folder in your Adobe Reader installation using Customization Wizard (e.g. C:\Program Files\Adobe\Reader <version>\Help), and put the local PDF file in there. Place the WinReader_Local_Help.js file into the Javascripts folder in Customization Wizard (C:\Program Files\Adobe\Reader <version>\Reader\Javascripts).

For solution 2 (HTML help files): after putting the Reader HTML files on your local intranet server, place the WinReader_Intranet_Help.js file into the Javascripts folder in Customization Wizard (C:\Program Files\Adobe\Reader <version>\Reader\Javascripts).

Now when Adobe Reader is launched on the user’s computer the help menu link will be replaced with your custom link. There may be a short delay before the link is updated after starting Adobe Reader.

reference: (181774134)

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

Acrobat/Reader: Invalid ColorSpace error opening a PDF


 When you try to view a PDF file in Adobe Reader or Acrobat, you see the following error:

“There was an error processing a page. Invalid ColorSpace.”

Try opening other PDF files in the same way and compare the results.  This problem only occurs for certain PDF files.


This error usually occurs viewing PDF files in the browser when there is a problem with the PDF file itself, particularly for PDF files generated with third-party applications or tools.  It will not prevent you from opening the file, but rather, some pages will not be visible.


If you are attempting to open the file through a browser (that is, from an Internet site), try to download the file to your local computer. Then, open it locally using Adobe Acrobat or Reader.  Check the file properties and see if a non-Adobe application was used to create the PDF file.

Here are some suggestions that have resolved the problem for other users:

  • If a non-Adobe application was used, then try using an Adobe application to generate the PDF file again.
  • If it is not possible to re-generate the PDF with an Adobe application, then try to resave it, and/or use the PDF Optimizer tool in Acrobat.  This will often fix any obvious syntax errors in the PDF.
  • If you used an Adobe application other than Acrobat to create the PDF file, ensure you have flattened all layers in the original file before creating the PDF, and check the colorspace settings you have used when exporting the PDF file.  For example, it is not valid to have a DeviceN color space with a colorant value “All”.  You can find details in the PDF Reference Manual (
  • If you have uploaded the file to a website using FTP, ensure you have transferred the file in binary mode.
  • You can try to disable the “Allow Fast Web View” option in the Internet preferences in Adobe Acrobat/Reader.

reference: (182325862)

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