Ok, kind a funny predicament...
Copied Prod Enviroment down to Stage Enviroment (files, db - the package).
Created new site on Stage IIS (iis 6.0). Named  it test.cms6.no, and updated host fil with this host header.
Ok, browsing this site gives me exactly the same content as the Prod Site. juuuhuu :)

Did the upgrade. Went well. Except couple of Xforms  (two forms element with same name, no biggie).
Browsed the new site. Works fine. Same content at all Pagetypes works (also xforms).
Goody. Upgrade test completede. We have CMS 6 on Stage enviroment.  Let's go to Prod enviroment.

Did the same thing there.
Innstalled CMS 6.
Also did an install of a test site with demo templates. Worked fine.
Created new site in iis with hostheader prod.cms6.no (updated host file)
Copied pages and DB (renaming the DB ofcourse) and ran the site.
Goody. Now I have two sites in Prod enviroment looking exactly the same. Both running EpiServer CMS 5 R2
(As the Stage enviroment did).

Time to upgrade.
Deployment center giving the exact same messages. Everything looks fine.
But hey...Browsing the site.
Page cannot be shown. This might be becouse of maintance...etc.
Blank with page with that header.
Typing in the UI path in browser kicks in the redirect script to loginpage, but same message.
Page cannot be shown.

Whattaaaaa??

Done this a couple times now.
Stage works fine every time.
Prod dont. jiikes.


The Prod site (Cms 5) is running under ssl port 443, the other sites don't.
Could that trigger som issues?