The valueDictionary is not formatted correctly and is missing any of the 'id,nodeId,__NodeId' elements
We're getting this error a lot in development and intermittently on a production site. The site is Umbraco 7.0.4 and forcing a restart by updating the web.config seems to fix it most of the time.
"The valueDictionary is not formatted correctly and is missing any of the 'id,nodeId,__NodeId' elements"
Has anyone else experienced this? I believe it's something in one of the examine/lucene indexes but can't see what would cause it.
I'd spotted the v6 issue previously and the fix for that looks like go onto the production servers and delete the indexes or restart the site, which is what we're doing but isn't really an option going forward as it doesn't always happen in office hours!
I'll report a new issue today, I'll see if I can gather some info first
The valueDictionary is not formatted correctly and is missing any of the 'id,nodeId,__NodeId' elements
We're getting this error a lot in development and intermittently on a production site. The site is Umbraco 7.0.4 and forcing a restart by updating the web.config seems to fix it most of the time.
"The valueDictionary is not formatted correctly and is missing any of the 'id,nodeId,__NodeId' elements"
Has anyone else experienced this? I believe it's something in one of the examine/lucene indexes but can't see what would cause it.
Thanks in advance for any help,
Steve
Hi Steve
I've not seen this issue myself...however I did a little digging and it seems to be an issue that has happened in earlier versions as well.
There is a forum post about it here http://our.umbraco.org/forum/developers/api-questions/44851-Issue-With-Media-Cache-in-v6 and there are some issues with many comments here http://issues.umbraco.org/issue/U4-1181 and here http://issues.umbraco.org/issue/U4-1132
Perhaps you can find a way to solve it based on the information these places?
And perhaps this needs to be reported once again for v7? If so please do so and it's got my vote for sure.
Looking forward to hearing from you.
/Jan
Thanks Jan,
I'd spotted the v6 issue previously and the fix for that looks like go onto the production servers and delete the indexes or restart the site, which is what we're doing but isn't really an option going forward as it doesn't always happen in office hours!
I'll report a new issue today, I'll see if I can gather some info first
Cheers
Steve
Hi Steve,
We are using umbraco v6 .2 and facing same issue .
Did you get any solution for this?
Note: Only we are doing server restart to resolve.
is working on a reply...