SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our search application appears to be working fine. Crawls do succeed, queries return, and general usage appears to be unaffected.

However, with every full crawl, we get thousands of the following message appearing in the logs:

01-15-2014 02:00:57.88    NodeRunnerContent1-7a4b7212-aa0    (0x0D10)    0x06CC    Search    Content Processing    ajyhd    Unexpected    DisplayAuthorEvaluator : (IStringField)aliasField == null

Many google attempts have resulted in literally zero results, so I know this is a long shot. Does anyone have any ideas even of where I might look for further diagnosis?

(This is Sharepoint 2013, new farm, but with some content migrated from 2010)

share|improve this question
i dont know much to answer but this should put you into the right direction, its todo with the sql database... there is an aliasField that is null within the content database that is possible that wasnt used in 2010 but is in 2013 – ali Sharepoint Jan 15 '14 at 9:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.