Skip to main content
Participant
January 9, 2023
Question

Can't Reader Enable Documents - This document could not be Reader Enabled

  • January 9, 2023
  • 2 replies
  • 2838 views

I use Adobe X for simple booking forms to which I add the clients name. I save them as Reader Enabled then send them to the clients for them to select their booking details. Suddenly, I can't save any of the forms as Reader Enabled.

I have about 30 different forms for different products. All worked fine before. Now none of them do - all give the same message "This document could not be Reader Enabled" but no clue why. I've tried reinstalling Adobe, and tried it on a different PC. I've tried loading and saving the documents to my local drive raher than to/from my NAS. Nothing seems to make any difference.
Anyone any ideas - I've trawled the web and can't find any solutions and have bookinngs I urgently need to process.

This topic has been closed for replies.

2 replies

Legend
January 10, 2023

https://helpx.adobe.com/acrobat/kb/reader-extended-pdfs-and-adobe-root-ca-expiry.html

There is no fix for Acrobat X, XI, 2015 or 2017.

BUT, check you still need Reader enabling. Recent versions of Reader may not need it.

Participant
January 10, 2023

Thanks. Very helpful. I did wonder if that was the issue.

I was going to test if it was still required with the latest version of Reader but when I attempt to download this, I select my operating system and language and it flicks to a plain black screen. So I can't even get an up to date version of Reader! What a quality operator Adobe is!

Participant
January 11, 2023

I have now managed to get ann up to date copy of Reader (Adobe had to download it for me)! And it does indeed seem that with the latest version of Reader it is not necessary to reader enable a form for Reader users to complete it and save it.

Participating Frequently
January 10, 2023

Since yesterday this happened to me also. Did also all the testing you did on other PC etc and same result. Any pdf file i try to reader extend i get the same message. Did not find any explanation or workaround for this yet..sadly.