More in this section

Forums / Bugs & Issues / Dashboard & Pages crashes application pool

Dashboard & Pages crashes application pool

2 posts, 0 answered
  1. Ryan
    Ryan avatar
    1 posts
    25 Apr 2008
    25 Apr 2008
    Link to this post
    A client was editing pages and moving things and caused some sort of error that I cannot figure out.

    Now when I login it crashes the application pool and I have to stop and start it again. if I go to my history and use a link further back in the site (bypassing the dashboard) i can navigate everything except the Dashboard and Pages main page. I can select a page link from my history and view an individual page but not the list of all pages.

    I don't know what to do - any help, insights, or suggestions would be greatly appreciated.
  2. Georgi
    Georgi avatar
    3583 posts
    28 Oct 2016
    29 Apr 2008
    Link to this post
    Hi Ryan,

    Since you mentioned reordering, we have a clue that might help us solve the problem.
    Which is the exact version you were using when you saw the error for the first time? We had a problem with reordering pages and we have already fixed it for the upcoming SP. The issue was a bit complicated. If you have several page groups :


    .. , if you drag parentPage to become a child of SubPageLevel2, then SubPageLevel2 becomes a parent of parentPage, and parentPage is already a parent of SubPageLevel1, and at the same time a child of SubPageLevel1. Can you see the cycle? It sounds a little strange, but this is stored in the database, and when trying to rebuild the Sitemap tree, the procedure enters into an endless loop. That could cause the ASP.NET process to crash.

    We managed to create a SQL script that should fix the problem you have. Just run it against your database, and all "problematic" pages will be set as root pages - they will not be child pages any more. You could re-arrange them in the pages tree as you like. Here's the script :

    ParentID = NULL 
    ID = ParentID 

    Let us know if your problems persist after taking these steps.
    Once again, we are sorry for the inconvenience caused.

    Kind regards,
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
2 posts, 0 answered