One of our customer's IT departments came to us with the Windows application event log bloated with errors from EPiServiceIndexingService. The only information available was this:
"EPiServer Indexing Service has problems indexing some of the locations, please consult the log file for details."
But, from what I've understood the log isn't default activated, so go fish. After a quick support-session with EPiServer I was routed to this blog post:
A post that, amongst other things, explains how to activate the log4net-module for the Indexing service with the following steps:
- Put the log4net.dll into the EPiServerIndexingService-folder, under Shared services in your EPiServer
- Create the most leight weight config-file possible, see below, and name it: log4net.config. And put it in the same folder. Parameters and configuration to the log-service can be changed at a later state.
- Restart the service
Example of log4net.config-file:
<?xml version="1.0" encoding="utf-8" ?>
<appender name="ErrorAppender" type="log4net.Appender.FileAppender" >
<file value="C:\temp\LogServerError.log" />
<appendToFile value="true" />
<conversionPattern value="%d [%t] %l - %m%n" />
<level value="ALL" />
<appender-ref ref="ErrorAppender" />