On searching further through the Reader X forum I came across the following suggestion, as posted by McTimotei on April 26, 2011:
After opening Reader X, navigate to Edit/Preferences/General, untick the "Enable Protected Mode at startup" box at the foot of the form, and restart Reader X when prompted.
This appears to have resolved my problem (thanks, McTimotei). But why was this difference introduced in the latest release without any warning to users? By making this change am I exposing my system to any problems?
we have provided the workarounds for Adobe Reader 10.1.2 print issues at http://kb2.adobe.com/cps/928/cpsid_92870.html
Meanwhile, we are working on providing a permanent fix to this and should soon roll out the same.
some of my customers are also using WInXP SP3 with the new 10.2.1 of Adobe Reader. Since the update they have also problems with printing documents. but the reader isnt crashing. the problem is that adobe reader shows a doubled default printer and uses the "cloned" printer for default. the cloned printer has no print funktions and you are not able to open the printer settings. you have manuely set the right default or another printer to print the dokument. the problem is, that they use the reader to print out automaticly generated dokuments.
example: winxp default printer: \\server\Printer_Share
this issu is happening on windows 2003 sbs with winxp clients ans windows 2011 sbs and winxp clients. the sbs are the printservers.
any ideas on this?
Please use the fix provided for Reader 10.1.2 at: http://kb2.adobe.com/cps/928/cpsid_92870.html to solve your issue.
Avoid disabling the Protected Mode, to ensure that your system is not vulnerable to security threats.
I reinstalled the 10.1.2 update. I tried to run the patch and the patch told me that I did not have Adobe Reader 10.1.2 installed. Perhaps that is because I have the full Adobe X Standard. So I attempted to print something and I noticed that the Print on Both Sides checkbox was checked. So I unchecked that option and the problem was solved.
I am sure you are finding out that everyone uses Adobe Reader and that outside of corporate users, do not have duplex printers. Even most small corporations don't have duplex printers. Having the checkbox checked by default was not a good idea.
Thank you for your attempt at helping.
One more comment. As a software developer, when I add new features to the software I am working on I take great pains to ensure that my existing users are minimally affected by whatever changes I make. The new features are available for them to use, but it's their choice to use them or not use them when they feel it's appropriate. Rather than defaulting "Print on Both Sides" to checked. On the installation dialog, below the progress bar you could have a panel showing people what new features are available. Then the users who have duplex printers can choose to use this option.
The patch provided at the above link as provided in your post seems to have fixed my problem -- thanks.
I must concur with ridawg however, that this situation should never have arisen. As a former software development / maintenance guy I agree that it is very important not to introduce unexpected changes in the behavior of an application (even when, as I have found to my cost, the change consists of the correction of a known and documented bug!). When such a change is absolutely necessary, the update information should make this absolutely clear to the user before the update is installed, along with a recommended circumvention.
Message was edited by: ʇɐb ɹəuəllıʍ - corr. URL link.
This patch does not fix our problem. We are still experiencing the issue in our Tokyo Office after this patch was applied.
The Tokyo machines have the Japanese MUI for windows, we believe that could be a reason.
Adobe should not release something that is not fully tested. ALL of our users in Tokyo are having this issue.
Other other fixes would be appreciated also a possible description of what the CPSID_92870 patch actually does on the back end would be great too. That way if in the MUI something that hasn't changed and needs changing it would be easier to distinguish.
I would like to set up an online connect session in order to gain more clarity on the issue faced by you. Could you please send out an email at email@example.com so that I can send you an invite for the same?
Genghis K. wrote:
We are still experiencing the issue in our Tokyo Office after this patch was applied.
Have you tried both solutions in http://kb2.adobe.com/cps/928/cpsid_92870.html ?
I have no problems printing from Japanese Adobe Reader 10.1.2 on Japanese Windows.
I have found another possible bug affecting network printing with 10.1.2 in Protected Mode on XP SP3 machines that has not been previously documented:
A number of users in one office were not able to print with 10.1.2 in Protected Mode (even with the printing hotfix/patch previously released) to their default printer; however they were able to print fine with 10.0.1 in Protected Mode OR by disabling Protected Mode in 10.1.2. They could print to Microsoft XPS Document Writer, however.
The cause was determined to be an issue with capitilization of the printer name in the registry! 10.1.2 in Protected Mode seems to be sensitive to this for some strange reason, though other apps don't care.
Check the following keys and ensure the capitalization of any references to name of your printer (or UNC path of the printer share) is consistent:
In our case, the reference to the name of the default printer was in lowercase, while the printer path recorded under settings was in UPPERCASE. Changing this to match immediately fixed the problem.
Atul - thank you for trying to fix the problem. I have downloaded and installed the _92870 fix and rebooted. This did not fix my problem.
When I'm viewing the pdf document, I select the print option, this brings me to a screen where I'm able to select my printer etc, once I select PRINT from this screen, a dialoge pops up asking me to "save as". The PDF never prints regardless of whether I save the document (per the Save As screen) or not.
Any other suggestions.
Thanks, Scrawner! I don't know how you discovered this, but it did lead to a solution for us (after CPSID_92870 did not...)
In our case the server names for the problem printer were identical in Connections and Device (it has no entry in Settings), but with the first letter capitalized. Printers that weren't causing problems had the server name all lower case, so I changed the server name of the problem printer (in both places) to lower case, after which Reader 10.1.2 had no problem.
Please pay attention, Adobe!