THIS IS ARCHIVED DOCUMENTATION

Error with ID NO_DOCUMENT_INDEXED

Symptom

When looking at the CES index logs (from the CES Administration Tool > Logs > Index or directly in the file C:\CES7\Logs\Index_YYYY-MM-dd.log), you may see errors similar to the following ones:

212285218277549773|IMPORTANT|2014-12-12|16:25:44|0|Rebuild on source Coveo_web_index - MachineName-InstanceName has been requested by domain\username.||||||||||||||||
212285218277549774|IMPORTANT|2014-12-12|16:25:44|0|Rebuilding the source Coveo_web_index - MachineName-InstanceName.|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|SUCCESS|||3514|32352||
212285218277549775|WARNING|2014-12-12|16:25:44|0|Since the live monitoring is currently enabled, the rebuild won't do anything.|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|SUCCESS|||3514|32352||
212285218277549776|ERROR|2014-12-12|16:25:44|0|Error with ID 'NO_DOCUMENT_INDEXED': No documents were crawled.|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|NO_DOCUMENT_INDEXED|||3514|32352||
212285218277549777|ERROR|2014-12-12|16:25:44|0|Queue Error: No documents were crawled.|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|SUCCESS|||3514|32352||
212285218277549778|ERROR|2014-12-12|16:25:44|0|... Coveo.CES.CustomCrawlers.CrawlerFatalException: No documents were crawled.|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|SUCCESS|||3514|32352||
212285218277549779|ERROR|2014-12-12|16:25:44|0|...    at Coveo.CES.CustomCrawlers.CustomCrawler.RefreshThread()|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|SUCCESS|||3514|32352||
212285218277549780|IMPORTANT|2014-12-12|16:25:44|0|The source Coveo_web_index - MachineName-InstanceName rebuild was stopped.|||||Sitecore Search Provider||||Coveo_web_index - MachineName-InstanceName|SUCCESS|||3514|32352||

Cause

The Coveo Search Provider is starting the Coveo Enterprise Search (CES) source before pushing Sitecore items to be indexed. Starting a source is done by enabling Live Monitoring and starting a rebuild of the source. When Live Monitoring is enabled on a source, the rebuild operation is expected to do nothing but set the source state to idle. After a rebuild operation, CES verifies if documents were indexed and throws the NO_DOCUMENT_INDEXED error when there was none.

Resolution

This is the expected behavior for the Queue crawler used by Coveo for Sitecore sources. You can ignore this error.

What's Next for Me?