Are you sure that there isn't any code activating indexing of page files? Also, what version of the .NET API and CMS integration are you using? In the old days of Truffler page files indexing was active by default.

Can't find any code that would activate indexing of page files.

We are running the 1.0.0.278 version the one for CMS 6 R2.

Did a run with PageIndexer.Instance.Conventions.DisablePageFilesIndexing(); added but still getting the same error.

Checking with Reflector it seems that IndexPageFiles would default to true. Where would the Index Object first get instantiated when running the indexing job?

// Generated by .NET Reflector 
namespace EPiServer.Find.Cms
{
using System;
using System.Runtime.CompilerServices;

public class IndexOptions
{
public IndexOptions()
{
this.IndexRelations = true;
this.FilterPages = true;
this.IndexPageFiles = true;
}

public bool FilterPages { get; set; }

public bool IndexPageFiles { get; set; }

public bool IndexRelations { get; set; }
}
}

Hi,

This is a bug in the current versions (7.0.586.0 and 1.0.0.278) of EPiServer.Find.CMS.dll when using the EPiServer.Web.Hosting.VirtualPathNativeProvider for serving PageFiles.

This will be fixed in the next EPiServer Find update.

Regards,
Henrik

And for future reference. The workaround while waiting for a fix is to set your PageFile provider to use EPiServer.Web.Hosting.VirtualPathVersioningProvider. (Note this might not work if you already have files in your vpp)

Thanks for the help Henrik!