Try our conversational search powered by Generative AI!

Jacob Khan
May 27, 2010
  6944
(2 votes)

Failed to load root node – Live Monitor

Today I installed live monitor on a CMS 6 site with PageTypeBuilder, PageTypeIcons and alot of other cool stuff. After following the installation I ran into the issue of “Failed to load root node”. This was also the issue that Kvart ran into when he installed live monitor. Libardo gave me the tip of using fiddler to see where it actually went wrong. Fiddler told me that it found the correct startpageid which was my startpage. But it could not find the page it self. My bindings of the site was setup to be “* :17020” which meant I could use the computers name and 17020 to access the site. I changed it so that the the binding was jacobkhan-imac and put that url in the web.config as stated by the instructions on world and there we have it.

In other words it could not find the site since I put in an ambigous url in web.config

Now everything works like a charm

image

May 27, 2010

Comments

Joakim Jormelin
Joakim Jormelin Feb 27, 2011 11:27 AM

Hi Jacob, I'm aware that this is an old post but I'm getting the exact same error but i cant fix it.
I've set "www.mydnsname.se" in both episerverframework.config and in web.config but still no luck.
I'm running on windows 2008 r2 64bit.


Any ideas?

spinto@mimecast.com
spinto@mimecast.com Mar 10, 2011 04:32 PM

Hi, I'm in the same boat as Joakim above. If anyone has any ideas other than specifying baseAddressPrefixFilters please do let me know!

Mar 5, 2013 10:46 AM

Hi - does anyone manage to get this working .I am facing similar issue , have set the correct end point addresses but it seems to stuck in loading clientaccesspolicy / cross domain xml files.

Live monitor works fine when I access the site direct with IP address where it is bind to but while accessing with site URL which comes through a load-balaner it fails.
Any ideas ?

Please login to comment.
Latest blogs
Do not upgrade to EPiServer.CMS.Core 12.21.4 without reading this!

Todays update of EPiServer.CMS.Core 12.21.4 alters default sort order in an unexpected way, when you are working with muligple languages and have...

Tomas Hensrud Gulla | May 14, 2024 | Syndicated blog

Upgrade Optimizely CMS From v11 to v12

Why Upgrade? There are many improvements implemented in version 12, but most importantly is that the whole framework is migrated from .Net Framewor...

MilosR | May 13, 2024

Configured Commerce - Infrastructure Updates Ahoy!

I'm very happy to share an important milestone - we no longer have any customers in our legacy v1 environment!  This means that the Configured...

John McCarroll | May 10, 2024

A day in the life of an Optimizely Developer - Enabling Opti ID within your application

Hello and welcome to another instalment of A Day In The Life Of An Optimizely developer, in this blog post I will provide details on Optimizely's...

Graham Carr | May 9, 2024

How to add a custom property in Optimizely Graph

In the Optimizely CMS content can be synchronized to the Optimizely Graph service for it then to be exposed by the GraphQL API. In some cases, you...

Ynze | May 9, 2024 | Syndicated blog

New Security Improvement released for Optimizely CMS 11

A new security improvement has been released for Optimizely CMS 11. You should update now!

Tomas Hensrud Gulla | May 7, 2024 | Syndicated blog