none
Event 9877, MSExchangeISMailbox Store

    Question

  • Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.

    Mailbox Database: MDB01

    Error Code: 0x80041606

    Wednesday, December 08, 2010 9:19 PM

All replies

  • i am recieing the 2 previous errors on my exchange 2010 SP1 box. i did some research and have narrowed it down to a bug in SP1 based on some blog posts. i was wondering if anyone has found a resolution for the error.
    Thursday, December 09, 2010 2:57 AM
  • Just letting you nkow I'm in the same boat... running exchange 2010 SP1 w/ UR 1. Getting these errors

     

    Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
    Mailbox Database: SATA1_MailboxDB
    Error Code: 0x80041606

    Thursday, December 09, 2010 8:16 PM
  • yea microsoft has a fix but is not realeased to the public...hoepfully they will see this post and send it.
    Thursday, December 09, 2010 10:05 PM
  • Hi,

     

    Regarding your question, I would like to explain that this is a known issue and it is still active now.

     

    Based on my research, this issue can be fixed after disabling IPv6,TCPChimney, RSS, and TCPA, we can take the following steps to check the result. If the issue still exists, we may have to wait for Hotfix’s response.

     

    Step 1:     Disable IPv6 on all the servers:

    a.       Open Registry Editor.

    b.      Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

    c.        In the details pane, click New, and then click DWORD (32-bit) Value.

    d.      Type DisabledComponents, and then press ENTER.

    e.      Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.  

     

    NOTE: The 0xffffffff value or the 4294967295 value disables all IPv6 components except for the IPv6 loopback interface.

     

    Step 2: Disable TCPChimney, RSS and TCPA on all the servers

              a.       Click Start, click Run, type regedit, and then click OK.

              b.       Locate the following registry subkey:

              HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

              c.       Right-click EnableTCPChimney, and then click Modify.

              d.       In the Value data box, type 0, and then click OK.

              e.       Right-click EnableRSS, and then click Modify.

              f.       In the Value data box, type 0, and then click OK.

              g.       Right-click EnableTCPA, and then click Modify.

              h.       In the Value data box, type 0, and then click OK.

              i.       Exit Registry Editor, and then restart the computer.

     

    NOTE: If the value of the EnableTCPChimney registry entry has been set to 1, the TCP Chimney functionality is enabled. For the same reason, if the values of the EnableRSS and EnableTCPA registry entries have been set to 1, the RSS functionality and the TCPA functionality are enabled.

     

    Best Regards,

     

    Evan

    Wednesday, December 15, 2010 7:31 AM
    Moderator
  • Hi,

    We've got the same issue, is this fixed with Exchange 2010 SP1 Update Rollup 2 or will this be included in a later Rollup?

    Remco

    Sunday, December 19, 2010 11:03 AM
  • Hi Evan,

    Do you know if there are existing cases? there is the same problem in the german forum. I´d direct the op to ms pss, but it should help more if there is already a case number. Or can you tell me something about the timeframe you expect a hotfix?


    Viele Grüße Walter Steinsdorfer MVP Exchange Server http://msmvps.com/blogs/wstein/
    Monday, January 10, 2011 4:52 PM
  • I don't have a case open, but I'm eagerly awaiting the fix. I can tell everyone that UR2 did not fix the issue.
    Monday, January 10, 2011 4:54 PM
  • Hi,

    Evan wrote: "explain that this is a known issue and it is still active now."

    Someone must know that and there must be an open case.

    just my 2 Cents.


    Viele Grüße Walter Steinsdorfer MVP Exchange Server http://msmvps.com/blogs/wstein/
    Monday, January 10, 2011 5:02 PM
  • Evan,

    Hope this reply is seen - by chance if I do what you state above - will this have any adverse effect on the DAG

    I was working with MS Tier 2 on a DAG issue and they said to not disable IPv6 functionality, even though we are not using it. 

     

    Thanks

     

    SJMP

    Tuesday, April 12, 2011 9:02 PM
  • We had the same problem "Event IDs 9877 w.0x80041606" and it wasn't solved until deployed RU4v2

    Working together with Microsoft on this case, we got out that clients using Windows XP and Outlook 2010 Instant Search in online mode are causing the problem (no Desktop Search installed).

    The good news is that the fix is part of Exchange 2010 SP1 RU4v2 and solved the issue in 99% of the cases.
    We applied RU4v2 in production environment and it removed nearly all of the Event IDs 9877 w.0x80041606 from the application log so far.

    Hope that helps,
    Klaus

    PS: In the meantime Microsoft released RU5


    Thursday, August 25, 2011 6:30 AM
  • yea microsoft has a fix but is not realeased to the public...hoepfully they will see this post and send it.


    Hi,

    Try out this and the issue is fixed

    Released: Update Rollup 5 for Exchange 2010 SP1

    Earlier today the Exchange <acronym>CXP</acronym> team released Update Rollup 5 for Exchange Server 2010 SP1 to the Download Center.

    This update contains a number of customer-reported and internally found issues since the release of RU1. See 'KB 2582113: Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1' for more details. We want to let you know this rollup contains the Exchange 2010 SP1 version of the change described in this KB article:

    2543879

     


    Mihir Nayak
    • Proposed as answer by Abhinav Aneja Thursday, August 25, 2011 7:27 AM
    Thursday, August 25, 2011 6:35 AM
  • yea microsoft has a fix but is not realeased to the public...hoepfully they will see this post and send it.


    Hi,

    Try out this and the issue is fixed

    Released: Update Rollup 5 for Exchange 2010 SP1

    Earlier today the Exchange <acronym>CXP</acronym> team released Update Rollup 5 for Exchange Server 2010 SP1 to the Download Center.

    This update contains a number of customer-reported and internally found issues since the release of RU1. See 'KB 2582113: Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1' for more details. We want to let you know this rollup contains the Exchange 2010 SP1 version of the change described in this KB article:

    2543879

     


    Mihir Nayak

    Agree with mihir.

    RU5 have been launched. you can go for it


    --------Abhi----------------- Exchange Specialist------------- ------------------ Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Abhinav Aneja Thursday, August 25, 2011 7:27 AM
    Thursday, August 25, 2011 7:27 AM
  • Hi,

     

    We're running SP1 wit RU4v2, still having this issue.

    Can someone confirm that it will be solved with RU5?

    I read that it would be fixed with RU4, but still isn't though.

     

    Thursday, September 01, 2011 8:45 AM
  • Hi Peter,

    RU5 will not solve the error 100%.

    We also still get the events Event ID 9877 w. 0x80041606 in the application log, but not as often as before we installed RU4V2, so we contacted Microsoft Support Team again. Here is the answer:

    CAUSE: The error has something to do with a 
    limit for single digit searching as a prefix per database using MSSearch 3.0. Under special circuminstances this limit is reached by a search request, the search will fail and you will receive Error 0x80041606 in the application log.

     

    RESOLUTION: Installing Exchange 2010 SP1 RU4 v2 should solve 90% of the Event ID 9877 w. 0x80041606. If you are still receiving Event ID 9877 w. 0x80041606, then either wait for a fix in Exchange 2010 SP1 RU6 or obtain an Interim Update for RU5. RU6 will contain a possibility to take influence on the default limit by increasing it step by step as far as the error will not occur any more.

    By the way: We get this error only about 10 times per day, so we are very happy that we installed RU4V2 which reduced the events so far.

    Klaus

     



    Thursday, September 01, 2011 11:34 AM