We have migrated content from an EPiServer 6 site, where they have approximately 540 pages under one pagenode (No subnodes), to an EpiServer 7 site. The problem we now experience is that the parent node containing all pages will not expand. Does any one know how to handle this?
Do you get any errors in the browser console when trying to expand?
I'm in the same project and it looks like the request times out before it's finished.
We have an aspx we use for ajax calls and that page inherits our template base class to get hold of settings pages etc. That page doesn't have a guid, or model but the template resolver seems to get stuck on it
We get a load of these lines before it times out:
EPiServer.DataAccess.ContentLoadDB: 2.13.2 Loading content from database for content with id: 832_8642EPiServer.Web.TemplateResolver: DocumentPage: Selected Namespace.Views.Json. (tag='', channel='', category='Page')EPiServer.Web.PermanentLinkMapper: Storing Guid=e9cd1285-b2e3-4aa7-966e-2c1f82cf0886, MappedUrl=/Views/Json.aspx?id=XXX, PermanentLinkUrl=~/link/e9cd1285b2e34aa7966e2c1f82cf0886.aspx in PermanentLinkMapStore cacheEPiServer.Web.TemplateResolver: DocumentPage: Selected Namespace.Views.Json. (tag='Preview', channel='', category='Page')
ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NETSystem.Web.HttpException (0x80004005): Timeout för begäran.
Not sure if this is the case, but it does someting with that page.
No errors apart from the 500 due to the timeout
Have you updated the statistics on the database.
We had the same issue with an EPi7 website after a content migration (4000 pages)
Try the following:
For us, this reduced the queries on the database for the page tree population from > 30 seconds to < 1 second.
Yes we updated the statistics but without success.Then we used SQL Server Performance Tools, Database Engine Tuning Advisor and applied the Recommendations to create 32 statistics/ index tables.The time was reduced from 3 min to 13 seconds. Hopefully much better in release.Question: Could it be a good thing to do a job that run UPDATE STATISTICS to always have this updated?