Critical parse failure: Extended graphic state resource missing

[pronto007]

Hi Community,

we create PDFs in Acrobat 10 (on Mac) and send them to our customer, who comments the passages that need to be changed and sends the PDF back to us. Since last week we get the following error messages when opening the PDFs:

Critical parse failure: Extended graphic state resource missing

If we remove the comments from the PDF, it can be opened without errors, so it's related to the comments.

We suspect the bug in the customer's Acrobat version which inserts the comments and since it suddenly started last week, a recently released update. Unfortunately I can't find a version history that provide me the current release of Acrobat. However, an employee of our customer told me he is currently using the following version: 2019.008.20074 (possible on windows) Is this the current release? Is there already any information whether the problem is a bug and will be fixed soon or something else won't work anymore?

Thx & Bye Tom

[Adorobat]

Hi Tom,

As per the issue description mentioned above, you are receiving Critical parse failure error when trying to open a pdf created in Acrobat X on Acrobat DC latest version, is that correct?

Would it be possible to share one of the pdf files you are working with to replicate the issue at our end? To share the file here in the forums, refer to the steps given in this link: How to share a file using Adobe Document Cloud

You may also share the link for the pdf via private message - How Do I Send Private Message

Also, let us know the steps you are taking to create a pdf in Acrobat X.

Thanks,

Shivam

[pronto007]

Hi Shivam,

>As per the issue description mentioned above, you are receiving Critical parse failure error when trying to open a pdf created in Acrobat X on Acrobat DC latest version, is that correct?

negative, the error occurs with a PDF created in Acrobat X in which comments were inserted with Acrobat DC (Version 2019.008.20074). It does not matter which Acrobat the PDF is opened afterwards, the error occurs in every version we are using, both Acrobat X and Acrobat DC (but not the latest version). What we noticed later, however, is that the error only seems to occur with acrobats that have a pitstop version installed. We have two acrobats without pitstop, both version 10 and version DC and there the error does not occur. We then checked the PDF in Acrobat's preflight and got an error in the comments during the syntax check. Something with ExtGState "GS0", the exact wording I can find again tomorrow.

>Would it be possible to share one of the pdf files you are working with to replicate the issue at our end?

yes I can give you an example tomorrow, now I'm not in the office anymore.

>Also, let us know the steps you are taking to create a pdf in Acrobat X.

puh, we could write a book about that, what exactly do you want to know?

Thx & Bye Tom

[Adorobat]

Thanks for the info, Tom. Could you share if you are creating a pdf using Create > PDF from.... option in Acrobat X or using pdf maker in third-party application like MS Word?

-Shivam

[pronto007]

Servus Shivam,

I try to upload an example PDF shortly. if you open the PDF with an Acrobat without Pitstop, the preflight syntax check will cause this error:

Otherwise the error message in the subject will be displayed:

>Could you share if you are creating a pdf using Create > PDF from.... option in Acrobat X or using pdf maker in third-party application like MS Word?

Yes, we create the PDFs using the export function from Indesign or Illustrator CS6

Thx & Bye Tom

[Test Screen Name]

All the different symptoms seem to agree that SOMETHING is damaging the PDF (specifically, removing a "graphics state"). You need to focus on the exact workflow used, including software versions. Are you absolutely certain that the customer is using Acrobat, there are many non-Adobe products, of variable quality, and there is Apple Preview, which is frankly awful for editing.

[pronto007]

Hi MVP,

the main problem seems to be the latest version of Acrobat in conjunction with the comments. You can reproduce the problem yourself in version 2019.008.20074 by creating a simple PDF (we used PDF X1a) with a simple color- and textbox, save it and add a comment, save it again or reopen it, and then perform a syntax check Acrobat buit-in preflight. You will receive this error message:

The difference now is whether Pitstop is installed or not. With Acrobat without Pitstop you will only get the error in the syntax check, with Pitstop already when opening the PDF. It seems to be a fact that the comment function in the new Acrobat version has a bug. It's just that simple...

Thx & Bye Tom

[pronto007]

Hi MVP,

the main problem seems to be the latest version of Acrobat in conjunction with the comments. You can reproduce the problem yourself in version 2019.008.20074 by creating a simple PDF (we used PDF X1a) with a simple color- and textbox, save it and add a comment, save it again or reopen it, and then perform a syntax check with Acrobats buit-in preflight. You will receive this error message:

The difference now is whether Pitstop is installed or not. With Acrobat without Pitstop you will only get the error in the syntax check, with Pitstop already when opening the PDF. It seems to be a fact that the comment function in the new Acrobat version has a bug. It's just that simple...

Thx & Bye Tom

[pronto007]

Servus Shivam,

I sent you a private message with a link. Can you please confirm receipt?

Thx & Bye Tom

[Adorobat]

Thank You Tom for sharing the link for the file. Allow us some time to analyze the file, will get back to you at the earliest.

-Shivam

[bens_enfocus]

I have already reported this problem, with some technical details, at Annotation appearance dict missing ExtGState – Share your feedback on Acrobat DC