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.

[sschindlbeck]

We are also having the same issue with files that worked fine in older versions of Adobe Acrobat Pro. Current version is 2018.011.20038. We can work in the file for some time before the message appears, but when it does, we cannot save our work. This can cost me hours of work. I was thinking about reverting to the old version but I can't find the licensing info to re-install. The only thing I can do at the moment is make sure I'm saving every 15 minutes or so to avoid losing too much time when the error occurs.

[TaylorChandler]

Can’t share any files as they contain sensitive data, but this is not isolated to a couple files. This happens with a ton of them.

[ppg5800]

both myself and my customers are still having the same issue.  here is a sample doc.

Shared Files - Acrobat.com

[ppg5800]

sorry, use this file for example:

Shared Files - Acrobat.com

[andreib77481166]

We also have this problem.

You have any news for us ?

[XtL_BCN]

Hello, I have this issue too with Adobe Acrobat Reader DC 18.011.20040

the failure happens after a while that a file is open, at which point it will affect the other open files one after another - working on pdf reports with pictures and text overlapped, seemingly generated from excel and / or ppt files - can't forward any for they are absolutely confidential.

like some other claims above, it all started a few months ago, probably after one of the corrupted updates

I executed the Installation repair feature, the failure is still there. and no other update is available in this moment

copied under the report that was generated to send out, in case it rings some bell to someone, somewhere

thank you very much

Acrobat Detail:

   Sandboxing: On

   Captive Reader: No

   Multi-Reader on Desktop Support: Off

Available Physical Memory: 632288 KB

Available Virtual Memory: 3488984 KB

BIOS Version: DELL - 1072009

Default Browser:

Graphics Card:

    Version: 0.0.0.0

    Check: Not Supported

Installed Acrobat:

Installed Acrobat: C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe

    Version: 18.11.20040.281318

    Creation Date: 2018/05/11

    Creation Time: 7:12:10 AM

OS Manufacturer: Microsoft Corporation

OS Name: Microsoft Windows 10

OS Version: 10.0.16299

Page File Space: 4194303 KB

Processor: Intel64 Family 6 Model 78 Stepping 3  GenuineIntel ~1992  Mhz

Time Zone: China Standard Time

Total Physical Memory: 4060384 KB

Total Virtual Memory: 4194176 KB

Windows Detail:

   Tablet PC: No

   Starter Edition: No

   Media Center Edition: No

   Slow Machine: No

Installed plug-ins:

    Version: 18.11.20040.281318

    Creation Date: 2018/05/11

    Creation Time: 7:12:10 AM

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\AcroForm.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\Annots.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\DigSig.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\EScript.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\IA32.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\PDDom.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\PPKLite.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\Spelling.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\Updater.api

C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\weblink.api

[Karl Heinz Kremer]

Let me repeat what was said before: If this happens with just one file, or files from the same source, it's very likely not a bug, but a problem with the PDF file(s). If this happens with random files - or all files, it is certainly possible that there is another bug in this area of functionality. From the outside, you and me are not able to determine which of the two it is.

I don't work for Adobe, so I don't know how exactly their bug report triage system works, but having working on large projects for other companies, I can tell you that the more often a problem is reported in a way that makes it repeatable in the lab, the more likely it is that you will get a fix within a reasonable time.

The only reliable way to get in touch with Adobe's engineers is via the bug reporting form: Feature Request/Bug Report Form

Sometimes Adobe staff posts here, but that does not mean that they will necessarily see all replies. When you post a bug report, make sure to include all relevant information, and if possible, share the file(s) that make this bug show up with them.

[XtL_BCN]

well in my opinion the source is very likely to be the cause. I work with a computer from Spain with some national version and international software, the failing reports I mention mainly come from a chinese organisation which I don't know what software they are using, or how they generate said reports, MSO save to pdf feature or some other pdf generator.. and the failure don't seem to happen on the files I generate myself. also their files contain some chinese characters for which I had to install an adapter too. on the other hand, my colleagues with computers in similar conditions like mine don't seem to have this problem.

will try to report on the link you facilitated, thank you very much

[sfr22]

Hi,

We are also experiencing this issue in our company. It is happening to a substantial amount of our PDF files. I certainly believe it is a bug. Are Adobe working on a fix?

[Karl Heinz Kremer]

Adobe does rarely comment publicly about what bugs they are working on. I can only recommend again that you file a bug report with as much information as possible: Feature Request/Bug Report Form

[marcosm79504128]

I have the same problem and my software is up to date

[Test Screen Name]

Then it isn't the same problem, because it was fixed. Same message maybe, but a different problem. Often it is a real problem with the PDF. Exactly how was the PDF made, and what is your exact software version?

[aliceyoung]

I have the exact same problem with just one page in a 50+ page PDF. The pages were made from TIFF scans, no compression. Everything else I opened the file with worked fine, I could even print it, but Acrobat Pro DC would barf with "Insufficient data for an image" ... But I found a solution. Open the "bad" file with Mac Preview, save as PDF to a new file, then open the saved file with Acrobat. No error. Perhaps the best fix for this bug is an Applescript to run the files through Preview.

I find it really bizarre that the creators of the PDF standard can't even make expensive tools that work properly with that standard.

[scottg56950285]

I am seeing this problem with the latest version of DC Reader downloaded today.  The exception code 0xc0000005 indicates a memory access violation.  It seems that explorer is crashing when opening certain PDF's.  These same PDF's open fine with Foxit Reader.

Log Name:      Application

Source:        Application Error

Date:          9/4/2018 10:37:06 AM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      blah blah blah

Description:

Faulting application name: explorer.exe, version: 10.0.14393.1378, time stamp: 0x594a147b

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x004afbe9

Faulting process id: 0x164c

Faulting application start time: 0x01d44475dfc00597

Faulting application path: C:\Windows\SysWOW64\explorer.exe

Faulting module path: unknown

Report Id: 9cffb0ce-ccec-432f-a34e-81b8bec315b0

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

[Test Screen Name]

This thread is about the problem (with many causes) where the user gets the message ""Insufficient data for an image". This does not seem related to the crash you are getting.

[scottg56950285]

It is the immediate error logged when getting the error from Adobe Reader when opening a PDF; "Insufficient data for an image."

[Test Screen Name]

This seems a different issue. Many people report "insufficient data for an image" but Acrobat or Reader then continues with a more or less blank page. Nobody has reported a crash. Especially, nobody has reported that when Reader gets this message that Windows Explorer crashes. Perhaps you can give more background, on the basis that this is a new and undiscovered issue rather than an old and well known one.

[MalteT]

The issue is still not fixed.

Seems it happens when files are linearized, so that a web based pdf renderer can get the content of the first page with loading as little data as possible (less requests).

This is such an optimized PDF, created from pptx: presentations_2017-10-11_ODF_Plugfest.pptx.pdf

Is there a better way to report this issue, as placing additional comments into this thread?

Best regards

Malte.

[Test Screen Name]

Can you post that publicly? That asks for a Microsoft password.

[Test Screen Name]

What app did the linearization, by the way? This suggests it damaged the file, but it will need analysis to see. Also, can you share the unlinearized file.

[MalteT]

There shouldn't be a password, can you please retry? I just sent the link to my post to someone else and he could simply open. So even the Adobe forum redirect should't matter Maybe your browser wants to log you in because you have been logged in there before?

The PDF was created with a version of LibreOffice where we are currently optimizing the PDF conversion routines for creating linearized PDF.

File should be fine, opens well in all other PDF viewers.

But if something should be wrong with the file, please let me know what that should be.

[Karl Heinz Kremer]

You may want to use the Acrobat Cloud to share the files. A while ago I wrote up some instructions about how to do that: Share Documents via Adobe's Document Cloud - KHKonsulting LLC

We need both files: The original one, and the one after linearization was applied, and exact instructions about how to get from the first one to the second one.

If you can show a reliable way to create such files, and the problem is really in Acrobat and not in the method of how the file was created, that will hopefully help Adobe's engineering team to fix this instance of the "insufficient data" problem.

[Test Screen Name]

Microsoft will only deliver the file to someone logged on to their network. But I won’t.

[MalteT]

Here a link into Adobe Cloud, PDF file

Shared Files - Acrobat.com

Here a link to the PPTX:

Shared Files - Acrobat.com

Unfortunately I can't provide access to the modified converter, as it runs on internal systems here. So the PPTX probably doesn't help much, but in the end the generated PDF should be sufficient for analyzing why Acrobat Reader doesn't like it.

[Test Screen Name]

Tech report for the people who make the PDF creation or optimizing software:

Page 1 has an image "Im5". This is width 891, height 180, bits per component 8, colorspace DeviceRGB.

The expected image data is 891 x 180 x 3 bytes = 481140.

However, the stream data decodes to 160,380 bytes.

I observe this would be correct if there were one byte per component; since it is using the DCTDecode filter this may be a greyscale JPEG file treated as RGB.

Tip to your people:

Look on page 1 for an image that is 891 by 180 pixels, especially a greyscale 1. Replace the image with a new one in colour.