SharePoint 2013 Search: Search Crawl Errors after SQL Server 2012 SP3 Applied

After we applied SQL Server 2012 SP3, we noticed that the search crawls (which are mainly against Line of Business Data) where producing errors. The error was:

The content processing pipeline failed to process the item. ( Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index; ; 

After trying many things such as resetting index, recreating the content source, etc., I finally resolved the issue.

I needed to go into the Business Data Connectivity Services service application and Upgrade the External Content Type profile pages:

After I performed the upgrade, the crawls successfully completed with no errors.

SharePoint 2013 Search: Crawl Issue - SPServiceContextScope is Being Disposed Out of Order

We were experiencing "blank" search results from certain result types related to business data connectivity service content sources. When attempting to run full crawls, there would be periods of crawl issues in the crawl log:

Error while crawling LOB contents. ( Error caused by exception: System.InvalidOperationException This SPServiceContextScope is being disposed out of order.; SearchID = <<guid>> )

I figured this was causing the empty results to appear and there seemed to be no way of fixing this. I didn't want to reset all content as we have many content sources and I would spend all day trying to crawl each one. So therefore I decided to try a less disruptive approach and it worked!

Here's what I did:

1. Deleted the Content Source from the Search Service Application
2. Recreated the Content Source using the same name.
3. Run a full crawl on the content source
4. Once the full crawl is finished, repeat for any other BCS content sources.

This was very easy and it fixed all of my blank results. In addition, this process did not bring down search or remove any content. This was a great fix-in-place solution!

On completion of my full crawls, I now had no Warnings or Errors on the two content sources I recreated: