+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. Jose Antonio
    Jose Antonio avatar
    13 posts
    Registered:
    19 Jul 2010
    04 Feb 2011
    Link to this post
    Hi, i was migrated the sitefinity project to the web server, and i show the error 
    'Invalid root node configured for pages. No root node with the name of "FrontendSiteMap".'

    i modified the configuration files and i solved it, but when linked the data base with the project and the aplication is breaking down. Any suggestion?

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    08 Feb 2011
    Link to this post
    Hello Jose,

    You could get this error if the project name has been changed - the name of the project is not the same as this one used when the project was installed

    You could check  App_Data\Sitefinity\Configuration\ProjectConfig.config file and projectName attribute. By default the attribute is not added to the config file. It is added after project installation The project name is used as an identifier by us.

    In some case the error could appear if the connection to the database is lost. Would you check the connection to the database in the DataConfig.config file?



    Regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Lorne
    Lorne avatar
    38 posts
    Registered:
    04 Nov 2010
    02 Mar 2011
    Link to this post
    I have a very similar problem. I've inherited some project files. I get this same error. How, specifically, can I resolve this issue?

    Thanks.
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    08 Mar 2011
    Link to this post
    Hello Lorne,

    The reasons for the issue are

    1. project name has been changed - project name is used as an identifier and it is not possible to change it on a  later stage.
    2. database connection

    Kind regards,
    Ivan Dimitrov
    the Telerik team
  5. Jason Rayner
    Jason Rayner avatar
    9 posts
    Registered:
    13 Apr 2005
    14 Mar 2011
    Link to this post
    Hi Ivan,

    I am encountering the same issue.

    1) The project name has not changed, well was certainly not changed by us. Is there anything in the deployment process that could cause it to change?
    2) I checked, rechecked and checked again and the database connection is correct.

    One odd thing to note is that is that if I change our local dev to the connection string from the production database we get the same error in our development environment.

    Is it possible that database transfer was somehow incomplete? Is there anything at all that we could be missing?

    Thanks,

    Jason
  6. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    15 Mar 2011
    Link to this post
    Hello Jason,

    Please compare the database size of the migrated and local database. Also check whether there are not changes to the App_Data/Sitefinity/Configuration.

    These files -  config files are closely related to the database.

    Greetings,
    Ivan Dimitrov
    the Telerik team
  7. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    15 Mar 2011
    Link to this post
    Hi Team,

    I am encountering the same issue. Everything is working properly on my local machine but not on the production server. I have copied the configuration files from my local machine and updated the connection string. The site was working properly on the production server before i upgraded to SP1

    View site here

    Any insight ?
  8. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    15 Mar 2011
    Link to this post
    Hi George ,

    Please check whether there are not changes to the name of the database tables. Also the websites produces different errors related to the problem with the dlls - "Could not load file or assembly"

    Regards,
    Ivan Dimitrov
    the Telerik team
  9. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    15 Mar 2011
    Link to this post
    Hi Ivan,

    I was updating the dll references while you checked the website. if you check it again now you can see the error. I have upgraded the project on my local machine then i took the database and restored it on the production server. So basically i have the same files / db and it's working locally.
  10. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    15 Mar 2011
    Link to this post
    Seriously this is ridiculous ! What on earth is the cause for such an ambiguous error...

    Can you please help ... I need to fix this urgently !
  11. Jason Rayner
    Jason Rayner avatar
    9 posts
    Registered:
    13 Apr 2005
    15 Mar 2011
    Link to this post
    Hi Ivan,

    This was literally xcopy / deploy from our development to production and everything in the App_Data/Sitefinity/Configuration folder except for the connection string in DataConfig.config is exactly the same between the two environments.

    The database on the dev server has already changed as development proceeds still so these are different sizes. We had encountered errors trying to publish the database and had to use scripts for all tables EXCEPT sf_chunks which we had to use DTS Wizard to transfer into the production database. The database on production looks functionally complete. Is there a database table / field or some place where I check on some magical value that can correct this issue we are having.

    Client press release announcing the website is now merely 2 hour away and I can't get this thing to work.

    Thanks,

    Jason
  12. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    15 Mar 2011
    Link to this post
    Ivan,

    Can you help us out !
  13. Dan
    Dan avatar
    24 posts
    Registered:
    02 Oct 2012
    15 Mar 2011
    Link to this post
    We're also running into this issue - our local sites work, but when the code is copied to the dev server we get this error.  All files are identical (including \app_data\sitefinity\configuration), so the database connection is the same as well of course.

    Thanks, Dan
  14. Dan
    Dan avatar
    24 posts
    Registered:
    02 Oct 2012
    15 Mar 2011
    Link to this post
    I just copied the entire app_data folder out to the dev server again, and it resolved the issue.  Seems to be something in the app_data folder other than the configuration files.

    Thanks, DanO
  15. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    16 Mar 2011
    Link to this post
    I have copied the App_Data to the production server and still it's not working ... the only difference i have between the production server and my local machine is the database name

    Log :

    ----------------------------------------
    Timestamp: 3/16/2011 7:54:18 AM
     
    Message: HandlingInstanceID: fbb43bb5-5930-47ad-bd3b-ccf3370e654d
    An exception of type 'System.Configuration.ConfigurationErrorsException' occurred and was caught.
    -------------------------------------------------------------------------------------------------
    03/16/2011 02:54:18
    Type : System.Configuration.ConfigurationErrorsException, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Message : Invalid root node configured for pages. No root node with the name of "FrontendSiteMap".
    Source :
    Help link :
    BareMessage : Invalid root node configured for pages. No root node with the name of "FrontendSiteMap".
    Filename :
    Line : 0
    Errors : System.Configuration.ConfigurationException[]
    Data : System.Collections.ListDictionaryInternal
    TargetSite :
    Stack Trace : The stack trace is unavailable.
    Additional Info:
     
    MachineName : SKNET139
    TimeStamp : 3/16/2011 7:54:18 AM
    FullName : Telerik.Sitefinity.Utilities, Version=4.0.1210.0, Culture=neutral, PublicKeyToken=b28c218413bdf563
    AppDomainName : /LM/W3SVC/21/ROOT-1-129447356457267430
    ThreadIdentity : Anonymous
    WindowsIdentity : NT AUTHORITY\NETWORK SERVICE
    Requested URL : /
     
     
    Category: ErrorLog
     
    Priority: 0
     
    EventId: 90020
     
    Severity: Error
     
    Title:Enterprise Library Exception Handling
     
    Machine: SKNET139
     
    App Domain: /LM/W3SVC/21/ROOT-1-129447356457267430
     
    ProcessId: 11056
     
    Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
     
    Thread Name:
     
    Win32 ThreadId:11100
     
    Extended Properties:
    ----------------------------------------
  16. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    16 Mar 2011
    Link to this post
    Hi Team,

    Can you please help ... You can view the site here

    Helloooooooooo
  17. Dan
    Dan avatar
    24 posts
    Registered:
    02 Oct 2012
    16 Mar 2011
    Link to this post
    George,

    I believe the cause of the issue for us was that one of the developers had added a master page / template to his local site, but the "copy to output directory" was marked as "do not copy" on the file, so when we did a deployment (using a build definition in VS 2010), the files were not copied to the server.  Since our local and dev sites currently share a database the dev site blew up because it had a reference to a master page that didn't exist in the file system.  

    You might try using the data compare tools in VS 2010 to compare the two databases and see what CMS data is different between the sites - maybe that will provide some insight. Good luck!

    -DanO
  18. George
    George  avatar
    204 posts
    Registered:
    05 Sep 2006
    16 Mar 2011
    Link to this post
    Thanks Dan for your suggestions.

    I have the exact same database on my local machine and the production server. I have restored the database there. I haven't added any master page nor any one from the team. I am still waiting for some feedback from the Sitefinity team. I hope they will respond soon.

  19. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    18 Mar 2011
    Link to this post
    Hello George ,

    If the connection string is different, make sure that in both environments the database user is db_owner or it is the same user. For example, if the user is db_owner it creates tables with dbo.tableName, if it is not - userName.tableName, which are two different tables. Maybe the data has not been published correctly. 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]/'.

    Kind regards,
    Ivan Dimitrov
    the Telerik team
  20. Gabe Sumner
    Gabe Sumner avatar
    440 posts
    Registered:
    09 Sep 2007
    18 May 2011
    Link to this post
    Hey everyone,

    I recently received this error and wanted to report my results.  However, I'm not convinced my scenario will be very applicable to others.

    I was using the Sitefinity 4.1 SDK to run the Charity sample.  After clicking run sample, I received the error mentioned in this thread.  I also tried resetting the sample and still received the error.

    --

    Here is how I fixed this:

    The SDK manages its samples in the C:\SitefinitySamples folder.  From what I can see, the database is instantiated from files in the C:\SitefinitySamples\Database folder.  For whatever reason (the SDK was running as Administrator) the SDK (or perhaps SQL Express?) was being denied access to these database files.  Consequently the Charity web site was being initialized using some incomplete database...which caused the error shown above.  

    I'm not sure it matters, but I was using a SQL username/password (not windows authentication) to initialize the Charity sample.

    To fix this I gave Everyone full control of the C:\SitefinitySamples.  After that, I reset the sample and it worked fine.  Granting Everyone full control of files isn't a great solution, but this is my personal workstation and I'm not overly concerned with security for a sample project.

    --

    Like I said, this is a narrow use-case and might not help others.  However, the problem did seem to stem from an incomplete database or access denied.

    Gabe Sumner
    Telerik | Sitefinity CMS
  21. Mark
    Mark avatar
    147 posts
    Registered:
    01 Jun 2010
    18 May 2011
    Link to this post
    I'm running into this problem this morning and nothing from the above thread seems to be helping.

    My site was 4.0. I upgraded to 4.1, then 4.1 SP1 immediately afterwards and brought my site back online.

    I had previously renamed my project and the project name did not carry over from my previous ProjectConfig.config file, so I added my new project name. I have checked the sf_page_node table and the app_name column has the same project name that my ProjectConfig.config has.

    When I try to view the homepage I receive the same error as the title of the thread. When I try to login through /sitefinity none of my usernames/passwords are working. I have checked the connectionstring and everything looks fine.

    Any other ideas on how I can get this site back up?
  22. Dan
    Dan avatar
    7 posts
    Registered:
    07 Oct 2010
    18 May 2011
    Link to this post
    I am having the exact same issues as those described by Mark. I did not have the project name problem.

    I receive the "Invalid root node configured..." error on the home page and none of my username/passwords are working.

    I also have checked permissions, connection string, data in the various tables and so on.
  23. Mark
    Mark avatar
    147 posts
    Registered:
    01 Jun 2010
    18 May 2011
    Link to this post
    Looking through my database, I think I've found out why my site is experiencing this behavior. Many of my times are duplicated: db_owner.table_name and dbo.table_name. 

    This happened during the upgrade because my 4.0 backup does not have the duplication. dbo.sf_users still has my username while db_owner.sf_users does not. It does not appear the updater touched the dbo.* copies but rather made new db_owner.* tables.

    What's the solution here?
  24. Mark
    Mark avatar
    147 posts
    Registered:
    01 Jun 2010
    18 May 2011
    Link to this post
    The root to my problem was that my tables were owned by dbo and not db_owner. I found a script that could change ownership and now 4.1 SP1 is working as expected. Here's the SQL script I needed to use:

    DECLARE @old sysname, @new sysname, @sql varchar(1000)
     
    SELECT
      @old = 'dbo'
      , @new = 'db_owner'
      , @sql = '
      IF EXISTS (SELECT NULL FROM INFORMATION_SCHEMA.TABLES
      WHERE
          QUOTENAME(TABLE_SCHEMA)+''.''+QUOTENAME(TABLE_NAME) = ''?''
          AND TABLE_SCHEMA = ''' + @old + '''
      )
      EXECUTE sp_changeobjectowner ''?'', ''' + @new + ''''
     
    EXECUTE sp_MSforeachtable @sql
  25. Dan
    Dan avatar
    7 posts
    Registered:
    07 Oct 2010
    18 May 2011
    Link to this post
    Again, I see the same thing as Mark. I agree that the new tables are probably the ones being hit which would certainly help explain things.

    For Telerik's info here are some details:

    The Identity of my Application Pool in IIS is a domain account and Sitefinity is connecting to a SQL Server database using Integrated Security (NOT a SQL Express database in App_Data). What I see is that after the upgrade there is a whole new set of tables in a schema named for the domain account and owned by the domain account. All of my real data is in the tables owned by dbo.

    This did not occur on my copy of Sitefinity running locally with a SQL Express database.

    I'm sure the script Mark provided would fix the problem, but I don't really want to go down that road. I'm going to restore from backups and wait till this problem is resolved by Telerik.
  26. Markus
    Markus avatar
    2763 posts
    Registered:
    25 Nov 2005
    19 May 2011
    Link to this post
    I ran into the exact same problem.

    I renamed my App_Data\Sitefinity\Configuration\ProjectConfig.config

    to ProjectConfig_old.config

    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.

    So Telerik - do me and others a favoir and think about what, when, were the ProjectConfig.config File could have been changed online in a production envirement!!

    Markus
  27. Gabe Sumner
    Gabe Sumner avatar
    440 posts
    Registered:
    09 Sep 2007
    01 Jun 2011
    Link to this post
    Hey everyone,

    I'm about to release a 30 minute video and accompanying blog post on deploying Sitefinity.  During research & recording I encountered this troublesome error.  This thread led me to the solution.  Like others in this thread, my development database was using tables that looked this like:

    dbo.[tableName]

    However, on the production server/database Sitefinity was expecting database tables that look like this:

    charity.[tableName]

    'Charity' is the database username I'm using through the shared hosting provider.  

    Because these tables didn't exist, Sitefinity created them...but they are empty.  When Sitefinity tried to find a web page it throws the error shown in the subject of this thread.

    --

    My solution was to remove charity tables that Sitefinity created by executing this SQL:

    EXEC sp_MSforeachtable @command1 = "DROP TABLE ?"

    BEWARE!!!!  This command will obliterate everything in your database.

    Then I re-transferred the database (with the dbo table names) to the production server and renamed all of these tables using the following SQL:

    DECLARE tabcurs CURSOR
    FOR
        SELECT 'dbo.' + [name]
          FROM sysobjects
         WHERE xtype = 'u'
     
    OPEN tabcurs
    DECLARE @tname NVARCHAR(517)
    FETCH NEXT FROM tabcurs INTO @tname
     
    WHILE @@fetch_status = 0
    BEGIN
     
        EXEC sp_changeobjectowner @tname, 'charity'
     
        FETCH NEXT FROM tabcurs INTO @tname
    END
    CLOSE tabcurs
    DEALLOCATE tabcurs

    You'll need to modify the dbo and charity values for your unique deployment.

    --

    Anyway the video is already uploaded and I'm waiting for encoding to finish.  When it's published, it will work at this URL:

    http://tv.telerik.com/watch/sitefinity/how-to-deploy-sitefinity-4-to-shared-hosting

    Thanks to everyone in this thread for helping to make this possible.

    Gabe Sumner
    Telerik | Sitefinity CMS
  28. Lukas
    Lukas avatar
    1 posts
    Registered:
    30 Nov 2010
    14 Sep 2011
    Link to this post
    Hey all

    If you are using the SQL Server Import and Export Wizard you can easily bypass this issue by specifying the correct mappings.
    During the wizzard in the "table and views" step, you can click the "Edit Mappings" button and enter a new "destination schema name".

    E.g. if your username in the connectionString is myUser set the dest. schema name to myUser.

    Complete the wizzard and everything should work as expected, at least it did for me :P

    Regards,
    Lukas
  29. Douglas
    Douglas avatar
    1 posts
    Registered:
    20 Jul 2011
    30 Sep 2011
    Link to this post
    This is absurd. This problem needs to be fixed ASAP and/or better messages need to come from Sitefinity as to what the issue is.
  30. Brian
    Brian avatar
    6 posts
    Registered:
    20 Jun 2011
    03 Oct 2011
    Link to this post
    Hi

    This solution worked for me for the above error and is very quick (no scripts/import or export) - just a setting in your external SQL Provider (using Microsoft SQL Manager).  I am using a external hosting provider arvixe but this would probably work on other providers.  When restoring database from local SQLExpress to external hosting provider SQL all I did was to make sure security (off root SQL Tree / not the security tab in your database) had my SQLUserId with the default schema of "dbo".  By default (after restore) you may find that the schema on your SQL provider has defaulted to your SQLUserId rather than dbo as it is in your local database.   After you have finished...then recycle application pool and/or web site.  All fixed!
    Hope this is helpful for any one else.
    Brian  
43 posts, 0 answered
1 2