Content Indexing function 'CISearch::EcGetRowsetAndAccessor'


We are having exchange 2010 with 2 nodes for mailbox with Dag and 2 nodes of CAS & HUB (all are VMs)

There was a disaster all servers got restarted abruptly. Then after bring up all above servers. I am getting below error in application event log.

Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch. 
Mailbox Database: Databaseabc 
Error Code: 0x80043629 

I tried starting the Microsoft search (Exchange) service on both CAS servers which were stop and set to manual. But after that also still seeing above error. Kindly need your valuable suggestion to rectified the problem.

Still i am not facing any problem as such i am able to search mails. 

Thanks & Regards,


July 26th, 2015 8:47am


Below things will be affected if the content index is not healthy

1) We will not be able to perform  eDiscovery search in the entire organization.

2) And also mailbox database in a DAG will not automatically failover if the content index is not healthy and it shows as failed and suspended.

First check the content index state by running the below command 

Get-MailboxDatabaseCopyStatus | fl Content*

If you see them failed and suspended rebuid them with the below command 

Update-MailboxDatabaseCopy -Identity DBname\MBXservername  -CatalogOnly

Log on to the affected server and navigate to the below location where you have host controller files

<C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController

Set the host controller service and Microsoft exchange search to disabled and stopped state

Rename the folder hostcontroller to hostcontroller.old    and start the host controller service this time it should most probably start the service without any issues

Once the service starts it will build new content indexes for the mailbox databases on the affected server.

Free Windows Admin Tool Kit Click here and download it now
July 26th, 2015 9:25am

Hi Champ,

Thank you for your question.

This issue occurs because Exchange Search has a hard-coded prefix search limit of 200,000 nodes for a single character search. When a prefix search exceeds this limit, the search returns QUERY_E_TOOCOMPLEX. Therefore, 0x80041606 is logged as part of event ID 9877. By default, all searches that use Outlook online mode in an Exchange 2010 environment are prefix searches. Using single digits or letters causes the system to search for all numbers or words that begins with the single digit or letter across the whole mailbox database. If the 200,000 nodes default limit is reached, the search returns the error.

We could refer to following link to fix it:

If there are any questions regarding this issue, please be free to let me know.

Best Regard,


July 26th, 2015 10:27pm

HI Sathish,

Thanks for your reply.. Sorry for the late reply.

I check the below command. 

Get-MailboxDatabaseCopyStatus | fl Content*  , the output came as healthy.

As i informed that there was some abrupt restart of the servers. When i brought exchange services up. I found that exchange do Discovery of DC in the site and outside.  For this event i was getting some error no DC found. 

Then i have restarted exchange Microsoft Active directory topology service and on the passive server, this issue resolved, after that i was getting on the active server as database context indexing failed on the active servers.  Then i restarted Microsoft Search indexer service then all shows healthy. 

But still i am getting the alerts in eventvwr . Still i didnt get any complaint from the end user that there is problem in the search.  Kindly suggest for further.



Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2015 7:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics