We setup Experience manager using the following guide with Tridion 2013 SP1 HR1 and DXA 1.2 (.NET) in the CD side. Most of it is working fine.

Inline editing is working fine for pages and components. When editing a single page (with global content as well), XPM works fine without any issues and content is refreshed when “Reloading the page” after successful publish.

We are hitting one issue with the update preview / refreshing the content for other publications (when global content was edited). The session preview ODATA service is accessible from both the CM and CD machines.

Preview not up to date warning

The preview for this page is not up to date Your changes to this page make an update of the page preview necessary

Upon clicking the "Update the Page Preview" or "Update Preview"; the CME is throwing the below error:

Unable to update the changes using OData Service. The remote server returned an error: (404) Not Found.

Developer console shows the below error.

enter image description here

CM Event logs show the following error.

Unable to update the changes using OData Service. The remote server returned an error: (404) Not Found. Component: Tridion.ContentManager.Publishing.PreviewService Errorcode: 1003 User: NT AUTHORITY\NETWORK SERVICE StackTrace Information Details: at System.Net.HttpWebRequest.GetResponse() at System.Data.Services.Client.DataServiceContext.SaveResult.BatchRequest(Boolean replaceOnUpdate) at System.Data.Services.Client.DataServiceContext.SaveChanges(SaveChangesOptions options) at Tridion.ContentManager.Publishing.PreviewService.ServiceImplementation.Preview(IEnumerable1 publishedItemsInfo, TcmUri publishingTargetId) at Tridion.ContentManager.Publishing.PreviewService.ServiceImplementation.Preview(IEnumerable1 publishedItemsInfo, TcmUri publishingTargetId) at SyncInvokePreview(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

I could not find much information in the logs to help assist further.

I referred HERE (very different error from above) and HERE (close but 406) but could not resolve.

Publication Target configuration:

Content Delivery Endpoint URL   : https://mysession-preview-service/odata.svc/
OData Access Token URL  : <Blank>
User Name               : <Blank>
Password                : <Blank>
Website URLs            : https://my-root-domain.com/

I am looking to enable inline editing for all children under my root parent domain like https://my-root-domain.com/context1, https://my-root-domain.com/context2 etc.

Update 1:

I am able to browse "https://mysession-preview-service/odata.svc" without any issues but "https://mysession-preview-service/odata.svc/" (with a trailing slash) is returning a 404 in the browser as well. Is this expected behavior?

The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /odata.svc/

Cd Core Logs:

2017-01-09 15:03:10,084 ERROR WritableODataClaimProcessor - Resource path is not valid!

  • 1
    How did you configure XPM settings on your Publication Target? Jan 9, 2017 at 18:32
  • I have updated the publication target settings to the question Rick.
    – Shiva
    Jan 9, 2017 at 18:44
  • 1
    What do you get if you enter https://mysession-preview-service/odata.svc/ in a browser? Jan 9, 2017 at 20:17
  • I have updated the question Rick. Is that expected? Any specific configuration that I should be looking at?
    – Shiva
    Jan 9, 2017 at 21:06
  • Try removing the trailing slash from the CD Endpoint URL in the Pub Target config. Jan 10, 2017 at 18:47

1 Answer 1


The bindings in my web.xml was what was causing the issue with the ODATA service (a combination of how SSL termination happens in our load balancer and ODATA server). Thanks to Brandon (from SDL support) for pointing that out.

Finally, we had disable the DD4T cache and disable session preview for optimum acceptable behavior.

Thanks to Albert's blog on troubleshooting SDL tridion XPM with session preview. Helped me confirm some of my above settings as well.

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.