World is now on Opti ID! Learn more

robert.dougan@mimtech.co.uk
Dec 2, 2010
  4491
(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

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |