The content processing pipeline failed to process the item.

Rui Pinto Ferreira 20 Reputation points
2024-12-10T15:13:01.4433333+00:00

I have a Sharepoint 2016 FARM with 3 Servers (1App Server + 2 Frontend Servers). All Servers have the same OS and Sharepoint version. On 11/30 all Crawl's started taking a long time to finish and all with a large number of files in error. I've seen several posts, but none of them solved my problem (Restart servers, restart Services, Reset Index). Can anyone help me?

The content processing pipeline failed to process the item. ( Error parsing document ssic://. It was not possible to acquire a worker. Failed to start acquired worker; ; SearchID = )

Microsoft 365 and Office | SharePoint | For business | Windows
0 comments No comments
{count} votes

Accepted answer
  1. Xyza Xue_MSFT 30,176 Reputation points Microsoft External Staff
    2024-12-11T01:43:38.6433333+00:00

    Hi @Rui Pinto Ferreira ,

    The error message "The content processing pipeline failed to process the item" typically indicates issues with the SharePoint Search service, particularly related to the content processing component. This can occur due to several reasons, including:

    1. Insufficient User Rights: The service account for the Windows Service – Search Host Controller Service may lack the necessary user rights. Specifically, it needs:
      • SeAssignPrimaryTokenPrivilege: Allows the Search Component to modify the security access token of the ParserServer.exe process.
        • SeIncreaseQuotaPrivilege: Allows the Search Component to adjust the memory quota of the ParserServer.exe process.
        1. Parser Server Workers: If all parser server workers cannot restart, it may indicate that the pool has no more workers available. This can be caused by:
          • Broken communication between the parser server and the content processing component.
            • Excessive resource usage leading to time-outs.
              • Permission issues with required directories or configuration files.
    2. Network Issues: If there are network communication problems between the crawl server and the content server, it can block the crawl, leading to errors.
    3. ULS Logs: Review the ULS logs on the server hosting the content processing component. Look for entries related to the parser server failing to start.
    4. Check for Updates: Ensure that your SharePoint servers are up-to-date with the latest patches and updates.

    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.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

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