Try our conversational search powered by Generative AI!
AI OnAI Off
Unable to load /EPiServer/shell/Stores/metadata/EPiServer.Core.ContentData?modelAccessor=%7B%22contentLink%22%3A%227_1710062%22%7D&dojo.preventCache=1
Have you used F12 and have error details turned on? You might see the actual exception message in the response tab of the failing request. If that's not an option, check the logs to find the actual exception.
If you can't find anything I would try upgrading CMS to 11 -prerelease. I'm thinking that's how Epi have done most of their testing.
Nov 21, 2017 8:23
How do I turn on detailed exceptions?
I think it is just a regular 500 error message no useful information. Prerelease sound good, but after Black Friday... :)
Edited,
Nov 21, 2017 8:26
DXC, and we have application insights activated but we can't find anything there.
Nov 21, 2017 9:02
I think you should see those types of errors in New Relic. I see some similar errors below Events => Errors.
For example an error in /EPiServer/cms/Stores/contentdata/37060_609256 where I can see the stack trace if I click on it.
Nov 21, 2017 9:17
Looks like it had todo with a misconfigured EpiserverFramework.config. We were missing this:
<event defaultProvider="azureevents">
<providers>
<add name="azureevents" type="EPiServer.Azure.Events.AzureEventProvider,EPiServer.Azure" connectionStringName="EPiServerAzureEvents" topic="MySiteEvents"/>
</providers>
</event>
For some reason this was removed during deploy so events was not sent on publish and user being on another instance could not see the changes. Why this caused a dojo exception I don't know.
/Kristoffer
Nov 21, 2017 13:45
Hi!
We get this error very often at our CMS site. It is actually a Commerce, 11.4, but it is the CMS part that has the problem.
The editors gets this message:
Unable to load /EPiServer/shell/Stores/metadata/EPiServer.Core.ContentData?modelAccessor=%7B%22contentLink%22%3A%227_1710062%22%7D&dojo.preventCache=1511168764852 status: 500"
when accessing a page. They cannot edit the current page and often the see old versions of the page. we did not have this error until we upgraded to Commerce 11.3 so I'm not sure if it might be Commerce related.
Thanks!
/Kristoffer