Exchange 2010 Search Issue Event 9842, OWA Search Fails

cloughs
cloughs used Ask the Experts™
on
Hello,

We have an Exchange 2010 SP2 Rollup 1 server running on 2008 R2 which isn't letting us search using Microsoft OWA.  We keep getting the error "The action couldn't be completed, please try again".

In PShell I have run:
Repair-ExchangeSearchSymlinks.ps1
and
ResetSearchIndex.ps1 (on each DB)

This command seems to give Time outs which I don't think is right:

[PS] E:\Exchange 2010\Scripts>Test-ExchangeSearch

Database     Server       Mailbox      ResultFound SearchTime Error
                                                   InSeconds
--------     ------       -------      ----------- ---------- -----
Mailbox D... EMAIL3       SystemMai... False       -1         Time out for test thread.
db1          EMAIL3       SystemMai... False       -1         Time out for test thread.
Partners     EMAIL3       SystemMai... False       -1         Time out for test thread.
Staff        EMAIL3       SystemMai... False       -1         Time out for test thread.


I am getting Event ID 9842 in the event logs per database for example:

Function CISearch::EcGetRowsetAndAccessor detected that content indexing was disabled for database 'Mailbox Database 1261017265' because of error '0x80041820' from MSSearch.

Also notice that the process "Microsoft.Exchange.Search.Exsearch.exe" program is stuck at 50% cpu usage and making the server run slowly.  Restarting the search service doesnt help and it was already started okay.  Rebooting also doesnt seem to fix this issue unfortunately.

I can see from google and from other questions on here that others have experienced similar, just wondered if anyone has any suggestions on how to fix the issue.

Thanks
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Kini pradeepDevelopment Manager

Commented:
what is the startup type for the Exchange search and also what is the service dependency for this service ?
Kini pradeepDevelopment Manager

Commented:
also have you tried deleting the search index and reindexing the Databases ?

Author

Commented:
Hi
The Microsoft Search Indexer is set to Automatic / status Started.
Dependencies:
Microsoft exchange active directory topology
Microsoft Search (Exchange)
-Remote Procedure Call (RPC)
--DCOM Server process launcher
--RPC Endpoint mapper


I have tried the resetsearchindex.ps1 script which I thought rebuilt the search indexes?

Thanks
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Kini pradeepDevelopment Manager

Commented:
you could try the manual option
ref: http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx

on my server I can see only Ms exchange AD topology and MS search as the dependencies.
what is the logon type?
Kini pradeepDevelopment Manager

Commented:
we are running E2K10 SP2 without any rollups

Author

Commented:
Yes MS AD Topology and MS Search are all that show for mine too, I expanded MS Search to show you what that relies on too.  I believe there is a rollup 1 out now for EX2010SP2 which we have put on the system.

Will have a go at the manual option

Author

Commented:
After manually reindexing I have different errors now

Event ID 9875
Unexpected error "DOC_TOO_HUGE: There are not enough resources to process the document or row" occurred while indexing document.
Mailbox Database: Partners
Folder ID: 1-1A0D3
Message ID: 1-460C8
Document ID: 537928
Error Code: 0x8004364a

Which states it was fixed in SP1 RU2.

http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/5f339225-b361-4256-9443-20634b63a818

We are on SP2 RU1?!

Also I have just logged into OWA to test the search and it still fails but creates this in the event log:

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

Is it getting worse?
Kini pradeepDevelopment Manager

Commented:
does this happen to mailboxes only in one database or is it for all the Databases?
Kini pradeepDevelopment Manager

Commented:
I wonder, do we have the Office filter packs installed correctly or is there any corruption.
could you please run ExBpa and let us know the result?

Author

Commented:
Im testing 2 users in different DB's and it affects both.  The test-exchangesearch shows all DB's failing to find the test message, is this normal?

Will run BPA and see what the results are now.
Kini pradeepDevelopment Manager

Commented:
No that is not normal

Author

Commented:
BPA Results
Looks like an xmas tree.  Not sure where those max incoming and outgoing sizes have come from.  Driver wise its vmware so the drivers havent been updates as such but that shouldnt cause the issue.


Warning
The Write DACL inherit (group) right for the Exchange Enterprise Servers group should be removed from the root of the domain

Network interface driver file 'c:\windows\system32\drivers\asyncmac.sys' for 'AsyncMac' on server Email3 is more than two years old. Check with your vendor to find out if a newer version is available. Installed driver details: 6.1.7600.16385 - 20090714011013.139624+060

SSL is enabled on the IIS root directory of Client Access server Email3. This will break HTTP redirection from other Client Access servers unless it is disabled.

Storage driver file 'c:\windows\system32\drivers\lsi_sas.sys' for 'LSI Adapter, SAS 3000 series, 8-port with 1068' on server Email3.clough.local is more than two years old. Check with your vendor to find out if a newer version is available. Installed driver details: 1.28.3.52 - 20090714024804.350065+060

Exchange server Email3 appears to be running as a virtual machine. Please review the system requirements detailed at http://go.microsoft.com/fwlink/?LinkId=148058.

A recommended value for the 'MinUserDc' registry entry on server 'Email3' should be between 1 and 3. As a best practice, create this registry entry to avoid overloading the PDC emulator.


Error
The maximum incoming message size is set too high. This can cause reliability problems. Current maximum message size is 53.7109375 MB.

The maximum outgoing message size is set too high. This can cause reliability problems. Current maximum message size is 53.7109375 MB.
Development Manager
Commented:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/7a4a7400-a582-4f95-9360-6d84e66e87ad

Not really sure whether this will fix it. will try and check with our MS partner tech and let you know if they have come across this kind of an issue..

Author

Commented:
I will have to do this out of hours given the reboot so will try overnight.

Thanks for your help so far

Author

Commented:
I had to run the exchange sp1 setup /prepareAD and /prepareSchema.  Rebooted and then re-ran the resetsearchindexes.ps1 script to fix the issue.  All working again now so many thanks for your help.
Kini pradeepDevelopment Manager

Commented:
Thats good news, glad to be of assistance.

Author

Commented:
It was a strange one, normally rebuilding indexes has fixed things in the past, never had to re-run the prepare scripts to fix anything exchange related before.  Still it seems to have worked and SP2 rollup 1 doesnt seem to have fixed the issue fully despite it being documented.  Thanks once again for your help.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial