Insufficient data for an image

[laurab4247824]

With the new version of Adobe Acrobat DC (2015.006.30413), there are documents that were scanned and OCR by a Toshiba and e-bridge re-rite software that now give an "Insufficient data for an image" error upon opening. They can be opened in an older version of Adobe. This problem was not occurring until the update hit this morning.

The scans that don't work have some kind of image on the page -- logo, signature -- but straightforward documents seem to still work just fine.

Documents that were previously scanned and OCR'd also have the same symptoms as those files that we currently are scanning.

I appreciate any help given!!

Laura.

[lorneb87540091]

Same problem with 2022.003.20314. 64 bit. Windows 10 Pro. 10.0.19045.

Absolutely ridiculous that I suddenly can't open these PDFs without seeing this error (insufficient data . . .). I can open the same pdfs on my MacBook using Preview, or Acrobat X (10.1.9), or Acrobat Reader DC (2022.001.20112), 

Acrobat Reader DC on my Windows 10 machine is pretty much useless now. Either I get "Insufficient data for an Image", or I get "There was an error opening this document. The file is damaged and could not be repaired." Sure, sure. Yet every other program I have everywhere else can open it just fine. 

[Aaron29732182x1ee]

For anyone still having this issue, it was resolved for me by re-saving the file as an optimizied PDF. So step by step: Open file having issues -> Save as Other -> Optimized PDF -> OK (Default settings work) -> Save file with whatever name you'd like -> Open it again, hopefully with any errors. Hope this helpful.

[Rhiannon31889648rbxr]

Is there a new update that would cause this issue to occur again? My team and I are experiencing the same error today.

[N3L$]

So, this issue has a couple of threads; this one here at
https://community.adobe.com/t5/acrobat-discussions/adobe-acrobat-9-and-quot-insufficient-data-for-an...
and another one at
https://community.adobe.com/t5/acrobat-discussions/insufficient-data-for-an-image/td-p/9691197/page/...
for example.

I read most all poster's notes and I am betting that there are at least 2 reasons for this . I can recreate this error with almost every version of Acrobat and acrobat pro I've checked. my first asserted reason only appears when the PDF is opened on a network shared/mapped/mounted drive. I put forth that this appears to be due to the locally cached copy of the network share's file becoming expired or corrupted and either the OS or the acrobat app is going back after n clock ticks and finding a delta between what's in local partitioned app or graphic memory and the originally opened file on the network. why that occurs could be opportunistic locks by security software or Lord knows what else. But, it can be consistently repolicated by simply letting the network file remain open in the acrobat app for >10mins.

The other reason, I put forward, and this is largely based on what I've read from those whose post(s) portray them as an authoritative telemetry collector, is that there is a rendering issue (not an area I'm exceedingly strong in) that's preventing even local files to produce the error. /used to be a guy named @Eric Chan at Adobe that could probably solve this in a few keystrokes, but besides him being on the PS RAW team he may not be there anymore.

regardless... look to the hypothesis I've shared and test to see if you can make it happen to a locally originated file on a storage partition that has exclusive use by the app; not shared storage.

I'll keep my non-thread related criticism out of this (which, I suppose, reveals I have some of the vendor).

Be Well,

->N