A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

robert.dougan@mimtech.co.uk
Dec 2, 2010
  6093
(0 votes)

Setting Up a New VPP

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.

Dec 02, 2010

Comments

smithsson68@gmail.com
smithsson68@gmail.com Dec 3, 2010 03:43 PM

Thanks for this Robert!

Jan 18, 2011 04:52 PM

thanks for this.. just what I was looking for.

Please login to comment.
Latest blogs
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025