Hi Forum Members, we drive a 2 node Exchange 2010 DAG, with all the latest updates (up to Updaterollup 3v3) installed. I´m stuck in a painfull situation, in which users started to complain about, that the search in OWA wasn´t working. I´ve tried to verify this - but it was working for my account. A look into the eventlog brought up this event ID 9877 – Source MSExchangeIS Mailbox Store Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch. Mailbox Database: DB019 Error Code: 0x80043629 This Event shows up for all Databases mounted on MBx1. All Databases mounted on MBx2 aren´t affected. What i tried allready: Found on article realted to this EventId (http://www.eventid.net/display.asp?eventid=9877&eventno=10771&source=MSExchangeIS%20Mailbox%20Store&phase=1) , started that on their Microsoft Search (Exchange) on the Cas Servers was set to manually and not running. This is the same here - started them - but that didn´t change anything. On MBx1 Restarted MSExchange Search / Indexer >Update-MailboxDatabaseCopy -Identity "DB019\MBx1" -CatalogOnly -> Error remains For an user loacted in an affected Database issued Test-ExchangeSearch -mailbox user Result: Database Server Mailbox ResultFound SearchTime Error InSeconds -------- ------ ------- ----------- ---------- ----- DB0xx MBx1... user... False -1 Time out for test thread If i check the Contentindexstate with the Get-MailboxdatabasecopyStatus CMDlet, it reports that all Indexes are Healthy! Now I’m stuck within the issue and did not find any solutions, related to that error behavior. Someone else experiences such problems? Any Help / suggestion is appreciated! best regards Markus

Hi It is known bug. Many users try difference ways to solve it. 1. first - setup /PrepareAD second setup /PrepareSchema reboot after it's done. 2. Restart Ms search service 3. It is said that it will be fixed by exchange 2010 sp2. As far as I know, exchange 2010 Sp1 RU4 will be released in July or August. You can read this thread and communicate with them . http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/25373135-2143-49b8-ae16-b7e711c554ecPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Terence, sorry for replying late but i have to disagree that not all the point you´ve mentioned were the solution at our end. i didn´t run /prepareAD / PrepareSchema nor any other specific tasks as discussed within the link threat you´ve included. What i did was: - Start Microsoft Search (Exchange) on both CAS Servers + set startuptype to Automatic - did not show any effect after service startup - installed June Patchday Updates on All Exchange Servers - Rebooted them - The error was gone Search is working again for all databases! So im not 100% sure, if the Service Change was the solution - or the simple Reboot. my 2 cents. Br, markus

Hi Thanks to share your experience. Maybe Reboot is the way to solve the problem.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.