Deployment from iis7 to iis6

Regressing this way (from IIS7 local to IIS6 in production) is difficult as there are quite a number of differences between the web.config files, and all of the help only tells you how to upgrade your configuration from IIS6 to IIS7 - not the other way round.

Shameless plug - but I wrote a blog post about exactly this - the basic crux is that I'd recommend starting with a default IIS6 EpiServer web.config (the blog post tells you where to find this) and updating it manually with all of your site specific settings (episerver - VPP - any httpmodules etc etc).

It should be possible to modify an EPiServer IIS7 web.config back to IIS6 but somehow I've just never got it to work. Its always been quicker for me to start from scratch.

Good luck :)

I have also given this regression a go with the "side by side config comparison" method.

I've tried the standard config files found in the location you specify in your blog post and also default config files in an empty website created by deployment centre and also a combination of both.

I cannot see any major differences between a working CMS 6 site and the "regressed" CMS 6 site. Web.config files and episerver.config files have only differences in settings as you mention, site specifics, VPP etc.  However I have the same problems outlined by Mark in the original post.

Symptoms:

• admin can not be reached by siteurl/uipath/admin - returns a 404
• siteurl/Util/login.aspx - returns a 404
• no images show on site
• right click context menu is not available as "EPi is undefined" (i have checked the util/Util solution elsewhere on the forum - no luck)

Yep these symptoms sound more like some 'other' missing configuration rather than any application specific stuff. Off the top of my head, heres some things it could be,

1) Have you set up the wildcard script mapping in iis6? -(http://world.episerver.com/Documentation/Items/Tech-Notes/EPiServer-CMS-5/EPiServer-CMS-5-R2-SP1/Configuring-EPiServer-CMS-5-Enterprise/)

2) Is EPiServer installed on the production box - obvious but you'd be surprised.....?

3) Are the VPP settings pointing to the correct folders to serve the EPiServer UI - something like 'C:\Program Files\EPiServer\CMS\5.2.375.236\application\UI' by default.

thanks for your suggestions but unfortunately the answer to all of those is yes!

the CMS 6 site with the near identical config files is running just fine on the same server.

I'm having exactly the same problem now and after many hours trying to fix it, changing and comparing the web.config files over and over again, I'm still stuck with the errors you guys mention above. I'd appretiate if you could post the solution to the problem, since I see the last post on the thread was written about one year ago.

Thanks in advance

Hi Guys i am also having the same problum...

Is there any solution to this problum???????????????

My suggestion would be to install a fresh empty site into your iis6 environment then publish your project specific files into that environment. I remember that the only way I got around this was to start again with a fresh site.

This is much easier if you are using PageTypeBuilder to manage your pagetypes in code.

I get 404 when browsing the dashboard. Everything else works fine. The site works fine in the development environment but not in test. Both are Server 2008 R2 and both running integrated mode on IIS 7,5.

all config files are nearly identical

any ideas?

I tried this: http://www.epinova.no/blog/Tore-Gjerdrum/dates/2011/9/problems-with-dashboard/ but it didnt help me.

Have you tried installing a fresh site in your destination environment then publishing your project specific files into it? That way you don't have to rely on manually setting up everything the EPiServer deployment centre would do for you when you create a new site.

To be honest, unless your problem is related to IIS6 deployment I would probably start a new thread.

As someone has already recommende before ,the best way to address this issue is to install a sample site and then pointing the application folder path to your published site.For manual installation the issues lies in web config.To be presice you have to add in few extra http handler in the web config for IIS 6.Please check sample httpModules and httpHandlers section for IIS 6  web config.

<httpModules>
      <add name="InitializationModule"
           type="EPiServer.Framework.Initialization.InitializationModule, EPiServer.Framework" />
      <add name="FirstBeginRequestModule"
           type="EPiServer.Web.InitializationModule, EPiServer" />
      <!--<add name="BasicAuthentication" type="EPiServer.Security.BasicAuthentication, EPiServer" />-->
      <add name="Initializer"
           type="EPiServer.Scheduler.Initializer, EPiServer.Scheduler" />
      <add name="WorkflowRuntime"
           type="EPiServer.WorkflowFoundation.WorkflowSystem, EPiServer.WorkflowFoundation" />
      <add name="UrlRewriteModule"
           type="EPiServer.Web.UrlRewriteModule, EPiServer" />
      <!--<add name="EventSubscriberHostModule" type="EPiServer.EventSubscriberHostModule, EPiServer" />-->
      <!--<add name="IIS5WebServicePostModule" type="EPiServer.Web.IIS5WebServicePostModule, EPiServer" />-->
      <add name="ScriptModule"
           type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add name="ShellRoutingModule"
           type="EPiServer.Shell.Web.Routing.ShellRoutingModule, EPiServer.Shell" />
    </httpModules>
    <httpHandlers>
      <add path="TrackerHandler.ashx"
           verb="*"
           type="EPiServer.Trace.CMS.Handlers.TrackerHandler" />
      <!--Static files served by EPiServer.Web.StaticFileHandler will have cache information added to Response headers
          so clients can cache files according to passed header information.-->
      <add path="*.png"
           verb="GET,HEAD"
           type="EPiServer.Web.StaticFileHandler, EPiServer" />
      <add path="*.jpg"
           verb="GET,HEAD"
           type="EPiServer.Web.StaticFileHandler, EPiServer" />
      <add path="*.jpeg"
           verb="GET,HEAD"
           type="EPiServer.Web.StaticFileHandler, EPiServer" />
      <add path="*.css"
           verb="GET,HEAD"
           type="EPiServer.Web.StaticFileHandler, EPiServer" />
      <add path="*.js"
           verb="GET,HEAD"
           type="EPiServer.Web.StaticFileHandler, EPiServer" />
      <add path="*.gif"
           verb="GET,HEAD"
           type="EPiServer.Web.StaticFileHandler, EPiServer" />
      <remove verb="*"
              path="*.asmx" />
      <add verb="*"
           path="*.asmx"
           validate="false"
           type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add verb="*"
           path="*_AppService.axd"
           validate="false"
           type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add verb="GET,HEAD"
           path="ScriptResource.axd"
           validate="false"
           type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add verb="*"
           path="*.mvc"
           type="System.Web.Mvc.MvcHttpHandler, System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add verb="*"
           path="UrlRouting.axd"
           type="System.Web.HttpForbiddenHandler, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

    </httpHandlers>

I´m guessing this thread is log dead by now, but I experienced the same problem today. Remember to also check the EPiserver util paths if working in a 64-environment locally. My paths were pointing to "\program files(x86)\..."