When updating the preview (either by clicking on 'Update Preview' or by saving changes) I get the following error:

enter image description here

In the console of chrome I see the following error

enter image description here

I checked the file system and Services.svc is in the right location.

The good old Event Viewer also noticed this error enter image description here

Is this a configuration problem or an infrastructure problem? Does anyone recognize this issue?

Hope you can lead me to a solution, thanks!

  • 1
    Have you tried giving it a valid null link? j/k Commented May 21, 2015 at 9:21
  • It seems that it was unable to figure out the URI of (some of) the items. Could you check the request to that web service call and see which variable was null? That would help narrow down the issue. Commented May 21, 2015 at 9:25
  • Haha, lol needed that ;) I found the solution, some templateIDs where null in the request, because that components didn't have a component template. Thank you for the hint (and the joke)! Commented May 21, 2015 at 12:10
  • Great! Glad I could help a little :) Commented May 21, 2015 at 13:20

2 Answers 2


Peter Kjaer and Bart Koopman gave the right hints. When I checked the POST request (using the 'Network' tab in Google Chrome), I saw the following:

enter image description here

Some TemplateId's were 'null'. This is because that components didn't have a component template.

In my DD4T view I created the XPM tag manually because there is no Component Presentation for this component.

In that tag I only specified the Component Id

        @Html.Raw("<!-- Start Component Presentation: {'ComponentID' : '" + footer.Id + "' } -->")

To fix this, I created a 'Dummy' Component Template and I am using that ID now as TemplateID for the components that don't have a Component Template, like this:

@Html.Raw("<!-- Start Component Presentation: {'ComponentID' : '" + footer.Id + "' 'ComponentTemplateID' : '" + DummyCTID + "'  } -->")

That's it :)


I'm no expert in debugging this, but the error sounds to me like you might have an invalid Component link in your content.

I've seen a similar issue before where the content of a Component was invalid, while the SDL Tridion UI still found it acceptable, the XPM Session Preview OData service couldn't hande it.

So I would first check the HTML source of this page and validate that all XPM comments have valid URIs specified, and then check the actual content on the Page.

Perhaps good to start with a simple reproduction scenario, is this reproducible on every Page, even on empty Pages? Or is it only a specific Page or Component Presentation that causes this?

  • Thank you Bart, I found the solution. Some of my XPM tags where missing a templateID Commented May 21, 2015 at 11:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.