A user reported they were trying to search in OWA in exchange 2010 and they are unable to.
This article is intended for Exchange administrators /IT staff not for end users. if you are a user then please contact your email support team for more assistance.
User is unable to do a simple search in search box in OWA.
The following event ID messages are logged every five minutes in the Application log:
Log Name: Application
Source: MSExchangeIS Mailbox Store
Date: 10/9/2017 11:37:44 AM
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 123456789Â
Error Code: 0x80043629
<Provider Name="MSExchangeIS Mailbox Store" />
<TimeCreated SystemTime="2017-10-09T16:37:44.000Z" />
<Data>Mailbox Database 1535770112</Data>
Log Name:Â Â Â Â Â Application
this can happen for several reasons including windows updates, improper
To resolve this issue, use the procedure described in this section.Â
run a command in shell to see if your indexing service is heathly:
look for result and your db for staus : ContentIndexState = Heathly
If it is healthy then :
Restart the following services in this order:
- Microsoft Exchange Search Indexer
- Microsoft Search (Exchange)
- Microsoft Exchange Information Store. This service may not start automatically, keep a lookout to make sure of this.
After restarting the services in this order test Outlook Web App and search should work again.
If not healthy then you should reindex the DB
Update-MailboxDatabaseCopyÂ "DB1\Server02"â€“CatalogOnlyÂ Â try running this command on offpeak hours
you may hav eot delete some files to get this to work right...
Stop the following services:
- Microsoft Exchange Search Host Controller
- Microsoft Exchange Search
The content index database will be the same folder that the database file is located in. For example, DB01 is located in F:DB01.
[PS]C:\>Get-MailboxDatabase DB01|select EdbFilePath
The content index is stored in a folder named for the GUID of the database.
Delete or rename the folderÂ xxxxxxxxx.single . Repeat the same steps to delete any other folders if you have many indexes.
Then start the services again...
The content indexes will be rebuilt, which can take quite a while to complete.
Eventually you should find that your content indexes are healthy again.
â€¢ Microsoft Exchange 2010, Microsoft Exchange 2013
courtesy of VND
http://www.vndx.com Web Solutions and custom programming including Managed Hosting Solutions
http://www.netservers.comÂ custom Hosting...introducing fast Solid State Hosting where everything is possible!