Share via

SharePoint 2016 crawl error- The content processing pipeline failed to process the item. ( ExpandSegments; ; SearchID = xxxxx )

Navas Shereef 141 Reputation points
2022-02-02T08:02:05.193+00:00

Hi,

Our 2016 farm search not crawling the new records. Scenario: There are 10000 records and only 200 records crawled and other records crawl log throws "The content processing pipeline failed to process the item. ( ExpandSegments; ; SearchID = xxxxx )" error. Crawled records modified time was before year.

According to parser-server-failed-to-start , I checked all the user rights and rights were already assigned properly.

Also, I tried to track the uls log similar to sharepoint-search-application-return-the-content-processing-pipeline-failed-to, uls log didn't throw any error relating to the metadata multi value error.

Any suggestions?

Microsoft 365 and Office | SharePoint Server | For business

1 answer

Sort by: Most helpful
  1. CaseyYang-MSFT 10,466 Reputation points
    2022-02-03T03:24:23.897+00:00

    Hi @Navas Shereef ,

    Is there anything has been changed before the issue occurs? Please follow these steps to troubleshooting this issue:

    1.You could try to reset the search index.

    2.Per my research, like lots of blogs said you should make sure the value for ‘Allow Multiple Values’ is set as same for the Managed Metadata Site Column and the Managed Property.

    3.Did you change the default zone of web application to use HTTPS instead of HTTP? In some cases, they switched site url to HTTPs and the issue was resolved.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.