Cloudy with a Chance of InsightsReaching for the Cloud NewsletterSubscribe to NewsletterSubscribe via RSS
The Microsoft Cloud Blog

Expert insights on Microsoft Azure, Cloud Architecture, and Enterprise Technology

1 min read
SearchSharePoint 2013

Error: The content processing pipeline failed to process the item. ( Object reference not set to an instance of an object. )

ShareLinkedInXBlueskyThreadsFacebook

I came across the following error in the crawl logs of a SharePoint 2013 instance.

“The content processing pipeline failed to process the item. ( Object reference not set to an instance of an object. )”

In my case this turned out to be because I had deleted the managed metadata service that had been originally created for this farm.  This was causing the existing search service to attempt to reference terms in the old managed metadata service and failing.

Recreating the search service solved this issue for me.

Want more cloud insights? Listen to Cloudy with a Chance of Insights podcast:

Spotify | YouTube | Apple Podcasts

Tags

errorManaged metadata Service
Like this article?

Comments

Loading comments...

Richard Hogan - Global Chief Architect, Microsoft Practice

Richard Hogan

Global Chief Architect, Microsoft Practice | IBM

Global Chief Architect, Microsoft Practice at IBM. 20+ years experience working at the intersection of cloud architecture, security, and emerging AI capabilities across Azure and the wider Microsoft ecosystem. Host of the Cloudy with a Chance of Insights podcast. Regular speaker at tech conferences and active contributor to the Microsoft Tech Community.

LinkedInYouTubeMore About Me

You might also like

SharePoint 2013 Error: The filtering process has been terminated

I had just completed a PowerShell scripted deployment of a SharePoint farm and was just performing the final checks when I noticed the following error in the crawl logs. “The filtering process has been terminated” This turned out that because in the PowerShell script I had specified that the SharePoint installation location should be different to… Continue Reading →

Error: Specified value is not supported for the domainname parameter.

I came across the below error when trying to create a new web application via PowerShell against a 2013 farm. “Specified value is not supported for the domainname parameter error when creating web apps” This appears to have been caused by the machine loosing connectivity to the domain so even though my server was domain… Continue Reading →

Attackers exploiting new critical OpenMetadata vulnerabilities on Kubernetes clusters

Attackers exploiting new critical OpenMetadata vulnerabilities on Kubernetes clusters

This Microsoft article provides guidance and analysis regarding the recently published vulnerabilities in the OpenMetadata platform. These vulnerabilities could potentially be used to access Kubernetes workloads and leverage them for cryptomining activity. Read the full article here….

Cloudy with a Chance of Insights

Practical discussions on cloud engineering, architecture, and the reality behind the diagrams.

Reaching for the Cloud

Bi-weekly reflections on cloud architecture, Azure, and the decisions teams wrestle with in practice.

Get the newsletter by email →Follow along on LinkedIn →
← View All Posts