Skip to main content
November 26, 2013
Question

No Pages Selected RDS Server 2012r2

  • November 26, 2013
  • 13 replies
  • 42823 views

Hi All

We are currently having troubles which seem to be random in nature printing only from Adobe PDF across three clients running on the below configuration.

  • Server 2012 r2 RDS (terminal Services) Hyper v instance
  • Adobe Reader 11.0.5
  • each of our three clients have a dedicated print server and all printers are shared network devices deployed by group policy.
  • Each RDS server has 15 to 25 user sessions

All users have no problem printing from any other app but when printing from adobe reader some users depending on the user and the printer (randomly) the user will not be able to print with the "no pages selected" dialogue box coming up.

For instance one user will log into their rdp session and will not be able to print pdfs to one printer. But another user can print from adobe no problems to the same printer.

Trouble shooting so far:

  • Re install Adobe
  • Ensure all drivers are at latest version V4 drivers where available and V3 where not. (Printers are HP upd and Xerox Docucenters)
  • pdf/a view mode set to never
  • Disabled Enhanced security mode and protected mode at start up.
  • Tested using auto rotate selected and not
  • changed the fit to page/shrink to fit etc options
  • Turned off advanced printing features on the printers.

If anyone could help this would be greatly appreciated as I am at the point of pulling my hair out and so are our clients.

Cheers

Luke

This topic has been closed for replies.

13 replies

Participant
August 19, 2016

Hello,

We are currently getting this issue.

Followed by "There were no pages selected to print"

We have tried everything in this forum and in the following links and still no joy:

http://puters.net/windows-server-2012-r2-2/printing-in-remote-desktop-2012-r2/

http://www.jesperhassing.com/?p=76

We are running Windows Server 2012 R2, XenDesktop 7.8 in PVS environment, Adobe Reader DC and Acrobat Pro DC - all patched to latest versions.

Testing has shown that the issue likes to crop up after a user session has been sitting in a disconnected state for 30-40 mins, however this is not always an actuality.

Default printer seems to disappear (no green tick) when the error occurs.

Printing works fine with all other applications.

If you manually map the printer, it prints PDFs fine.

Printers are mapped via Citrix Studio policy (we previously had them mapped via Citrix GPO in Windows but this made no difference)

We have also done a full uninstall and reinstall of Adobe.

Does anyone have any more suggestions?

Thank You

Andrew

Participant
September 21, 2016

We have just managed to finally fix this issue after following everything in these forums and more.

Running Windows Server 2012 R2 with XenDesktop 7.8 VDA

It appears the fix for us was to change the account used by the Citrix Print Manager Service on the VDA.

Go to the log on tab of the service, and select "Local System Account" and tick the box to Allow service to interact with desktop.

Hope this helps someone, it drove us nuts for months.

TheWizardKs
Participant
July 26, 2018
michaelu90566260
Participant
February 8, 2016

Here is a link referencing the previous write up.  Seems like mine are back up and running (fingers crossed)

Printing in Remote Desktop 2012 R2 | puters.net | All about fixin' puters

Mantobrew
Participating Frequently
November 30, 2015

The silence is deafening

EnterpriseHelp
Inspiring
November 30, 2015

This is a 3rd party issue related to the print environment and is not caused by Acrobat. Read the thread and associated links.

hth,

Ben

ThomasITEO
Participant
December 1, 2015

Then why is it only Adobe Reader that has the issue. And not all the other apps that print?

ThomasITEO
Participant
September 22, 2015

We see this too on multiple customers. Are Adobe ignoring this issue?

Participant
September 24, 2015

Hi Guys

Any news about this subjet?

I have the same issue, 2012R2, multiple users RDP, abode DC and for some users they can't print. I tried with foxit but printers are not all listed.

Participant
March 30, 2015

Just off the phone with Adobe.    The word is acrobat 10/11 is not compatible with 2012r2 and wait until Adobe Acrobat DC come out in few weeks.

Participant
June 23, 2015

We do have the same issue.

print server is a sbs 2012 - terminalserver is a 2012 R2 standard.

Adobe DC does not fix the solution, as aardum says, its related to Print processors / drivers and so on.

Ohadf-GICqiQ
Participant
March 4, 2015

Hi guys,

Don't want to wake the dead here but I've been struggling with the same issue for the past week and went through all step suggested.

If all fails like in my case and you are using UPD with your RDS 2012, Disconnect the user, go to your UPD store location, rename the user's UPD to xxx.old and log in with that user again.

Worked for me, The UPD was re-created and the user issue was magically solved.

Last resort but it worked.

Hope it'll be useful.

Cheers,

Ohad

September 8, 2014

We are experiencing the same problem, i.e. the ‘no pages selected’ message box when printing documents from Adobe Reader.

The issue occurs at multiple customer sites. They use a variety of printer drivers (HP, Sharp, Kyocera, and Canon). The common factor is the use of Remote Desktop Server 2012R2.

Following the tips & guidelines in this thread (and the Digital Zombies article) has certainly reduced the problem, but not totally eliminated it.

Restarting the print spooler on the RDS host (temporary) resolves the problem.

Has anyone any additional tips or tricks to permanently fix this issue?

Participating Frequently
September 8, 2014

ArenaceousYeti,

If you like, you can PM me your e-mail and I can help you troubleshoot the issue.  As I mentioned previously, I find that the print processor is the biggest culprit, so please confirm that all your printer drivers are using winprint.  Also, what server OS are you using for your print server?  When the issue happens next, even though the printer on the server may be set to winprint, check the user's print processor for the offending printer when you log onto their session and check there.  They may have connected to the printer before you made the change to the print server.  I setup a logoff script that deletes all printers for our users, and then when they log on, all of their printers have to be remapped through group policy.  You may want to implement a similar strategy for about a month until you can be sure that everyone's old printer connections have been cleaned up.

September 10, 2014

@aardum: You hit the nail right on the head. Indeed, there were still some references to 3rd party print processors (hpcpp170 from the HP UPD, see member ‘hardcrack’ earlier in this thread) in the users’ terminal server profiles. I’ve changed these to winprint.

By the way: even though the user’s default/primary printer is using winprint, they still can’t print PDF documents to it if the problem occurs.

The print server is, just as the RD server, running Windows Server 2012 R2.

We will evaluate the situation in a couple of days and let you know the results.

Off topic: member ‘idtent44’ mentioned the ‘duplicating printers’ issue. We are also experiencing this. I wonder if the two problems are related.

Participant
June 25, 2014

I had quite the same problem.

try connecting to the printer with full domain name

\\printserver.xyz.local\printername instead of \\printserver\printername

that did the trick

greetings

Participating Frequently
June 25, 2014

I'm currently writing it up.  It's quite lengthy, but I'm hoping it will be thorough enough to help a lot of people.  The reason connecting with the FQDN instead of NetBIOS name worked for dekinderw is because it was creating new printer connection in the registry.  It's basically a band-aid fix, and the issue will most likely resurface.

June 25, 2014

Hi all

We're suffering with this same issue, it's very frustrating for our users!

Is ThinPrint a viable solution to resolve this? Or do you guys think it's a more fundamental issue with the printing subsystem on 2012 R2?

I've had other strange problems on our RDS box as well, removed printers reappearing, it all seems to point to the client side provider.. See the TechNet post here:

Problem with multiple instances of shared printers being installed on client computers when the spooler service is start…

Participant
June 5, 2014

Since we're posting workarounds

I've got a .cmd script that users can run on demand that wipes out all their printer connections and logs them out.  When they log back on their printer connections are reestablished and printing works again (until it doesn't).

Crude, but it allows the end user to work around the problem.

printreset.cmd

______

@echo off

echo Run this to reset your printers.

echo -

echo WARNING - This script will log you out of Windows!

echo Please close open documents before continuing!

echo -

echo Press CRTL-C to cancel or any other key to continue...

pause

reg delete "hkcu\printers\connections" /f

pause

logoff

______

Participating Frequently
June 5, 2014

Nice! I like it.  Instead of doing a logoff, couldn't you just have it run a GPupdate /force?

Participating Frequently
June 12, 2014

aardum, did you finally opened the ticket with Microsoft? Could you provide me the number? I hope today I'll be able to open mine (was waiting for the partner contract renewal).

Participating Frequently
May 26, 2014

I've this problem too! Pretty much same environment. It's very annoying, and I've tried all the points in the first post.

Does anyone have a final solution? I'll give a try to aardum suggestion...

Participating Frequently
May 27, 2014

Unfortunately the issue has resurfaced.

Interesting to note: When I have this issue with Adobe, if I try to print from Foxit, the printer is missing from the drop down.  This would lead me to believe it's an issue with connecting to the printer, but then why do all other applications print just fine? What is it about PDFs that is causing this issue? 

Participating Frequently
May 27, 2014

About your suggestion, AFAIK, it's the same if you go to the printer in your print server and un-check the "Render print jobs on client" or something like this. I've not tried yet, and if the problem it's still appearing in your environment, I will not do.

One thing I've tried too is to exclude the AppData\Roaming\Adobe folder from the roaming profiles (my setup have 2 RDS servers, with roaming RDS profiles), and this has not change anything, the problem still persists.

Today I've uninstalled Adobe Reader XI (11.0.7, to be precise), and I've installed latest Sumatra PDF. It's very lightweight, and I will give it a try to see if it works with no issues. Will post an update in a week or so if it (still) runs well.