Error with cmsContentXml when moving a content item in the tree
In tab Content in Umbraco 8 (latest version), I'm trying to move a Content node to another node somewhere else in the tree I get this:
An error occured
Invalid object name 'cmsContentXml'.
Exception Details
System.Data.SqlClient.SqlException: Invalid object name 'cmsContentXml'.
I've Rebuild the model, Refreshed all caches in Published Cache Status (except the internals).
Is there a way to also or rebuild refresh this cmsContentXml ?
Any ideas what might be causing this issue and what could be solutions to this.
The Move itself seems to work because after a refresh it is moved to the proper position. But of course I don't want to have the end customer having to see error messages while doing basic operations.
Note: I double checked that all my nodes are in status Published. I also removed everything in my Recycle Bin already.
If I delete the contents of folder \App_Data\cache
My problems disappears, still wondering what the deal is with this cmsContentXm it was trying to access, but for now (finger crossed) deleting the files in the cache directory seems to get rid of the error I had.
Error with cmsContentXml when moving a content item in the tree
In tab Content in Umbraco 8 (latest version), I'm trying to move a Content node to another node somewhere else in the tree I get this:
An error occured Invalid object name 'cmsContentXml'.
Exception Details System.Data.SqlClient.SqlException: Invalid object name 'cmsContentXml'.
I've Rebuild the model, Refreshed all caches in Published Cache Status (except the internals).
Is there a way to also or rebuild refresh this cmsContentXml ?
Any ideas what might be causing this issue and what could be solutions to this.
The Move itself seems to work because after a refresh it is moved to the proper position. But of course I don't want to have the end customer having to see error messages while doing basic operations.
Note: I double checked that all my nodes are in status Published. I also removed everything in my Recycle Bin already.
Think I just found something which helps.
If I delete the contents of folder \App_Data\cache
My problems disappears, still wondering what the deal is with this cmsContentXm it was trying to access, but for now (finger crossed) deleting the files in the cache directory seems to get rid of the error I had.
is working on a reply...