Aug 27, 2010
  7066
(4 votes)

How to get EPiServer Search to work on Windows Server 2008 R2

EPiServer uses the Microsoft Indexing Service to create the indexes for the built in EPiServer search control.

To get it to work with Windows Server 2008 you need to do a couple of setups.

Here’s my action list - hope I can save someone else’s time…

 

1. The MS Indexing Service is not installed by default on the 2008 Server, so we need to get this up and running: http://support.microsoft.com/kb/954822 (I run a reboot after this. Not sure if its needed)

2. Then we need to add a index catalog. Start with firing the CIADV.MSC

3. Right click, choose “New” and “Catalog”

4. Enter a name for your catalog (the default is “Web”) and browse to your web folder (typically the VPP folder)

5. Choose “Properties” for the catalog you just added and go to the folder “Tracking”. Make sure the “WWW Server” points to your    web site

6. After that, right click on the catalog you just added and choose “New” “Directory”.

7. Create directories to the folders you want to index – i.e the “PageFiles” and “Documents” folders

8. Restart the MS Indexing Service after the creation of the catalog

9. Edit the “EPiServer.IndexingService.exe.config” hidden under your EPiServer installation (…EPiServer\Shared\Services\Indexing Service). Make sure the  connectionstring (one for each item root index) has the correct database values. In addition, the “filePath” must lead to the right VPP folder (i.e. …\VPP\Global)

10. Edit the “episerver.config” – make sure you are using the “VirtualPathVersioningProvider”. Important: The “indexingServiceCatalog” is the one you created in step 4

<add showInFileManager="true" virtualName="Global Files" virtualPath="~/Global/" bypassAccessCheck="false" name="SiteGlobalFiles" type="EPiServer.Web.Hosting.VirtualPathVersioningProvider,EPiServer" indexingServiceCatalog="Web" physicalPath="[YOUR PATH]\VPP\Global" />

11. Delete any “index” folder under your VPP\Global, VPP\Documents, VPP\PageFiles (probably you don’t have any)

12. Restart the EPiServer CMS Indexing Service (runs under Administrative Tools ->Services)

13. Take a look at Mari’s blog on how to test if your CMS is ready for searching: http://labs.episerver.com/en/Blogs/Mari-Jorgensen/Dates/2009/11/Searching-for-files-in-EPiServer-CMS-5/

 

 

Good luck!

Aug 27, 2010

Comments

Jørgen Tonvang
Jørgen Tonvang Sep 21, 2010 10:33 AM

Great post. I think the most obvious "gotchas" are that the Indexing Service is not installed by default on 2008, and when you do install it, the Web catalog (that is refered to by default in web.config) has to be created.
One would think that the EPiServer deployment center would handle (or at least inform about) this upon installation, but it seems the EPiServer search has a really low priority these days...

Per Nergård (MVP)
Per Nergård (MVP) Sep 28, 2010 07:48 AM

Excellent.

Mar 31, 2011 05:21 PM

Indexing Service is only needed if you wish to make files referenced by EPiServer.Web.Hosting.VirtualPathNativeProvider searchable. Files referenced by a EPiServer.Web.Hosting.VirtualPathVersioningProvider are indexed internaly by EPiServer CMS and should not be indexed by Indexing Service.

Johan Book
Johan Book Dec 2, 2011 11:15 AM

Searching in native files isn't working for EPiServer CMS 6 R2 regardless of how much you try to configure the Index Service ;-) This is confirmed to be a bug. See http://world.episerver.com/Support/Bug-List/#bug,EPiServer%20CMS,74385,%2b4d5gb25szlPurXylr9TFRIdi%2fs%3d

Sigve Fast
Sigve Fast Jan 19, 2012 11:09 AM

Thanks

Please login to comment.
Latest blogs
How to get the Page Tree back in Optimizely CMS

Lost the page tree in Optimizely CMS? Here's why it happens and the non-obvious fix to get it back.

Henning Sjørbotten | Apr 10, 2026 |

Optimizely CMS 13 and the first bug fixes

The first bug fixes for Optimizely CMS 13 is here!

Tomas Hensrud Gulla | Apr 9, 2026 |

lunchin Optimizely Cloud Extensions now supports CMS 13

lunchin.Optimizely.Cloud.Extensions version 2.0 has been released today which adds support for Optimizely CMS 13.

Mark Hall | Apr 9, 2026 |

Running the Optimizely CMS 13 Alloy Site on macOS with Docker

In my first Apple Silicon post and the 2025 revisit I covered running an Optimizely Foundation site on an M1/ARM Mac. This time I wanted to try...

Stanisław Szołkowski | Apr 9, 2026 |

Stott Security v7 for Optimizely CMS 13

Stott Security version 7 is now available for  Optimizely PaaS CMS 13 , introducing support for configuring security headers by both  application...

Mark Stott | Apr 9, 2026

Optimizely CMS 13 and errors when creating pages after upgrade

After upgrading to Optimizely CMS 13, I ran into issues creating pages and deleting media. The fix was easy!

Tomas Hensrud Gulla | Apr 9, 2026 |