5

We are running 2011 SP1 - HR1. Recently we started getting the following sequence of messages in the message centre when starting the GUI

The remote server returned an error: (404) Not Found
The remote server returned an error: (404) Not Found
The remote server returned an error: (404) Not Found
The remote server returned an error: (404) Not Found
The remote server returned an error: (404) Not Found
The remote server returned an error: (404) Not Found
The remote server returned an error: (404) Not Found
Loading list of languages failed
The remote server returned an error: (404) Not Found
Loading list of locales failed

The browser itself is not getting a 404 status on any response, so this looks to me like failed requests against the core service running server-side. However, I haven't been able to find any matching evidence in the logs on the server.

What further steps can I take to diagnose the root cause? Is there more logging available that I can enable? Are there any likely causes that I should be aware of?

What might be the cause of this happening on a previously well-behaved system? (I'm thinking Windows update.... anyone else seen a recent bad patch? What else might it be?)

Update: we are seeing 401 statuses for URLs such as /WebUI/Core/Controls/Tree/TreeHead.xml. Might this be related?

Update: Once the GUI has loaded, you can navigate around, and normal item lists will populate as normal, but if you try to load a list of users, you get the 404 again. The user preferences box loads Ok, but the language/locale lists are empty - I guess the GUI only tries to load them once. Can this be something specific to system lists?

  • 1
    Can you list what addons you have, as it very well might be one of the addons, like Outbound Email? – Andrey Marchuk Oct 23 '13 at 8:43
  • It's completely vanilla. We have the razor mediator installed, but I doubt if that's relevant. Other than that, nothing. – Dominic Cronin Oct 23 '13 at 8:46
  • 1
    How is authorization set up? Do you see this across browsers? – Raimond Oct 23 '13 at 9:04
  • 1
    401's are normal behavior in most cases I thought, you first get a 401 and then the request is automatically retried with credentials, that's how I understood a browser normally works. – Bart Koopman Oct 23 '13 at 10:11
  • 1
    Have you set it up on a custom host header? Has this been configured correctly? – Ryan Durkin Oct 23 '13 at 10:53
9

If you set up a new instance of SDL Tridion and you would like it to run under a custom binding you need to ensure that the configuration files are set up correctly to handle it.

The configuration files are mentioned in this question on setting up SDL Tridion with multiple hosts headers: https://stackoverflow.com/questions/9428360/i-set-up-my-sdl-tridion-2011-instance-to-run-with-multiple-host-headers-and-now/

| improve this answer | |
  • 1
    That was the problem. The Tridion explorer web site originally had two bindings (a named one, and a default localhost:80 one). Both of these were correctly configured in the CME web.config as Tridion.WPF.RedirectTo and baseAddressPrefixFilters. Then I assigned the default localhost:80 binding to a different web site, and failed to update these settings. The result was that Tridion was attempting to make calls to endpoints on localhost:80 that didn't exist. Thanks. – Dominic Cronin Oct 23 '13 at 13:51
  • Oh dear. I knew this was familiar. I've just come across a "note to self" I wrote back in December dominic.cronin.nl/weblog/… Oh well - can't win em all. – Dominic Cronin Oct 29 '13 at 17:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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