Invisble Assets

After inserting a large number of images into MediaBin, a tiny number failed to insert with the following exception:

Exception Server was unable to process request. --> MBException: An unhandled exception occurred (0x80040416)

This isn't a problem or unusual considering the number of inserts. So we just mark which assets failed to load, and then reinsert them.

The problem is that these assets don't seem to show up in a search, but something appears to have been inserted.

As the assets don't show up in a search, the reinsert process thinks it's a new asset, and tries to use the insertAsset method rather than the reviseAsset method. So it fails with:

Exception Server was unable to process request. --> MBException: Item added would be a duplicate. Not added (0x80040400)

Looking in the container via the windows client, I can see the assets although they don't appear to have any metadata associated with them, only a name. I don't have the option to delete them using the windows client. Trying to download the asset yields this error:

The attempted operation is not supported in the current item state. (0x80040428)

Although I couldn't delete them, I did have the option to use the cut and paste feature in the windows client, so I was able to place them in a temporary container and then just delete the container.

Although this has 'fixed' the problem, and this is the first such occurrence, I'm curious if anyone else has had similar problems and if there is anything we can do to avoid it occurring again?

Find more posts tagged with

Comments

msrinivas

Is this a custom script that you have?

lyman

"The attempted operation is not supported in the current item state. "

Some background. First this should not happen and perhaps with the logs we can figure out what is going wrong! Please get in touch with support.

What is happening is that to avoid potential name conflicts, MediaBin inserts into the database when a job is queued a "pending" image (we call them "ghosts" informally). They show up in the Windows Native Client as empty boxes. This reserves the name and avoids two images being queued that would otherwise overwrite each other.

When a job completes or fails its associated pending image is supposed to be deleted. The fact that this did not happen is a bug!

You can try going into the Windows Native Client and "deleting" the empty images, however I am uncertain if that would work. We may ave to provide you with a clean-up SQL script.

Again the mbp.log should give us an idea of what went wrong.

Cheers,

Lyman Hurd