+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / error: Invalid root node configured for pages. No root node with the name of "FrontendSiteMap".

error: Invalid root node configured for pages. No root node with the name of "FrontendSiteMap".

43 posts, 0 answered
  1. Jan
    Jan avatar
    2 posts
    Registered:
    02 Jul 2008
    03 Nov 2011
    Link to this post
    Brian, you are brilliant. How the heck did you figure that out? I also host with arvixe the only challenge using SQL Management studio takes forever to load the user properties. It is easier to do this by script:

    USE

     

    [database_name]

     

    ALTER

     

    USER [User_name] WITH DEFAULT_SCHEMA = dbo

     



  2. Brian
    Brian avatar
    6 posts
    Registered:
    20 Jun 2011
    03 Nov 2011
    Link to this post
    Thanks Jan for feedback. I hadn't heard anything on this until your post so hope it continues to help anyone frustrated by errors or earlier proposed forum work arounds.  BTW - Lots of trial and error to get to this solution and....Yes hosting provider is slow on SQL Management Studio for me too.  Your script certainly the way to go. Thanks

    Brian
  3. DMRC
    DMRC avatar
    5 posts
    Registered:
    30 Aug 2011
    08 Nov 2011
    Link to this post
    I concur. Brian, you are a genius. This really helped. Thanks so much!

    Just an FYI for anybody else: Along with replicating our DB and using Brian's method to check the dbo, we also have to replicate the Configuration folder under App_Data, except for DataConfig.config - and then and only then will the QA server work.

    My suggestion for improvement would be to have all those settings stored in the Configuration folder to somehow be contained in the DB. I'm sure there are reasons why this is the case, though, but we have to develop more automation steps than anticipated to get a replication procedure in place.
  4. Brian
    Brian avatar
    6 posts
    Registered:
    16 Nov 2011
    18 Nov 2011
    Link to this post
    I've encountered roughly the same issue.  I've only been working on my development machine with a development database while I evaluate SiteFinity.  Yesterday, everything was working fine.  The very last thing I did was to set up an LDAP connection.  All I did is:

    - Create a new LDAP connection under Settings -> Advanced -> Security -> LDAP Settings -> LDAP Connections
    - Change the Authentication settings within IIS.

    Then I moved on to some production issues.  I came back to the SiteFinity site today and had the error described in this thread.  After reading all the posts, I found that the "projectName" property in the ProjectConfig.config was empty.  I definitely did not touch this - I've never even looked at this file.

    The first thing I did was set the Authentication settings in IIS back to what they were.  That didn't fix it. Then, I found what it should be in one of the other posts in this thread and copied it from the database field sf_page_node..app_name.

    That fixed my issue.

    -BEP  ( Brian, but not the Brian that posted the fix above )

    "Downloaded my App_Data\Sitefinity\Configuration\
    ProjectConfig.config from the server and compared it. And yes the Project name was GONE. Simply empty.

    I put my project name back in and uploaded the file, restarted the server and the site was back on!

    So this fixed it!

    BUT - I tell you it was no move to production, no changes - unbelivable as it might sound - this just happened."
  5. NK
    NK avatar
    82 posts
    Registered:
    15 Apr 2010
    04 Apr 2012
    Link to this post
    Hi,
    I just upgraded to 5.0 from 4.4 and I had this error "'Invalid root node ..... "FrontendSiteMap".' The projectName was not empty in App_Data\Sitefinity\Configuration\ProjectConfig.config file.

    How do I fix?

    Thanks,
  6. NK
    NK avatar
    82 posts
    Registered:
    15 Apr 2010
    04 Apr 2012
    Link to this post
    Hi,
    I just upgraded to 5.0 from 4.4 and I had this error "'Invalid root node ..... "FrontendSiteMap".' The projectName was not empty in App_Data\Sitefinity\Configuration\ProjectConfig.config file.

    How do I fix?

    Thanks,
  7. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    04 Apr 2012
    Link to this post
    Hi Nelson,

    Check whether the SQL server was configured correctly to serve the schema of your database. If you have custom db schema name you should set all appropriate configurations, otherwise the system will re-create all tables ( which will be empty ) under the default dbo owner.

    Greetings,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  8. NK
    NK avatar
    82 posts
    Registered:
    15 Apr 2010
    06 Apr 2012
    Link to this post
    Reset the user account to dbo right and it worked.

    Thanks Victor.
  9. Jonathan
    Jonathan avatar
    26 posts
    Registered:
    23 Jul 2012
    18 Oct 2012
    Link to this post
    Ivan already mentions this in one of his earlier responses, but it still tripped me up and thought I would post here for posterity. Ivan says:

    Could you please open sf_page_node table and make sure that it is not empty and the value of the app_name column for all records is '[ProjectName_From_ProjectConfig]/'.

    Note the *slash* after the project name (I didn't see it and blame the parenthesis, apostrophe, etc for blinding me) . That is, if project name is "MyProject", the value in app_name must be "MyProject/" (note the slash)
  10. Patrick Dunn
    Patrick Dunn avatar
    237 posts
    Registered:
    03 Nov 2014
    19 Oct 2012
    Link to this post
    Hi,

     Did you manage to get your site online? For anyone deploying Sitefinity to Arvixe or any other shared hosting and getting the Frontend node error you can check out Gabe's blog where he details a SQL script to run to change the schema or this blog post (easier) to generate .sql scripts and edit them to change your schema.

    All the best,
    Patrick Dunn
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  11. Sam
    Sam avatar
    1 posts
    Registered:
    06 Feb 2014
    09 Jul 2014 in reply to Brian
    Link to this post
    Brian's solution worked for us. In Arvixe, the user's Default Schema was the user ID. Changing the Default Schema to 'dbo' resolved our issue of duplicate tables prepended with the user ID.
  12. Bil
    Bil avatar
    51 posts
    Registered:
    27 Aug 2012
    19 May 2015
    Link to this post
    Just a note that in version 8 this error exists if the database is completely gone. I invoked it (deliberately) with an Azure deployment. Setup the cloud app without a backend database. I was expecting some kind of SQL error but got this instead (and the call stack showed nothing from the *.Data assemblies). Would be nice if the right error message bubbled up. I still don't know the significance of the project name and why/how/where it's referenced however once I brought the database back online the site was fine.
  13. Sabrie Nedzhip
    Sabrie Nedzhip avatar
    534 posts
    Registered:
    08 Dec 2016
    22 May 2015
    Link to this post
    Hi Bil,

    Thank you for your feedback. I have forwarded this information to the developers team and they will take it into consideration for the future releases.

    Regards,
    Sabrie Nedzhip
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
43 posts, 0 answered
1 2