Hi guys,
I wasn't sure whether to post this here or on the connectivity forum. But, on balance, I think here...
Issue: Occasional corruption of multi-page (between 50 - 150 pages) scan to email as a .pdf.
You could scan a 100 page document and get the problem, re-scan it and maybe get the problem for a 2nd time or maybe it will be fine on the 2nd time of scanning. Proper intermittent.
It doesn't appear to be a size issue, most times it's a document with at least 50 pages which displays the issue though.
The message on the PC screen whilst scrolling through the document is "not enough data to make an image (14)" when viewing via Adobe Reader. Also, there are pages missing, anywhere between 10 to 40 consecutive pages.
Sometimes the document won't open at all, you just get a message about the file being damaged or corrupted and that's it.
I have tried using a different .pdf Reader and have the same issues as above, missing pages.
I've never been able to recreate the problem on demand or ever, only seen the end result of the corrupted pdf.
The C454e F/W is up to date, Adobe reader is current version. Client using MS Office suite (Outlook destination for scan to email) hosted online by their I.T. provider.
I had a look online and found all sorts of Adobe related problems with corrupt document. Could it be this?
Further research revealed what happens to the pdf once it leaves the Bizhub.
This is my understanding of what happens.....the pdf gets created inside the C454e, the pdf exits the machine thru the network cable and makes its way along the path the SMTP address is pointing to. When it reaches a certain point on its journey the pdf may get encoded, if might not, this is down to the provider of that service. If the pdf does get encoded, it also gets decoded when it reaches its destination. I think Outlook does a bit of this. Some sites indicate that this could cause corruption of pdf documents. Other sites suggest that when a pdf comes back in to the building (offsite hosted Exchange) it will be 'sniffed' by a router. This sniffing could cause packet loss which in turn could cause the pdf to become corrupt.
Then there's the antivirus software which will interrogate the email attachment, this also has been known to corrupt pdfs
I did a fair bit of reading, some of which sunk in, some didn't. In summary, I'm surprised with everything going on, anything works at all!
I have never heard of this problem being caused by a KM device. But this is a new installation and the perception is it's the KM which is creating a corrupt pdf in the first place. Unfortunately I can't ever recreate the fault. Tried Compact pdf too, but never goes wrong with any consistancy. This is causing some real problems for the client and they are kind of stuck in the middle of the Bizhub and the IT provider.
We have emailed their IT and the initial response is that the Bizhub is the cause of the corrupt pdfs.
Trying different compression settings has done nothing, it never goes wrong when we are onsite. Even if it did, we still wouldn't be able to prove anything conclusively.
Anyone come across this before of have any idea?
Thanks
Taminol
I wasn't sure whether to post this here or on the connectivity forum. But, on balance, I think here...
Issue: Occasional corruption of multi-page (between 50 - 150 pages) scan to email as a .pdf.
You could scan a 100 page document and get the problem, re-scan it and maybe get the problem for a 2nd time or maybe it will be fine on the 2nd time of scanning. Proper intermittent.
It doesn't appear to be a size issue, most times it's a document with at least 50 pages which displays the issue though.
The message on the PC screen whilst scrolling through the document is "not enough data to make an image (14)" when viewing via Adobe Reader. Also, there are pages missing, anywhere between 10 to 40 consecutive pages.
Sometimes the document won't open at all, you just get a message about the file being damaged or corrupted and that's it.
I have tried using a different .pdf Reader and have the same issues as above, missing pages.
I've never been able to recreate the problem on demand or ever, only seen the end result of the corrupted pdf.
The C454e F/W is up to date, Adobe reader is current version. Client using MS Office suite (Outlook destination for scan to email) hosted online by their I.T. provider.
I had a look online and found all sorts of Adobe related problems with corrupt document. Could it be this?
Further research revealed what happens to the pdf once it leaves the Bizhub.
This is my understanding of what happens.....the pdf gets created inside the C454e, the pdf exits the machine thru the network cable and makes its way along the path the SMTP address is pointing to. When it reaches a certain point on its journey the pdf may get encoded, if might not, this is down to the provider of that service. If the pdf does get encoded, it also gets decoded when it reaches its destination. I think Outlook does a bit of this. Some sites indicate that this could cause corruption of pdf documents. Other sites suggest that when a pdf comes back in to the building (offsite hosted Exchange) it will be 'sniffed' by a router. This sniffing could cause packet loss which in turn could cause the pdf to become corrupt.
Then there's the antivirus software which will interrogate the email attachment, this also has been known to corrupt pdfs
I did a fair bit of reading, some of which sunk in, some didn't. In summary, I'm surprised with everything going on, anything works at all!
I have never heard of this problem being caused by a KM device. But this is a new installation and the perception is it's the KM which is creating a corrupt pdf in the first place. Unfortunately I can't ever recreate the fault. Tried Compact pdf too, but never goes wrong with any consistancy. This is causing some real problems for the client and they are kind of stuck in the middle of the Bizhub and the IT provider.
We have emailed their IT and the initial response is that the Bizhub is the cause of the corrupt pdfs.
Trying different compression settings has done nothing, it never goes wrong when we are onsite. Even if it did, we still wouldn't be able to prove anything conclusively.
Anyone come across this before of have any idea?
Thanks
Taminol
Comment