Jacob Khan
May 27, 2010
  7571
(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
Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |