Search code examples
tridiontridion-2011

Could not parse componentmeta

We're trying to upgrade an old Tridion 2009 site to Tridion 2011 and some problems occur when we're publishing Pages.

Here is a snippet from the cd_storage_conf.xml:

<Publication Id="78" defaultStorageId="defaultdb" cached="true"> 
    <Item typeMapping="Binary" cached="true" storageId="defaultJSPFile"/>
    <Item typeMapping="Page" cached="true" storageId="defaultJSPFile"/>
    <Item typeMapping="Metadata" cached="true" storageId="defaultdb"/>
</Publication>

defaultJSPFile references a Filesystem storage and defaultdb references a MSSQL database storage. And here is the error message from the publishing queue. 

66560, Unable to store item inside current transaction, 
Could not parse tcd:pub[78]/componentmeta[119939], 
Could not parse tcd:pub[78]/componentmeta[119939], 
Could not parse tcd:pub[78]/componentmeta[119939], 
Could not parse tcd:pub[78]/componentmeta[119939], 
Could not parse tcd:pub[78]/componentmeta[119939], 
Could not parse tcd:pub[78]/componentmeta[119939], 
Unable to store item inside current transaction, 
Could not parse tcd:pub[78]/componentmeta[119939] , 
Could not parse

Changing the storageId of the Metadata typeMapping to defaultJSPFile makes the error go away, but we can't make it work to get the metadata into the database.

Solution

  • Problem solved. It seemed the Tridion.ContentDelivery.Interop.Dll wasn't upgraded in the deployer. I'm still not sure what has changed that the deployer would go through the linkinfo folder in the deployment zips.

    To summarize, make sure you upgrade EVERYTHING when installing a service pack or a hotfix rollup.