Invalid root node configured for pages. No root node with th

Hi,

So I know this error isn't a new one as I've done a whole lot of reading on the issue. Here's my history so far

 - Created the SF5 site on a local dev server with a project name of "dev.mysite.com"
 - Uploaded the site to our client's server and got the site up and running 
 - Made sure the database user uses the dbo schema on the client's database

Everything was working and fine at this point, until I did something silly, which was 

 - Edited /App_Dev/Sitefinity/Configuration/ProjectConfig.config by changing the project name to "www.mysite.com"

I then received the "Invalid root node" problem - at that point I switched the project name to "dev.mysite.com" and the site began to work again. 

What I decided to do at this point was go into sf_page_node and update the app_name field to my new "www.mysite.com" project name. I was hoping to be able to rename the project so that it would match the client's final domain name. This caused the "Invalid root node" problem again so I thought I would just change everything back to "dev.mysite.com" and it would work.

But the site still gives that error (on the public site as well as the admin side). I'm hoping someone can help me resolve this problem without me having to rebuild the database from scratch?

Cheers,
Nick

Hello Team,

I am facing the same problem too. 

I developed the website in my local machine and uploaded it on live server. Only the database user is different then my development server but the db user has db_owner rights.  I have changed the configuration details in Dataconfig.config file for the database details, Nothing has been changed by me except the database user but I am facing the error which says.. 

"Invalid root node configured for pages. No root node with the name of "f669d9a7-009d-4d83-ddaa-000000000002"."

Please find the attached screen shot. 

Could you please help me to resolve the problem asap?

The thing which I noticed on the server's db is that when I expand the tables it displays single table with multiple name.  One is for the dbo.sf_page_node  and one for my dbuser.sf_page_node. I removed all the tables which starts from [dbuser.] but still the error is there.

Hello,

 Please, try the solutions in this KB:http://www.sitefinity.com/developer-network/knowledge-base/when-sitefinity-project-is-deployed-to-production-server-an-invalid-root-node-configured-for-pages-no-root-node-with-the-name-of-frontendsitemap-error-is-thrown

Make sure that the user has the dbo as default schema as well. Another thing that you can try is restoring the backup of the database again.

[quote]Make sure that the user has the dbo as default schema as well.[/quote]

This line sorted us out this morning--thanks! Would you add this to the KB article? The screenshot displays the default schema as being blank. 

I am getting the same error as above, and I have double checked all the things that have been mentioned in various posts around this issue here dating back to 2011. 

I am wondering whether my issue has something to do with the following: 

I am trying to deploy a newly acquired standard edition to our host using a temporary URL which I have received from our host. In other words, the URL for which this Standard Edition has been registered for is not the same I am using for testing it on the host. Our main URL is still pointing to our main website and I cannot migrate it until the new site is finished.

 I am wondering whether the fact that I am experiencing the same problem as described here has something to do with me trying to use the temporary URL. If so, then this error is not very verbose.

Any comments highly appreciated.

 Andrew

Hello Andrew,

If the site work ok in a different environment, there is most likely a connectivity issue to the database. If you are using a different domain name from the one in your license, the site will work fine but you will get a trial message.

Also, how are you deploying the site? The best way is to simply copy over the project folder and fix the connection string.

Regards,
Atanas Valchev
Telerik

Thanks for your comments Atanas,

I was able to solve the issue in the meantime. For those who run into the same problem like me, here is another thing they can be looking out for:

What I did before:

1. I used the Azure SQL Migration Wizard to copy the DB from development to production. It works quite well and copies all objects and the data without much ado.

2. I published the SF project using the VS publishing mechanism. The connection string would be replaced automatically.

What happened: 

For some reason, the SQL Migration Wizard did not only copy the dbo objects, but also created the same objects AGAIN in the schema of the owner of the target db. So if I had a user "test" with a schema "test" in the target db and an object "dbo.table" from the source db, then it would create both a table "dbo.table" and "test.table" in the target db. So I ended up with a duplicate of each object in the target db. One copy in the dbo schema and one copy in the "test" schema. Only the dbo schema tables however would be filled with data. The objects in schema "test" remained empty.

What happened when SF connected to the DB and started to look for the data was that it came back and reported above error (rightfully so). It would go look for "test.sf_page_nodes" instead of "dbo.sf_page_nodes". It would find the table, too, because it was created by the SQL Migration Wizard. But it would be empty. Hence the error message.

How to fix it:

Make sure that the default schema of the  db_user is set to dbo. See attached image. At least that's how I did it. It will then use the right tables. If you drop the DB and run the SQL Migration Wizard again it will also avoid that objects are created twice (see above). 

Not sure if there is an option in the SQL Migration Wizard to do this from the outset. If someone has the time to investigate this then that would be great. 

I hope this helps others who may run into the same issue.

Andrew

Hi Andrew,

Thank you for sharing your findings with the community.

Regards,
Atanas Valchev
Telerik

Sitefinity Veriosn- 9.

I have this situation after my trial license expired. The Proof-of-concept site wouldn't come up. Trying to create a dummy project just to enter license-key would fail on "file in use". So I dropped the project, rebooted machine and created project again. Then on browse, "initializing..please wait" went on forever.  So I closed that tab. Now I am getting this error. If I have changed name of project, can I look in the files or database what is expected? Because only thing I have done is drop and add project in sitefinity CMS project manager. DB-connection, security rights and default schema are Ok as suggested.