• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Print Dialog throws an error when the printer doesn't have "Everyone Print" permissions.

New Here ,
Mar 27, 2020 Mar 27, 2020

Copy link to clipboard

Copied

We have been using Adobe Reader for years without any issue.  We did the Server 2016 updates a few days ago and it started throwing a fatal error when you click on print.  You don't get the print dialog.  It just throws an error and shuts down.

 

We have a terminal server and we have people from several different locations logging in.  Each location has several printers.  To avoid confusion, we only give permissions for a particular printer to people in that location (Yes people from Columbus will try to print in Augusta and wonder where their print out went).  In any case, this was working fine until this week.  It might have been the Adobe Reader update or the Server 2016 update, but if your default printer is set to a printer that doesn't have "Everyone Print" permissions, the print dialog won't even show up.  If you set your default printer to a printer that does have "Everyone Print" permissions, you can use the print dialog to switch to the restricted printer and it will print fine.  The only problem seems to be having your default printer set to a restricted printer.  The person doing the printing definitely has permissions to use the printer.  It is like Adobe Reader is using a different security principle when it is enumerating the printer list in the Print dialog.  Anyone else having this issue?  Anyone have a solution?

 

Thanks,

Jim

TOPICS
Crash or freeze , Print , Windows

Views

124

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation