To resolve this issue, install the following update rollup:
2608656 Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3
Important 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:
322756 How to back up and restore the registry in Windows
After you install the update rollup, follow these steps to set the maximum number of query restriction nodes.
Note We recommend a start value of 1,000,000 (decimal):
- In the Application log on the Exchange Server 2007 mailbox server, note how many times Event ID 1025 together with error code 0x80041606 occurred in the past month. This information will be used as a baseline to determine whether the MaxRestrictionNodes setting reduces or eliminates the issue.
- Click Start, type regedit in the Start Search box, and then press Enter.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExSearch
- Click Edit, point to New, and then click Key.
- Type MaxRestrictionNodes, and then press Enter.
- Click MaxRestrictionNodes, click Edit, select New, and then click DWORD (32-bit) Value.
- Type Server, and then press Enter.
Note The registry entry should resemble the following:
Key Name:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExSearch\MaxRestrictionNodes
Value Name: Server
Value Type: REG_DWORD - Click Server, click Edit, and then click Modify.
- In the Value data field, type 1000000 (Decimal).
Note The registry entry should resemble the following:
Key Name:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExSearch\MaxRestrictionNodes
Value Name: Server
Value Type: REG_DWORD
Value Data: 1000000 (Decimal) - Exit Registry Editor.
- Restart the Microsoft Exchange Search Indexer service.
Notes- After you restart the Microsoft Exchange Search Indexer service, check the Application log for the following event IDs:
- Event ID 130: Failed to convert the MailboxDB Guid read in from under the MaxRestrictionNodes registry key to a GUID
- Event ID 131: Failed to open the MaxRestrictionNodes registry key
- Event ID 132: Failed to set the MaxRestrictionNodes property in the indexer
- If you are receiving any of these events, you may have entered the registry key or the DWORD value incorrectly. Or, you may not have spelled the new key or DWORD value correctly. Make the necessary corrections, and then restart the Microsoft Exchange Search Indexer Service. Search for any new instances of event IDs 130, 131, or 132.
- Check the Application log either weekly or monthly based on the number of event ID 1025 messages that have error 0x80041606 in the Application log.
- If you are still receiving a significant number of these events, you can increase the value incrementally to 2000000 (Decimal).
- Do not increase the value beyond 2000000 (Decimal) without explicit direction from a Microsoft Support Engineer because doing this may reduce server performance.