Posts tagged "printing"

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

LiveCycle Designer: Render a trailing page in a form for duplex printing

When you use duplex printing (that is, printing on both sides of the paper), you can print a separate blank trailing page. To print a trailing page, the last page must always have an odd page number (that is, page 1, 3, 5, 7, and so on). When the last page is odd, it prints on a new sheet of paper separate from the rest of the form.

Render a trailing page in LiveCycle Designer 7.x

LiveCycle Designer 7.1 includes a script for rendering a trailing page.

To make sure that the last page has an odd page number, do the following:

  1. insert a blank hidden body page in the form just before the page you want to use as a trailing page.
  2. insert the following script in the layout:ready event of the form to show/hide the blank page at run-time:
var pageCount = xfa.layout.pageCount();

if(pageCount%2 == 0) {
    //even, show the blank page to shift the trailing page down to an odd page number
    form1.blank_page.presence="visible";
} else {
    //odd, hide the blank page as the trailing page is already on an odd page number
    form1.blank_page.presence="hidden";
}

Note: The layout event ensures that the trailing page always falls on an odd number, even if the end user alters the form contents. Such alterations cause the layout:ready event to run and adjust the page numbers accordingly.

Rendering a trailing page in LiveCycle Designer ES

LiveCycle Designer ES includes functionality in the Master Pages to handle duplex printing.

  1. Add Master Pages for odd/even numbers, for the last page, and for the blank page.
  2. Using the Printing option in the Master Pages page set, set up the form for duplex printing.
  3. For the odd/even Master Pages, choose the appropriate option in the Master Page >Pagination tab under Odd/Even.
  4. For the last page, choose the Last Page option in the Master Page > Pagination tab under Placement.
  5. For the blank page, choose the Blank Pages option in the Master Page > Pagination tab under Odd/Even.
  6. For the body page that occurs just before the trailing page, choose Go To Even Page in the After settings under the Pagination tab.

Sample files

Here are some sample file showing the solutions as outlined above for Designer 7.1 and ES.  I have included some test data files also to test the solutions with different page numbers.  You can import the data files into the XDP templates using Designer to test the solutions.

sample_files

reference: (181512630)

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)