I'm able to open certain set of pdfs in all the softwares without error. It works even in previous versions of Acrobat reader. However, in Acrobat reader 21.001.20135, I'm getting the below error. (There was an error processing a page. There was a problem reading this document (109)).
Could you please let us know if:
We would definitely need sample PDF file where we can reproduce this.
Appreciate your help. I'll share the pdf with you privately.
For protected Mode preference: Please check under Security (Enhanced) section in preferences.
I shared the pdf that created trouble to your email. Also, I'm sharing the control panel entry for your reference.
I disabled the checkbox as you had said, restarted the app and then tried. However, it still didn't work.
Thnak you for update Prash. I have recieved your file and will be debugging this issue.
With the sample PDF file you have provided, we could reproduce the issue in older versions for Reader as well. Could you please confirm with which version was this working for you earlier? Currently we are getting badly formatted object error on content stream of the sample PDF you shared for page 1. Can you also share details like how this PDF is produced?
We get PDF files from API. Then, we use IronPDF (a C# plugin) to programmatically lay an image on top of the PDF. The initial file that we get works on Acrobat reader without issue. After we lay the image on the PDF file, we get this error only with the Acrobat reader. It opens normally in browsers (Chrome and Firefox) and a few other software. Someone raised a ticket with my team saying that their team member was able to open this PDF in their system with Acrobat reader. I don't have the information right now. Is the version really important for you to identify the issue?
One of the user in the team was able to open without error using Adobe Reader DC (32bit), Version-2021.001.20138.
Do you have any updates on this?
We have reported this issue and as per the current investigation, the issue seems to be with the file.
We have noted all the details and we are still looking into this issue.
I will keep you updated.