MP 5002: Corrupt PDF Files

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sandmanmac
    Field Supervisor

    Site Contributor
    2,500+ Posts
    • Feb 2009
    • 3960

    #1

    MP 5002: Corrupt PDF Files

    Helped a colleague install a supposedly refurbished MP5002 the other day.
    PDF's scanned to email are often (not always) corrupted.
    What you see when viewing this document, will depend on what viewer you use (Adobe/Foxit Reader/ Edge, Etc.)
    Sample PDF.pdf
    I was basically using 2 of their email addresses to send test scans. They would often get the message "Not enough memory to open file" (or similar), when using Adober reader.
    Most of the other programs I used had varying results - from Blank pages , to all black .
    Almost all of the firmware was very outdated, so I updated to fairly recent versions of all, but to no avail.
    I don't know right now if it happens when scanning to folder.
    I also performed a scanner memory clear
    I don't have any skin in this game at the moment (not my machine or customer), but it is an interesting problem, that I'd welome any feedback on
  • KenB
    Geek Extraordinaire

    2,500+ Posts
    • Dec 2007
    • 3945

    #2
    Re: MP 5002: Corrupt PDF Files

    Could be a RAM problem.

    Try the same doc at different resolutions, and see if it changes.

    I had a very similar problem with eCopy (server based) a few years ago.

    Turned out to be messed up memory in the MP 4001.
    “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

    Comment

    • slimslob
      Retired

      Site Contributor
      25,000+ Posts
      • May 2013
      • 36222

      #3
      Re: MP 5002: Corrupt PDF Files

      Try changing the compression settings.

      Comment

      • sandmanmac
        Field Supervisor

        Site Contributor
        2,500+ Posts
        • Feb 2009
        • 3960

        #4
        Re: MP 5002: Corrupt PDF Files

        Thanks for the input guys.
        I did try a couple of different resolutions, and compression settings.
        Neither made any difference.
        I'm not even sure where he stands on this situation at the moment, or if I'll be contacted to go back and have another go at it.
        I suggested that I was leaning toward something wrong with the controller, so he may just go ahead and try complete unit from another machine, which would resolve the problem if it were just a Ram issue (which sounds interesting)

        Comment

        Working...