Reader DC Not enough data for image (2021.011.20039)

Forum|Forum|4 years ago
January 17, 2022
4 replies
2565 views

Hello,

since Update 2021.011.20039 we get some errors when opening our scanned documents. Not all but some.

Error: Not enough data for image

The document can be open with edge and ran without problems with adobe even bevore the update.

Does anyone have the error or a workaround ?

Kind regards

This topic has been closed for replies.

Correct answer JUSTUS22696051zl6j

edit 2. Now i did my first own scans to see what happened. I scanned personal A4 paper and when i opened it in Adobe Acrobat DC, it looked good. But when i embedded the file in Microsoft Excel, the same problem occured with the previous one that i described.

Any idea what can i do? It looks to me that the problem is not in the pdf-files that i embed.

Should i try to reinstal my AA DC or Microsoft Office apps?
Regards,
Justus

Edit 3. I Finally fixed the problem. I tried the "Fix the install"-section and it worked, no more problem.

Regards,

Justus

M

Marcus22688169cb9lAuthor

Participating Frequently

Hi Sweta,

After the update to 2022.001.20117, the problem with older documents that were scanned in color with JPEG2000 unfortunately still exists.

M

Marcus22688169cb9lAuthor

Participating Frequently

Hello Sweta,
we just installed version 2022.001.20085. Unfortunately it doesn't fix the error. The same mistake. "Not enough data for an image."
We cannot install the updates, otherwise we will not be able to open the scanned documents. But this is also a security problem. Last patch October 2021.
Can you open the pdf files from us? We cannot open them on any of our systems with Adobe Reader. Windows 10, Windows Server 2016 / 2019.
With MS Edge we can open the Files. It works with Firefox too.Only Adobe Reader after 07/21/20099 causes problems.

Need Help

Regards,
Marcus

M

Marcus22688169cb9lAuthor

Participating Frequently

Same error with the Version 2022.001.20085. 😞

M

Marcus22688169cb9lAuthor

Participating Frequently

It looks like the problem occurs with PDF-A dokuments.