Retry of query machine ‘Server Name Here’ has failed with error: The content index is corrupt. 0xc0041800. It will be retried again in 900 seconds. Component: 39f41350-d1ae-48ff-ad09-04e9da90185d
An index corruption was detected in component ShadowMerge in catalog Portal_Content. Stack trace is .Component: 39f41350-d1ae-48ff-ad09-04e9da90185d
Query machine ‘Server Name Here’ has been taken out of rotation due to this error: The system cannot find the file specified. 0x80070002. It will be retried in 15 seconds. Component: 39f41350-d1ae-48ff-ad09-04e9da90185d
It turned out that the index had been corrupted on that server due to the machine rebooting while the index was propagating from the index server. Luckily there was an easy fix.
First, I removed the search role from the problem server via the Services on Server screen in Central Admin. This allowed the crawl to continue and the index to propagate to the other query servers. After the crawl completed, I reinstalled the search role on the query server. Before doing so, however, I renamed the folders that contained the corrupted index files on that machine to ensure that a fresh copy of the index would be propagated.
The problem server picked up the index during the next propagation and was automatically added back into the query rotation.
