• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3134
  • Last Modified:

Keep getting index errors on Exchange 2010 server

I'm seeing repeated errors in the event log on my 2010 exchange server:

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

This appears for each of the 4 databases I have every 10 minutes or so.  I've done the following which worked for a day but it showed back up again this morning:

Run Repair-ExchangeSearchSymlinks.ps1
Run .\ResetSearchIndex.ps1 -force 2010_DB3

Any ideas on what the root cause of this is and how I can prevent it?
0
First Last
Asked:
First Last
1 Solution
 
SreRajCommented:
Hi,

As per Microsoft this error is logged because Exchange Search has a hard-coded prefix search limit of 200,000 nodes for a single character search. They are saying this is fixed in Update Rollup 6 for Exchange Server 2010 Service Pack 1. Do you have it already in your environment?

SP1 Rollup 6 - http://support.microsoft.com/kb/2608646

Details regarding this error can be found at http://support.microsoft.com/kb/2616127
0
 
First LastAuthor Commented:
I am fully patched as of today, I did that rollup back when it came out.  The odd thing is this wasn't always a problem, only in the last couple of weeks.  I can't figure out what has changed.
0
 
Blue Street TechLast KnightsCommented:
Hi danbrown1888.

Rerun the schema upgrades for SP1 (using the sp1 setup files...) and restart the exchange services. After that, search should work as intended again.

Also, check 'Microsoft Search (Exchange)' service on Client Access Servers is NOT set to 'Manual' and not running. Start and set to Automatic.

Did you execute your remediation per this article? http://blogs.technet.com/b/exchange/archive/2011/06/30/after-installing-exchange-2010-service-pack-1-searching-via-owa-or-outlook-online-mode-fails.aspx
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
SreRajCommented:
You could try manually rebuilding the Full-Text Index Catalog. To manually rebuild the full-text index catalog, stop the Microsoft Exchange Search Service, delete the old catalog, and then restart the service. This procedure forces the server to re-create the full-text index catalog.
Following are the procedure to manually re-create index catalog.

1.Stop the Microsoft Exchange Search Service by running the command: Net Stop MsExchangeSearch
2.Delete the full-text index catalog directory
The directory name of index catalog follows the convention CatalogData-<guid>-<guid> where the first <guid> is the GUID of the database, and the second <guid> represents the Instance GUID, which is used on a clustered mailbox server to distinguish between the nodes. Example for an index catalog is ‘CatalogData-b56624f3-bf19-4463-926f-d4705ac3dd08-cc64dd2d-2428-4f12-bba2-79d6d34c4d27’. Delete this folder.
3.Start the Microsoft Exchange Search Service by running the command: Net Start MsExchangeSearch

Following screenshot shows how you can locate the CatalogData folder.

CatalogData Folder
0
 
First LastAuthor Commented:
@diverseit - I can try that, do you know if it would cause any issues since I'm already on SP3?  This is a two member DAG so I assume it should be done on both sides.

@SreRaj - I've run Repair-ExchangeSearchSymlinks.ps1 and .\ResetSearchIndex.ps1 [-force] <dbname> [<dbname>] which seems to help for a short time but the error always comes back.  Will doing it the manual way you suggest be different than using the scripts?

Of the two options here is there a consensus on which approach might work best?  I'd lean towards manually deleting/rebuilding the index if its likely to work.
0
 
SreRajCommented:
Running ‘.\ResetSearchIndex.ps1 -force 2010_DB3’ is same as manually deleting and re-creating catalog folder. If there is a DAG copy for the database, then you should update the content index for the copy using the following command.

Update-MailboxDatabaseCopy -Identity <DBCopyName>\<DBCopyServerName> -SourceServer <SourceServerName> -CatalogOnly

Also, it is specified in the following thread that restarting ‘Microsoft Exchange Information Store’ too fixes this problem.

http://social.technet.microsoft.com/Forums/exchange/en-US/bded36b7-8fa1-42ab-9303-5b3f38d95a27/owa-search-issue
1
 
First LastAuthor Commented:
Hi SreRaj

I think you may have something with the updatemailboxcopy command, that's one thing I haven't tried yet.  It is a two member DAG so I'll try running that command after hours this week and see how we do, thanks!
0
 
First LastAuthor Commented:
This was resolved by reinstalling the filter pack, there must have been some kind of problem when it was updated during SP2.
0
 
First LastAuthor Commented:
Found own solution
0
 
Senior IT System EngineerIT ProfessionalCommented:
First,

Where did you download th Filter pack that is not comaptible with the Exchange Server 2010 SP3 ?
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now