Transferring an EPiServer 6 Site from an x86 Environment to x64

Thu, 28 Jul 2011 11:25:57 GMT

Here’s a quick note about a problem I faced when moving an EPiServer site between servers.

The original source server was an x86 machine, running Server 2008 and IIS7. The destination server also ran Server 2008 and IIS7 but was an x64 environment.

I set up the site, browsed it and all seemed to be fine until I tried to access the editor or admin, those threw back 404s.

It took me a bit of investigation to find the issue. It turns out that my episerver.config file was looking for EPiServer directories at C:\Program Files\EPiServer but on the new x64 environment EPiServer had been installed at C:\Program Files (x86)\EPiServer.

These broken references were causing the 404s on the editor and admin, once they were changed the site functioned as expected.

Something to watch out for!

Setting Up a New VPP

Thu, 02 Dec 2010 18:17:28 GMT

I had to configure a new VPP for a Content Channel to work with the SharePoint Connector to push documents from a SharePoint site into my EPiServer site.

So, I created a new VPP entry in my EPiServer.config…

        1: <add showInFileManager="true" virtualName="FOI" virtualPath="~/FOI/"

       2: bypassAccessCheck="false" indexingServiceCatalog="Web" 

       3: physicalPath="C:\EPiServer\VPP\MySite\FOI"

       4: name="FOIFiles" type="EPiServer.Web.Hosting.VirtualPathVersioningProvider,EPiServer" />

…and then configured my Content Channel.

All went well and SharePoint was able to upload documents.

However, when I tried to serve out the documents on the site or view them in the file manager, I kept getting 404’s.

The problem was that, in addition to the VPP entry in the EPiServer.config file, you also need to make a <location> entry in the web.config for your VPP, like so…

       1: <location path="FOI">

       2:     <system.webServer>

       3:         <handlers>

       4:             <add name="webresources" path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" />

       5:             <add name="wildcard" path="*" verb="*" type="EPiServer.Web.StaticFileHandler, EPiServer" />

       6:         </handlers>

       7:     </system.webServer>

       8:     <staticFile expirationTime="-1.0:0:0" />

       9: </location>

Perhaps an obvious thing but I didn’t see any information about this on EPiServer World so I thought I would post it here for anyone else who may encounter the same problem.

Blog posts by Robert Dougan

Transferring an EPiServer 6 Site from an x86 Environment to x64

Setting Up a New VPP