SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems ( - Contact me direct: or call 704-873-8846 x704.

Search This Blog

Wednesday, September 16, 2015

SharePoint 2013 Search Crawler failing, Event ID 1400

You might come across this issue when setting up a new farm - the errors vary, but in the System Event Application log, you will begin seeing warnings with Event ID 1400.

The issue is that the Search Service account doesn't have the proper local secuity policies set. Most of us are familiar with setting:

  • Impersonate a Client After Authentication
  • Logon as a Service

However, unique to this account, it needs:

  • Adjust memory quotas for a process

If the account doesn't have Adjust memory rights, the 1400 error occurs and SharePoint will not crawl content.

To fix, simply search for "Local Security Policy" and open it. Expand the Local Policies then select User Rights Assignment and add the Search Service Account (and the Farm Account) to each of the above polices:

Run an IISReset on the farm then start a new crawl.

1 comment:

Jessica Matters said...

Outstanding! What a wonderful content you've written on SharePoint.Thank you so much for sharing your knowlege on SharePoint Developer with us. Please keep sharing such as great content in future.