Hey!

At first glance it sounds like the pageStartId-attribute in episerver.config is incorrect. But since it isn't that...

What kind of error do you get when navigating to http://<yoursite>/? I'm pondering if the changes to web.config might have gone astray.

Hi Daniel,
I've been over  the config and I can't spot any errors ;-( So I'm not sure what I'm missing.
The error I get is a HTTP error from the web server; it's a 403.14 - Forbidden (The webserver is configured not to list directory content)

For some reason the EPiServer is not picking up the / site...
BTW, default.aspx is set as default document, not that it matters...

//Morten

Okay. Is there an actual default.aspx that inherits from EPiServer.TemplatePage in the root?

What happens if you try http://<yoursite>/<language> e.g. http://localhost/en?

Thank you for helping out here Daniel, much appreciated!

/no gave me the startpage, but what has changed after the upgrade?  Beats me ;-)

//Morten

Appears like the modules aren't firing for the path "/". :) Did you add Default.aspx to the root? And have it inherit from EPiServer.TemplatePage?

I don't have a default.aspx page, my startpage is further down in the folder structure.
Besides there are no code changes between CMS5 and CMS6.

This is wierd...

//Morten

The change is in how the IIS is handling your request, I'm afraid. I hope to have a chance and dig deep into this problem over the weekend. 

But as a workaround I think if you add a default.aspx page (and don't really add any other logic/markup to it) and have it inherit from TemplatePage, then EPiServer will use your start page that is defined further down in the structure based on the startPageId attribute.

So much for a smooth upgrade and no breaking changes...
I'll try to add a default page though, if that works then all is fine really.

Thank you for your time Daniel!

//Morten

No worries, Morten :)

Let me know how it works out!

Sorry for the inconvenience, it is most probably caused by bug #36105: "CMS6: Start page returns 404 on some upgraded multilanguage sites", it has been fixed and will be available in the released version.