Posts in Category "Acrobat"

Reader 10.1.2: printing results in an application crash

Issue

If you are using Adobe Reader 10.1.2 you may experience some problems when attempting to print a PDF document.  The symptoms of this problem will be that either nothing will be printed, or, Reader may crash.

Reason

This is a bug in Reader 10.1.2 and is resolved with the 10.1.3 and later releases.  The problem is related to network printers that do not have a “Share name” defined.

If you cannot update to 10.1.3 immediately (in controlled enterprise environments) we have provided known workarounds to avoid the issue until you can install the update.

Solution

1. Open Reader

2. Choose Help > Check for Updates

Reader installs the update automatically.

If you prefer, you can download and install the update yourself. Click the link below and scroll down to the update section of the page.

Reader updates (for Windows)

Workarounds

Option 1: install patch for Adobe Reader 10.1.2

  1. Log in to your computer as an Administrator.
  2. Click the link to download the AdobeReaderPatch10.1.2_cpsid_92870.zip  file.
  3. Unzip the file to extract the executable AdobeReaderPatch10.1.2_cpsid_92870.exe.
  4. Close Adobe Reader if it is running.
  5. Do one of the following to run the AdobeReaderPatch10.1.2_cpsid_92870.exe file:
    1. Double-click the AdobeReaderPatch10.1.2_cpsid_92870.exe file.
    2. Run the AdobeReaderPatch10.1.2_cpsid_92870.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 AdobeReaderPatch10.1.2_cpsid_92870.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)

Option 2: create share names for all network printers

  1. Go to Start > Devices and Printers.
  2. Access all Network Printers installed on your machine.
  3. Right click on each network printer to access the printer properties.
  4. Goto the Ports Tab and verify the printer is a network printer (i.e. it is using a “Standard TCP/IP Port”).
  5. You only need to continue if this is a network printer.
  6. Open the Sharing tab and give your printer a “Share name”.
  7. If you wish not to share your printer then you may choose to give it a “Share name” and then select the “Do not share this printer” checkbox.
  8. Please ensure that all Network printers have been assigned a Share name otherwise the problem will persist. Please find below a screenshot for your reference.

Option 3: disable protected mode

The second work around is to turn off the Protected Mode of Adobe Reader and the problem will be resolved right away. However, it is not advised to keep the application in non-protected mode for security reasons.  It is advisable to turn this setting ON once you are done with your printing task.

You can access this setting by going to Edit–>Preferences–>General, and un-check the option “Enable protected mode at start-up” at the bottom of the window. You will need to re-start the Adobe Reader after you have made changes to this setting.

reference: (3088576)

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

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

Issue

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.

Explanation

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 (http://www.w3schools.com/xml/xml_syntax.asp):

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

Notes:

You can use a regular button with script like “event.target.submitForm({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/Reader: Z@xxx.tmp files left behind in Temp folder after printing

Issue

If you are printing files with Adobe Reader/Acrobat you may notice that some tmp files are created in your Windows Temp folder:

C:\Documents and Settings\<user>\Local Settings\Temp

with file names similar to:

Z@R3A.tmp

Z@R3C.tmp

Z@R3E.tmp

Z@R38.tmp

Z@R3B.tmp

Only some of these tmp files get cleaned up after the print job has completed and you close Adobe Reader/Acrobat.  The remaining files are locked and cannot be deleted.  This can cause problems particularly in Terminal Server or Citrix environments where the user’s profile should be cleaned up when they logoff, but such locked tmp files prevent the successful cleanup.  This problem with remaining locked files only seems to occur on Windows XP, NT and 2003 Server.

Reason

These tmp files are actually the true type fonts that are used by the Windows print spooler when printing a PDF.  The font files get created using the Windows call CreateScalableFontResource.  This Windows API call locks the files and thus when Acrobat calls DeleteFile on these files, sometimes an ACCESS_DENIED error is returned and they cannot be deleted.

The issue is the OS keeps a lock on these files which gets released on system restart, or when the user logs off and back on (this is the case with XP/NT/2003Server).  These files can be deleted when the system restarts, Acrobat/Reader is launched again and then closed which will issue the request to Windows to delete the files again.  Sometimes the lock on these files is released by the OS after some time has elapsed.

We have been unable to identify the root cause of this issue in Windows and why it keeps a lock on these files, despite very intensive testing and debugging.  The problem is not isolated to any specific issue in Adobe software.

We provide the following workarounds to avoid this issue.

Workaround1

In a Terminal Server or Citrix environment it is not possible to restart the machine, as there may be other users logged on.  Therefore you may use one of the following workaround files.

There are 2 methods used in Acrobat/Reader to create these temp files for the fonts.  In the first acroct.ini file we disable one of these methods, and this has brought positive results in most cases.  In the second acroct.ini file we disable both methods, so that no temp files for the fonts are generated anymore, and therefore cannot be locked.

1. close Adobe Reader/Acrobat

2. extract the first acroct.ini, or second acroct.ini file to C:\Windows

On Terminal Server this should then install the .ini file in each user profile under C:\Documents and Settings\<user>\Windows.

Please note that using these .ini files will reduce the quality of the printed output, as the printed fonts can no longer render exactly as shown on screen.  Therefore it is more desirable to use the first acroct.ini (diables only one method) if it solves the issue, rather than the second acroct.ini (disables both methods).  You should verify the printed output using these files and decide which one works best for you.

Workaround2

Following our testing we have discovered that the issue does not occur in Windows 7, or Windows 2008 Server.

It seems that the updated versions of Windows provide a solution to this issue.  We would therefore recommend updating your OS if possible.

reference: (182680504/2989318)

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

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

Issue

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

Reason

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:

xref
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: http://labs.appligent.com/pdfblog/pdf_cross_reference_table.php).

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

Solution

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:

http://acrobatusers.com/tutorials/where-has-the-typewriter-tool-gone

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

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

Description

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.

Suggestions

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: http://acrobatusers.com/tutorials/how-add-text-pdfs

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 (84 votes cast)

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

Issue

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.

Reason

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.

Solution

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.

Workarounds

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]

“bCheckReadMode”=dword:00000000

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

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

“iWizardRun”=dword:00000001”

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.3/10 (89 votes cast)

How to enable the Javascript debugger in Adobe Reader

Using the debugger with Adobe Reader

 The JavaScript Debugger is normally accessed from the Acrobat Pro user interface, but it can also be triggered to appear in Adobe Reader when an exception occurs.  Though fully supported JavaScript debugging is only available in Acrobat Pro, the following instructions make the complete Debugger functionality available in Adobe Reader on Windows and Mac OS platforms.

For Windows, note that this procedure involves editing the registry. Adobe Systems Incorporated does not provide support for editing the registry, which contains critical system and application information. It is recommended that you back up the registry before modifying it.

  1. Get a copy of the file debugger.js from an installation of Acrobat (plugins folder), the Acrobat Developer Center, or from the SDK (Acrobat 9.0 SDK/JavaScriptSupport/Debugger/debugger.js)
  2. Copy the debugger.js into the Reader 9.0/Reader/JavaScripts folder.
  3. Create key/value pairs in the registry settings, starting at the location HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\JSPrefs\ on Windows as shown in the table below, or in the property list file :Library:Preferences:com.adobe.Reader9.0.plist on Mac OS.

For Mac OS, use an appropriate editor for the property list file, and add the following children under JSPrefs, using Type “Array” in each case: ConsoleOpen, ConsoleInput, EnableDebugger, and Exceptions. Under each of these children, add the following children: 0 (number) and 1 (boolean).

bConsoleInput REG_DWORD 0×00000001
bEnableDebugger REG_DWORD 0×00000001
iExceptions REG_DWORD 0×00000002
(This will break into the Debugger when exceptions occur.)

4. Close and restart Adobe Reader. At this point the Javascript Debugger will be available.

Note: Since Adobe Reader does not provide access to the Debugger through its menu items or the Ctrl + J key sequence, the only ways to access the Debugger are to execute a JavaScript, cause an error, or customize the user interface (for example, you could add a button that runs a JavaScript causing the Debugger to appear).

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

Acrobat/Reader: how to handle the Adobe Approved Trust List (AATL) update dialog

Description

When you use Adobe Acrobat or Reader to open PDF documents that were signed or certified using certificates, you may see the following message:

A new security settings update is available from Adobe Systems.  Would you like to install it now?”  This dialog is a trusted Adobe dialog referring to updates to the root certificate list (AATL) in Acrobat or Reader.

Explanation

AATL or Adobe Approved Trust List is a program that allows millions of users around the world to create digital signatures. The signatures are trusted whenever the signed document is opened in Adobe Acrobat 9 or Reader 9 or later.  The list of trusted certificates is updated from time to time in case some certificates have been added, renewed, or have expired.

These updates are distinguished from the standard product updates for Acrobat or Reader, which can be triggered by choosing Help > Check For Updates.

Related preferences

If you want to check for certificate updates, choose Edit > Preferences > Trust Manager > Click Update Now under the section Automatic Updates. The same update dialog box opens. Using this option, the certificate updates are loaded from a trusted server.

To enable the automatic update check, choose Edit > Preferences > Trust Manager > Load Trusted Root Certificates From An Adobe Server.  To enable the automatic check without any notification, deselect Ask Before Installing.

Assuming that you have enabled the automatic check, the certificate updates are triggered under the following conditions:

  1. you open a file that has a digital signature, and
  2. you have never checked for updates before, or
  3. you have checked before, but
    1. 28 days have elapsed and
    2. there is a new update available

You can select Yes and the trusted certificate list in Acrobat or Reader is updated. If you want to see the trusted list, choose Open Adobe Reader > Document > Manage Trusted Identities. In the window that opens, choose Display > Certificates. The entire Trusted Certificates list currently installed with your Reader appears.

Enterprise deployment

If you are working in an enterprise environment and want to control these settings for an enterprise deployment, use the Customization wizard to activate or deactivate these options.

Additional information

http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS8084ADD0-83CB-43fe-B3CC-0D9AF9224C8C.w.html

 reference: (182278250)

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

Configuring Adobe Reader help files for offline use

Description

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 adobe.com.  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.

Suggestions

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 Adobe.com (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: http://help.adobe.com/en_US/reader/using/reader_X_help.pdf.

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.

Adobe_Reader_9.0_HTML_Help.zip

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: 7.8/10 (5 votes cast)

Acrobat/Reader: Invalid ColorSpace error opening a PDF

Issue

 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.

Reason

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.

Solution

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 (http://www.adobe.com/devnet/pdf/pdf_reference.html).
  • 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)

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

Issue

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.

Solution

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.

http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS58a04a822e3e50102bd615109794195ff-7fe4.w.html

reference: (181750120/2615060)

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

Acrobat/Reader: poor performance opening a PDF with a smart card

Issue

It takes a long time to open a PDF file when there is a smart card attached to the computer.  This issue can occur regardless of whether the smart card is used in Acrobat/Reader.

Solution

Update to Acrobat 9.4.5, 10.1, or later.

Additional information

When the smart card is attached to the computer, Acrobat detects there is a certificate available. It tries to validate the smart card by checking the certificate chain in the Acrobat and the Windows trust stores. There is a known issue in Acrobat where the algorithm performing this certificate check is inefficient and loops through the chain multiple times. Adobe has improved the performance of the certificate check. However, it has no influence over the other components that lead to the total delay where a smart card is inserted. There are also known delays in smart cards, the reading device and driver, and in the Windows trust store.

reference: (182022367/2710575)

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

Acrobat/Reader: disable or remove Flash components

Following the high frequency of security updates related to Adobe Flash, there’s often a security update required for Adobe Reader or Acrobat.  Flash is embedded in both of these products.

You may want to remove the Flash components file (authplay.dll) from Reader or Acrobat. When this file is removed, you can avoid applying the Acrobat/Reader security updates when it is a security issue exclusively in Flash. However, Adobe doesn’t support removing the authplay.dll from the installed plug-ins for any version of Acrobat or Reader. These products have not been tested in this form. Removing the authplay.dll file can result in unexpected behavior.

If you do remove authplay.dll, then make sure that you can reproduce any issues that arise on a standard Acrobat installation before contacting Adobe support. (A standard installation is one in which the authplay.dll file is installed.)

Here is a rough description of the possible behavior based on version:

  • Reader and Acrobat 8 and earlier: Not relevant as Flash is not embedded in these versions.
  • Reader and Acrobat 9: Possible to remove or rename authplay.dll. However, doing so can result in an application crash when rich media content is opened in Reader or Acrobat. (For example, when you open PDF portfolios, or PDF files with embedded rich media content)
  • Reader and Acrobat 10: Not possible to remove or rename authplay.dll as the user interface itself contains Flash components. (Using protected mode avoids the security updates anyway)
  • Reader and Acrobat 10+: it is still under discussion whether Adobe will offer the ability to disable or remove the Flash components from Reader or Acrobat.

reference: (182321552)

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

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

Issue

 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.

Solution

 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)