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; } } }

Exception in Primitive Error

leala_abbott

When attempting to download assets in Mediabin (TIFs and JPGS), my users are receiving the following error:

Exception in Primitive {53E24C2A}! Reason = Could not open file, Message = CGetOriginalPrimitive::ReceiveParameters() Could not copy file.
ERROR: Job {5293D031-B8F9-44CD-B914-5C13FF93E253} Setting parameters in primitive Get Original Primitive. RC = The operation failed. Check the log output for details

We are also getting the "16bit file being truncated into 8bit file" error

MediaBin Webclient Version: 4.5.3
MediaBin windows client 4.5

Please let me know if there is any other information needed...

Find more posts tagged with

Comments

msrinivas

What is the original format in which these assets were ingested in MB and what is the format that you are trying to download it in?

Are you using any transformation task while downloading?

error_digital_sig.png

leala_abbott

They are in their native formats, some were ingested as TIFs and some were ingested as Jpgs, users are downloading them in their native formats, but sometimes are trying to render TIFs to Jpgs for download. Users have tried with no rendering, rendering every download method available as to troublshoot the issue and find out what task was causing the error with no luck. Always the same error.

lyman

The 16-bit file message is only a warning. MediaBin preserves 16-bit files but when you repurpose them to other formats (the majority of which only support 8 bits files) MediaBin truncates.

The error in the Get Original primitive is more ominous. It implies that there may be something interfering with the files in the ImageDB directory. Support can provide a reconciliation script to make sure that nothing has been inadvertently deleted. Another possible cause is that a virus scan or back-up utility is holding a lock on the file in question.

Cheers,

Lyman Hurd