Home » blog » jskemp's blog

WCM: contentItemKey error

Posted September 30th, 2009 by jskemp

Since we've still got to investigate this a bit more, it sits here before posting as a bug ...

Our content guy ran into an error while attempting to create a new piece of content.

Interestingly, he created the content record, saved it, then went back in and added HTML content to the document.

When attempting to save the record he got a message like 

Error: Parameter name: contentItemKey Actual value was f818fe69-0dd8-4cb0-a037-650370c36793.

No matter what he does, when it goes back to the content 'window' he gets a message about an unexpected iMIS error. Changing the Content Layout from (None) to something else (like SingleColumn) allows him to add the html content successfully.

I've only found two tables that seem to help with how content is stored, and none of them have this contentItemKey value (and a search on iMIS Community doesn't turn up any results).

Adding content to the record before initially saving it works fine.

15.1.1.2998

jskemp's blog | login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Two semi-relevant tables

On September 30th, 2009 jskemp says:

DocumentMain and Tag are the two tables that I've thus far found to be important.

Unfortunately, I've been unable to determine where, for example, the actual HTML content is stored in SQL (I assume it's still stored in the db somewhere).

login or register to post comments

The HTML is stored in the

On September 30th, 2009 Eric Means says:

The HTML is stored in the DocumentMain Blob column (as XML-serialized objects).

I've not seen that error (and you might check on the latest patch version to see if that resolves it before spending too much time on it), but the error usually indicates that something went awry with the in-session variables used to keep changes active between postbacks.

If he saves the content record (without adding content), then closes and reopens the content record, does it work?

login or register to post comments

Thanks Eric. I guess there

On September 30th, 2009 jskemp says:

Thanks Eric. I guess there goes the chance of our SQL guru doing easy find and replaces on HTML content to fix our mistakes/changes ... :D

Initially he said that it would work, he just had to make sure that Content Layout was changed correctly, but when he tried it with me over his shoulder it bombed out with the same error.

And going into the record, saving, then going into it again resulted in the same issue. It looks like by default (None) changes to SingleColumn, so maybe next I'll see if he can change it to a different layout and see what occurs.

I'll see about whether we can upgrade, or, since we're at least a handful of months away from ramping up for 'real' testing, if we just need to keep it as a note for later.

Thanks again for your comments.

~James

login or register to post comments

Have you customized the

On September 30th, 2009 Eric Means says:

Have you customized the SingleColumn layout, or is it the same version we shipped? It's interesting that it fails on that but works if you change the layout. (I remember *something* along those lines, but GA was long enough ago I can't recall if it was something we encountered pre-release and fixed, or post-release and patched).

login or register to post comments

Nope, it's completely a

On September 30th, 2009 jskemp says:

Nope, it's completely a fresh install, with 0 customizations.

login or register to post comments