Posts in Category "Printing"

Acrobat: PDF Printer missing after installation on Windows 64-Bit

Issue

If you have installed Adobe Acrobat on a Windows 64-bit OS, you may notice that the Adobe PDF printer has not been installed.  During the installation you may have received an error similar to the following:

Please note that the Adobe PDF Printer functionality to create PDF files  is only available with Adobe Acrobat (paid version), and not with Adobe Reader (free version).

Solution 1

Repair the Acrobat installation using the option in the Help menu.

Solution 2

Uninstall and then re-install Acrobat on your Windows OS.

Solution 3

Manually install the PDF Printer

  • Click Start >  Control Panel > Devices and Printers
  • Select Add a printer
  • Select Add a local printer
  • Check Use an existing port and select Documents\*.pdf (Adobe PDF) from the drop down.  Click Next
  • Click the Have Disk… button
  • Click the Browse… button
  • Navigate to C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Xtras\AdobePDF
  • Select AdobePDF.inf from the list if using Acrobat Pro, or AdobePDFstd.inf if using Acrobat Std, then click the OK button
  • You will see many Adobe PDF Converters in the list, however count six down from the top and click Next (you may need to try this numerous times to find the correct Converter from the list that works with your version of Windows)
  • Name your printer, e.g. Adobe PDF
  • Follow the rest of the prompts and your PDF printer should now be installed correctly

If you are later prompted for the ADPDF9.PPD file, it can be found in the C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Xtras\AdobePDF\<OS version> folders.

Additional Information

http://forums.adobe.com/message/3348729

http://acrobatusers.com/forum/pdf-creation/how-do-i-insatll-adobe-pdf-printer-windows-7-adobe-reader-9/

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

Acrobat/Reader 10.1.2: printer blinking/paper tray messages caused by duplex print option

Issue

If you are using Acrobat/Reader 10.1.2 to print PDF documents, you may notice that the job is sent to the printer as a duplex job (print on both sides) and this may cause some issues like printer lights blinking, or errors about lack of paper in the paper trays.

Reason

With Acrobat/Reader 10.1.2 we have introduced the widely used print option “Print on both sides of paper” directly in the Acrobat/Reader print dialog.  This option is available in the printer settings, but it is not very convenient to have to open the printer settings and change it each time you wish to print differently (simplex/duplex).

This option in the Adobe print dialog is enabled by default, whereas the initial value should match what the user has specified in the printer properties.  This option can lead to the printing anomalies mentioned above.

Solution

This is a bug in Acrobat/Reader 10.1.2 and has been fixed in the 10.1.3 update so that the option has the same initial value as defined in the printer settings, and the printing anomalies should no longer occur.

1. Open Acrobat or Reader.

2. Choose Help > Check for Updates.

Acrobat or Reader will install the update automatically.

Workarounds

There are 3 options to workaround this issue.

Option1

To workaround this behaviour in the meantime simply disable this option in the Adobe print dialog.

Option 2

In an enterprise environment, you can use the following registry key to disable duplex mode automatically in Adobe Reader X:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\AVGeneral]

“iDuplexMode”=dword:00000001

or for Adobe Acrobat X:

HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0\AVGeneral]

“iDuplexMode”=dword:00000001

For MacOS use the preferences file (com.adobe.Reader.plist / com.adobe.Acrobat.Pro.plist) which is located in [user]/Library/preferences/.  The name of the key is DuplexMode under AVGeneral and it has the datatype Number. You should set this value to “1”, for Simplex.

Option 3 (courtesy of the post from banyooo on http://forums.adobe.com/message/4147397)

If you are in a Windows domain controlled environment you can also roll out this registry key using a group policy as follows:

  1. Open your Windows Group Policy Editor
  2. Chose “New Group Policy”
  3. Ggo to UserConfiguration >Settings >Windows Settings >Registry
  4. Right click “Registry”
  5. Chose “New-> Registry assistent”, local computer
  6. Go to [HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\AVGeneral] “iDuplexMode”=dword:00000002
  7. Click “finish”
  8. Double-click that new entry and navigate down until you see “iDuplexMode”
  9. Double-click it too, and change the REG_DWORD value to “1” (decimal)
  10. Chose “Replace” under the “Action” menu
  11. Close the GPO editor and link that newly created group policy to your domain or OU or whatever
  12. Perform a gpupdate /force at the client to see the reg entry changing from “2” to “1”
  13. Reboot your clients or just wait for the gpupdate timeout period

reference: (3088596)

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

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

Acrobat/Reader: Application crash using HP Universal Print driver

Issue

 When you use the Hewlett-Packard Universal Printer driver, Adobe Reader and Acrobat may crash. The following error may appear in the OS event log:

Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=083a8310 ebx=0701649c ecx=08431f30 edx=00000be8 esi=00000000 edi=0000002c eip=0700bf92 esp=0012cea4 bp=0012cef4 iopl=0
 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 fl=00210206

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Programme\Adobe\Acrobat 8.0\Reader\BIB.dll -BIB!BIBLockSmithAssertNoLocksImpl+0x4b7b:0700bf92 0fb772fe
 movzx esi,word ptr [edx-2] s:0023:00000be6=????0:000> kb
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WTSRV\system32\ntdll.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Programme\Adobe\Acrobat 8.0\Reader\AGM.dll -

Explanation

This issue occurs only after printing multiple times; sometimes only after the fourth or fifth print job. It is only reproducible in certain environments (for example, German Windows locale, with a German domain).  This issue was thought to be an Adobe issue, based on the error message above pointing to an Adobe DLL.

After further investigation, Adobe discovered that strange results from the call to the Microsoft API “DeviceCapabilities” cause this error. When correct, this call returns the number of pages that were sent to the printer. For a document with 22 pages, it sometimes returns 39 sometimes 22 and sometimes -1, which means the function failed. Any result other than 22 is false and could result in the crash. If the function returns 39, then there is space for 39 pages reserved in memory when only 22 are written. Therefore, some other memory is overwritten by mistake, which would result in an application crash.

HP have developed an updated driver to fix this issue.  Other customers experiencing this issue should contact HP to get the updated driver.

reference: (181283908/2558881)

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

Acrobat 8 SDK: docPrintParamsRec variable limited to 64 characters

Issue

If you are using the Acrobat SDK to control the print functionality in Acrobat/Reader, or to write a custom print plugin, you will need to use the function: AVDocPrintPagesWithParams(avDoc, &docPrintParamsRec);

The length of the input parameters in docPrintParamsRec, e.g. the printer names, are limited to 64 characters, or 32 Unicode characters. Windows however supports up to 240 characters for printer names.
Printing to a printer with a name longer than 64 characters, will not give an error message, the document will just not print.

Reason

This is a limitation in the Acrobat SDK as it still uses short printer names.  In the Acrobat standard printer dialog, there is no limitation as the dialog uses internal methods which have already been extended for long printer name support.

Solution

The Acrobat 9 SDK will resolve this issue and add support for long printer names.

Additional Information

Please refer to the following link for the declaration of the AVDocPrintPagesWithParams function (pg: 1713):

http://www.adobe.com/devnet/acrobat/pdfs/acrobat_pdfl_api_reference.pdf

it is discussed again here:

http://www.adobe.com/devnet/acrobat/pdfs/plugin_apps_developer_guide.pdf

reference: (180009702/1673603)

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

Acrobat/Reader: “Too few operands” error printing a PDF

Issue

 If you are trying to print a PDF with Reader/Acrobat you may receive the error message “Too few operands”.

Reason

 You may need to strip down the original XDP file in Designer object-by-object, re-generate, and try to print the PDF to find the offending object. Drop-down list boxes that contain a blank entry in their lists has been known to cause this issue in previous versions.

Once you identify which object is causing the problem you should analyze this object and all related script to isolate the root cause of the issue.

reference: (1-19885739)

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

Reader 8: how to print comments

Issue

You can use Acrobat 8 to apply usage rights to PDFs, in order to distribute the PDFs for Review and Commenting workflows to Reader 8 users.  This includes the option to print comments.  This is possible in Acrobat 8 using the “Document and Markup” option in the print dialog itself, and if the “Print notes and pop-ups” option in the Commenting preferences in Acrobat is enabled.

However, in Reader there are no Commenting preferences, so the users have no way to enable printing of comments even if they select the “Document and Markup” option from the print dialog.

Solution

There is a registry key in Acrobat that controls the “Print notes and pop-ups” option in the Commenting preferences.  If you set the following key in the Reader registry, then the comments are printed:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\8.0\Annots\cPrefs]
"bprintCommentPopups"=dword:00000001

_____________________________________

reference: (180910916/2332536)

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