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

Documents saved using Print to PDF function give access denied when opened.

Community Beginner ,
Jul 05, 2023 Jul 05, 2023

I am hoping someone can offer some insight outside of the usual suspects as to why this might be. 
I have a customer who uses the print to PDF function to save files on to the organizations shared drive for easy consumption by others at the organization. After a recent Windows Update the PDF converter dissapeared from the print options and when reinstalled the user could no longer open documents saved to the shared drive.
If the option is instead used to save locally, the PDF can be opened as normal. 
I have turned off "Run in App Container" and "Enable Protected Mode at Startup" options as well as specifically trusted the drive location and it still gives the same error.
Adobe Reader is latest version, completely patched and no errors given on repair scan.

TOPICS
Edit and convert PDFs , General troubleshooting
1.5K
Translate
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
Community Expert ,
Jul 05, 2023 Jul 05, 2023

The "Print to PDF" command is not a part of Reader (which can't create PDF files, only display them). I'm guessing it's a Microsoft feature, so this question should be asked in an MS forum. Reader only opens the files, if they are not corrupt.

By the way, I hope they're not doing that on pre-existing PDF files (known as "re-frying") as that's a very bad practice...

Translate
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
Community Beginner ,
Jul 05, 2023 Jul 05, 2023

@try67 
Thank you for the advice, the problem may be in the functionality of the print to PDF at the OS level I will open a post in MS forums as well to seek insight on that side of things. 
Thankfully they are not re-frying (phew), that was an early check in the process of troubleshooting this for me.

Translate
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
Community Expert ,
Jul 05, 2023 Jul 05, 2023

By the way, does it work if you copy the file to the local computer and then try to open it using Reader? If so, it's a permissions issue, most likely.

Translate
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
Community Beginner ,
Jul 05, 2023 Jul 05, 2023

It works even if the file is fully moved to the shared drive from the local, not just copied. But I am not entirely sure where that permission interaction would be held up. Can you give the print to pdf function specific permissions per workstation?

Translate
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
Community Expert ,
Jul 05, 2023 Jul 05, 2023

It's not the PDF printer, but the folder on the network drive where the files are saved. If you only have read-only access to it it might prevent the application from opening it properly (for example). I would suggest talking to your network admin about this issue.

Translate
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
Community Expert ,
Jul 06, 2023 Jul 06, 2023
LATEST

[MOVED TO THE ACROBAT READER DISCUSSIONS]


Acrobate du PDF, InDesigner et Photoshoptographe
Translate
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