A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Jacob Khan
May 27, 2010
  7447
(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

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!

Muhammad Kashif
Muhammad Kashif 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
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025