Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 8719

Event ID 9877, Exchange 2010 SP3 RU4

$
0
0

On 2/19 I installed RU4 for Exchange 2010 SP3 on a server at a client's site.  This is a single server with all the roles on it, with about 40-45 mailboxes. Ever since then, during the busiest hours of the day (around 7AM to 5:30PM or so), I get the following event log error on this server:

Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          2/20/2014 6:58:49 AM
Event ID:      9877
Task Category: Content Indexing
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: Mailbox Database 0784353824
Error Code: 0x80043629
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeIS Mailbox Store" />
    <EventID Qualifiers="49198">9877</EventID>
    <Level>2</Level>
    <Task>46</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-20T11:58:49.000000000Z" />
    <EventRecordID>423922</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>CISearch::EcGetRowsetAndAccessor</Data>
    <Data>Mailbox Database 0784353824</Data>
    <Data>0x80043629</Data>
    <Binary>5B444941475F4354585D00000E020000FFC8070000000000000300020000EBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C710100000008085C710100000008085C7101000000080BDCC101000000C00D4224010E7FAFFFFEBD410101B0000008B3B4010E7FAFFFFEBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C710100000008085C710100000008085C7101000000080BDCC101000000C00D4224010E7FAFFFFEBD410101B0000008B3B4010E7FAFFFFEBF410101B000000F7991010000000008B304010E7FAFFFFEBB410101B0000006DA74010E7FAFFFF6DE74010E7FAFFFF85C7101000000080D25560200F01048040008F6600000C00D25560200F01048040008F661B000000AD0C4010BFF9FFFFE3D400101B00000029D14010E7FAFFFFADC34010E7FAFFFF53BD00101B000000D25560200F01048040008F66E7FAFFFFD25560200F01048040008F6600000080D25560200F01048040008F6600000C00C5C14010EE030000715D4010EC030000D25560200F0104800B00AA671B000000543760201DFAFFFF0B005C0EE7FAFFFFD42160200F0104800B005C0EE7FAFFFFD25560200F0104800B005C0E00000080D25560200F01048040008F660000008023C3001000000C0023FC4010370A0000D25560200F01048040008F66E7FAFFFF</Binary>
  </EventData>
</Event>

The frequency of these errors varies and it definitely seems to be related to the amount of traffic. Over the weekend it only occured about 5-10 times a day.  For the past couple of days, it's been pretty constant about every 15 minutes or so all day.

I've looked this up, but I've only found a few posts mentioning similar errors, all relating to earlier versions of Exchange 2010. Supposedly this problem was fixed in one of the rollups to SP1 or SP2, I think.  I never saw these errors, though, until the SP3 RU4 rollup.  I haven't heard any complaints from users, but I'm concerned that this might escalate and start causing noticeable searching issues.

Any ideas would be appreciated.


Deb


Viewing all articles
Browse latest Browse all 8719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>