0

We have an on-premises SharePoint 2016 farm consisting of 3 servers (application&search+wfe+database). We recently found that the enterprise search wasn't working. When looked at the crawl logs under the Search Service Application, the following error was reported and the crawl wasn't working:

Content Processing Pipeline Failed to Process the Item

There were comments on Internet suggesting that this could be due to an issue with Manged Matadata Property Mappings, but when click on the Search Schema in Search Administration, it displays the following error without showing the Managed Properties.

An unknown error occurred.

We've tried restarting the Search Host Service and Time Service, but it didn't help.

Any assistance with resolving the issue is much appreciated.

Improve this question

1 Answer 1

Reset to default
0

Have a look in the ULS logs. Check the Search Databases health. It could be any number of things, but the ULS is the place to start.

Improve this answer
2
  • Thanks for the reply. I was able to re-produce the error in my lab environment by installing The February CU. I've provided the error messages from the ULS logs below for others benefit. Installing the latest update didn't resolve the issue and eventually, I ended up submitting a ticket to Microsoft. The solution was to build a new Search Application. The errors <br/> earchServiceApplication::QueryManagedProperties--Exception: System.IndexOutOfRangeException <br /> failed propertyName PopulateTimeInterval exception System.IO.FileNotFoundException: The system cannot find the file specified.
    – jayd2020
    May 9, 2020 at 7:31
  • Yep, sadly the CU can lead to these problems.
    – Matthew McDermott
    May 11, 2020 at 18:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.