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
Search

Error: Attempted to make calls on more than one thread in single threaded mode using multiple Content by Search web parts

ShareLinkedInXBlueskyThreadsFacebook
In SharePoint 2013 when adding more than one Content by Search web part to a page you may receive the following error
“Attempted to make calls on more than one thread in single threaded mode. (Exception from HRESULT: 0x80010102 (RPC_E_ATTEMPTED_MULTITHREAD)) Correlation ID: 00000000-0000-0000-0000-000000000000“
This is caused by a bug in the original release, this has been fixed in the April Update, which can be downloaded from here http://support.microsoft.com/default.aspx?scid=kb;EN-US;2726992
Please be aware that this is not really a CU as it requires http://support.microsoft.com/kb/2767999 to be installed first.

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

Spotify | YouTube | Apple Podcasts

Tags

2013content by search
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: The content processing pipeline failed to process the item. ( Object reference not set to an instance of an object. )

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… Continue Reading →

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