We have recently seen issues with Universal printing where the print spooler clears just fine from the server but nothing comes up for the local print job. Running on Windows Server 2008 R2 64bit and Remote Application Server v16.2 Build 19048
We have no consistency when it happens or what the fix is. Sometimes its logging off all sessions and restarting the 2x client. Sometimes you can log into a full desktop and print then it works for a while and sometimes it just doesn’t work at all. Most users are using Bluebeam for their default PDF viewer. Seems to be a issue with all of our published apps but predominately SAGE Timberline 300. We’re getting to the point of moving to another solution.
That sounds frustrating! So, are you saying the print jobs don’t show up at all on local printers, even though they clear from the server?
Exactly. Sometimes we can get it working by logging off all sessions and restarting the 2x client. Other times, printing works if you log into a full desktop, but it stops working after a while. It’s just all over the place.
that’s odd. Are all users having this issue, or is it mostly with a certain application?
It’s across the board for all our published apps, but we see it a lot more with SAGE Timberline 300. Most of our users are using Bluebeam as their default PDF viewer, but I’m not sure if that’s related.
I wonder if it’s related to how Bluebeam handles print jobs. Sometimes, specific applications can have compatibility issues with Universal printing. Have you tried testing with a different PDF viewer, like Adobe Reader, just to rule that out?