It's all about the answers!

Ask a question

Ram exception: prefix string too short asset upload

Venu Konatham (345) | asked Oct 25 '12, 4:21 p.m.
 When we are executing a bulk upload into RAM (script written using ram api), we are getting an error that says 'prefix string too short' for each asset. and the upload is failed.

 what could be the reason for this. (Ram version used is

2 answers

permanent link
Rich Kulp (3.6k38) | answered Oct 26 '12, 10:56 a.m.
This is a known problem. Fixed in (in development) with Defect 75146.

The workaround for now is to delete the asset and recreate with no file names that are shorter than three characters. Or leave the file with the name of less than three characters alone. Don't replace it or delete it.

This is because the error occurs when trying to archive the "previous" version of the artifact before deleting or replacing it.

permanent link
Venu Konatham (345) | answered Oct 27 '12, 3:04 a.m.
 Richard, Thanks for replying.

But strange thing is that there is no problem with asset file as such. We uploaded the same asset in a different environment without facing any issue. I think this error also occurs in other situations than file name alone.

Also, to give you more information,we started facing this issue after we had problems with disk space. We have increased the disk space, then restarted the server. from then on we are facing this issue. We did Rebuild the index yesterday, and this error was not appearing. But now we see that are lot of corrupted assets, with missing artifacts. (Probably due to errors when disk space was not enough). But this is not expected, I suppose. It is more convenient if the assets are not created at all, when there are issues, instead of creating corrupted assets.

For us to continue further, what is the best way to get rid of these corrupted assets ? We are thinking about clean-up the complete DB, as we are at very early stage of our migration. 

Thanks in Advance,

Rich Kulp commented Oct 29 '12, 11:21 a.m.

First, the prefix too short problem occurs when trying to Update an existing asset with new content where a file is being deleted or replaced and the file name is less than three chars. An upload of a new file would not encounter this.

Your second problem is due to running out of space. If you are early in your migration then it would probably be easier to start from scratch with clean database and persist area. Otherwise deleting these assets could be a problem. Batch delete (search for them and then do batch update and select delete) may allow them to be deleted if corrupted. That works most of the time.

Your answer

Register or to post your answer.