Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Event ID 9877 with error code "0x80041606" when you use Outlook in online mode to search for a keyword in Exchange Server 2010
Article ID: 2616127 - View products that this article applies to.
Consider the following scenario. By default, Exchange Search is enabled for a mailbox database in a Microsoft Exchange Server 2010 environment. You use Microsoft Outlook in online mode to search a mailbox for a keyword or phrase that contains a single letter or a single digit. In this scenario, you receive the following error message even though there are matches for the keyword in the mailbox:
No matches found for "keyword".Additionally, the following event is logged in the Application log:
NOTE: 0x80041606 = QUERY_E_TOOCOMPLEX
Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 9877
Task Category: Content Indexing
Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: Mailbox Database
Error Code: 0x80041606
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.
Note The most common way to reach the 200,000 nodes limit is to search for a word or phrase that contains a single digit or letter. There are also other less common causes, such as entering very complex searches with many ANDs, Ors, and NOTs. Additionally, complex combinations of date ranges and search terms, many entries in the To and From fields, or a combination of all these things may cause the limit to be reached.
To resolve this issue, install the following update rollup:
2608646Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2608646/ )Description of Update Rollup 6 for Exchange Server 2010 Service Pack 1
322756After you install the update rollup, to have us set the maximum number of query restriction nodes to 1,000,000 for you, go to the "Fix it for me" section. If you prefer to set the maximum number of query restriction nodes yourself, go to the "Let me fix it myself" section.
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Fix it for me
To set the maximum number of query restriction nodes automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.
Fix this problem
Microsoft Fix it 50810
Then, go to the "Did this fix the problem?" section.
Let me fix it myselfAfter you install the update rollup, follow these steps to set the maximum number of query restriction nodes to 1,000,000 (decimal):
Did this fix the problem?
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about Exchange Search, visit the following Microsoft website:
General information about Exchange SearchFor more information about how to disable or enable Exchange Search, visit the following Microsoft website:
General information about how to disable or enable Exchange SearchFor more information about the MaxRestrictionNodes entry, visit the following Microsoft website:
General information about the MaxRestrictionNodes entry
Article ID: 2616127 - Last Review: January 4, 2012 - Revision: 4.0