nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

After MediaBin 4.6 upgrade, PDFs can't be added

Bill Klish

MediaBin 4.6
Windows 2003
Adobe Acrobat 7.0.9

I have no problem adding PPT files, but PDF files that are successfully added using the out of the box Insert task on a 4.5.3 server end up causing the following error after timing out on our 4.6 server:


PrintToImage: Warning - timeout waiting for printing job completing.
Exception in Primitive {1E885AE1}! Reason = Problem in RIP.
, Message = PDFDecoder: Error ripping page content

I have left the printer named Black Ice EMF TS and made it the default printer. I have updated the MBPrintOut settings as well.

Any ideas?

Find more posts tagged with

Comments

msrinivas

How large is the PDF file and can you open up the PDF file on the MB Asset Server? And also how has this PDF been created?

Bill Klish

800 KB. It was created using the deployment agent, running the output pdf task on a ppt file. I was able to ingest the ppt file. I was able to insert the same pdf file on another 4.5.3 server. It just times out on the 4.6 server. We did upgrade acrobat from 6 to 7.0.9 as well on the 4.6 server. I believe it is still 6.0 on our 4.5.3 server.

iwTech

Hi Bill ,

Please let me know , if you still have the issue .
I faced the same issue , while installing the media bin 4.6 in conjunction with Oracle .
Please do a cross check to upload .pdf files to media bin through Windows Client .
If you are still experiencing the .pdf insertion times out issue . check your acrobat reader version.

I resolved the .pdf insertion times out issue by un-installing acrobat reader ver. 7.0 and re-installing acrobat reader ver. 6.0

Spiff

Another question to Bill: are all PDF files failed, or just this single one? Have you tried a smaller PDF file?

Not that 800KB is too big, but I am just trying to understand the problem.

Bill Klish

All Fail. I uninstalled acrobat 7.0, reinstalled 6.0 and still have a problem.

iwTech

Question to Bill:
Are you getting the same error while uploading files to
Web client / Windows client ?

Bill Klish

Here is the answer. I have installed acrobat 8, that didn't fix it. Even though the 4.6 installation manuals say not to change the name of the black ice printer to Metafile Printer, I changed the name to Metafile Printer and everything works now.

Wondering if this is a doc bug or what, but it works now.

Spiff

No, it is not a doc bug. Changing the printer name to Metafile Printer will fail the conversion of MS Office files to PDF files and therefore is not recommended.

To help solve you problem, I have 2 other questions - when you upgraded to MediaBin 4.6, have you uninstalled the old Black Ice printer driver and install the new version? If positive, did you use the same user account to do the installation as the one running MediaBin service?

Bill Klish

Great. I didn't test that and support didn't suggest that either. I will test an office doc now.

The software was installed as local Administrator, but MediaBin is running as a domain user. Shall I switch MediaBin to run as the same?

EmployeeInformation.rptdesign

Spiff

No, MediaBin service should always be run by a domain user. So, it's strongly recommended to use that same domain user account to install the new Black Ice printer driver (as well as other helper softwares such as MS Office and Acrobat).

Bill Klish

****, ok. Perhaps I missed that in the installation documentation. Will have to go back and reinstall everything then.

Spiff

I am sorry but those external applications (such as MS Office) are getting tougher on who can/can not run them. The worst case is that you can run them, but end up with incomplete/incorrect results. That why now we suggest using same user account for installation/activation.

Bill Klish

Ok, so I got around to testing this. As Metafile Printer, I can import BOTH Office and PDF files without error. So, now I am even more confused. You are saying one thing, support is saying another. Which is it?

Spiff

Take my answer.

As 'Metafile Printer', you can ingest Office and PDF files without error. But you can't retrieve Office assets into PDF files. If you don't need this Office-to-PDF conversion feature, there is no problem to keeping the 'Metafile Printer' naming. But if you do, the printer must be renamed back to 'Black Ice EMF TS'.

Go back the original issue, how is the performance in ingesting PDF files now?

Bill Klish

Looks like you are correct. We need this functionality and this is what we got when we just executed it:


Exception in Primitive {1E885AE2}! Reason = Unspecified error, Message = PDFEncoder: DLAutoPublish Error: -10 \\WOVEN-DEV-MB\MBDataDirectory\CADIn\{CEE4AD17-93BD-4244-A7B9-8CA0AA6EB3EE}\{CD0EC292-21B0-4B90-9C73-15CDCBB3FE12}.doc

So, it looks like we need to name it back and go back to the drawing board with support. How come they didn't know that we couldn't do this?

Spiff

MB 4.6 just went of door not long ago, and this change is a sharp one from previous versions.

Have you reinstalled the new printer driver (as well as MS Office and Acrobat) using the user account that runs MediaBin service? If positive, have you tried to name the printer 'Black Ice EMF TS'?

Bill Klish

I renamed the printer back to black ice... switched the owner of the MediaBin Server process to be the same user as the printer install and everything actually works now.

Thanks for the help!