Our Exchange 2010 server (v14.03.0339.000, which is the latest version as of February 2017) works fine (one single exchange server in the AD), except for the search index.
Resetting the search index (
ResetSearchIndex.ps1 -Force -All, deleting the catalog folder, restarting search related services, rebooting the server etc.) didn't help, because:
Healthy after being
Crawling for a few minutes after a catalog reset. Although being
Healthy, the size of the catalog folder in the file system of the mailbox is just about 400KB (I read that the catalog size is generally supposed to be about 5-10% of the database size, which would be about 5GB in my case).
Perfmon shows 0 successfully indexed documents, while way beyond 200k documents are listed as failed.
time out for test thread. In the event log, I get
Event 9877: 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch. Error code: 0x80004005
Repair-ExchangeSearchSymLinks.ps1 and rebuilding the catalog as suggested here: https://blogs.technet.microsoft.com/exchange/2011/06/30/after-installing-exchange-2010-service-pack-1-searching-via-owa-or-outlook-online-mode-fails/ didn't help either.
Any ideas? Could
0x80004005 point towards an access denied issue?
Update: Creating a new mailbox database, moving mailboxes there and indexing yields the same error. Furthermore, I have created a new user with a mailbox, same issue here.
Unknown error code 0x80004005 for each document, and the function ends with
Error 0xe0434f4d (Unknown error (0xe0434f4d)) from cli_GetDrmFailedItems + CategoryInfo : NotSpecified: (0:Int32) [Get-FailedContentIndexDocuments], RpcException + FullyQualifiedErrorId : 5B3DED0E,Microsoft.Exchange.Management.Search.GetFailedDocuments + PSComputerName : myexchangeserver.domain.com
I tend to think that the cause must be global, maybe in Active Directory itself.
Yes, issues are related to indexing in Exchange Server. Whenever Indexing issue arise in Exchange Event Code 9877 generated with specific id details, in your case Error code 0x80004005.
Possible Resolution of the Error Code “0x80004005”
Know more about solution of error 0x80004005
User contributions licensed under CC BY-SA 3.0