Exchange 2010 SP3 CU7 Index / Search not Indexing / no result

I Have Problemes with an Exchange 2010 Sp3 Ru7 Server. The SearchEngine does not index anything. No Database have index Data. When i went to OWA no Searchresult on Server.
I have start the resetsearchindex etc. The Microsoft-Exchange-Troubleshooters/Operational gives no error, Mailbox Repair also no error. When i start resetsearchindex the Folder in the Database Directory ist going delete an renew. Then he create 19Files but
nothing more happend.
i configure Perfmon to see activity. There i see that under MSFTESQL-ExchangeCatalog the Counter ""Batches completed w/errors 1800"
After few hours an error in Eventlog came.
Die Exchange-Suchindizierung hat die Indizierung der Postfachdatenbank Mailbox_Database_01 (GUID = b69e081c-65d8-49a9-8a82-0cdc16333380) aufgrund eines Fehlers (Microsoft.Exchange.Msfte.BatchTimeoutException: Timeout detected for batch Database Guid:b69e081c-65d8-49a9-8a82-0cdc16333380;
NumberOfFailedDocuments:0; ShouldIsolateError: False; SubmitTickCount:38475899; BatchKind:RetryMailbox; Number of entries:100) vorübergehend deaktiviert.
Anyone an Idea ?
Thanks for Help- Thomas

Hi,
Here are some suggestions, please try these to check result.
Please check to see if you are using a 3rd party disk defragmenter. If you are using this type of software, stop all the 3rd party defragmentation services temporarily.
Please check to see if the CatalogData folder is being scanned by file-level antivirus OR on-demand antivirus. If it is, reconfigure both file-level and on-demand antivirus, so it is not scanning the CatalogData folder.
Please turn up logging to expert for MSExchange Search Indexer\Configuration and MSExchange Search Indexer\General.
Please rebuild search catalog and check if event 110 is logged in the application log. Event 110 means the full crawl is completed successfully.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

Email Delivery problem from Mailman to Exchange 2010 SP3 - Invalid Character Set Name in Message Subject

Dear all,
we have a problem in the email delivery from Mailman 2.6 List Server to Exchange 2010 SP3 CU7,
related to the encoding name of the Message Subject.
The error we receive is the following:
#550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (iso8859-7) is invalid or not installed.;
cannot handle content of message with InternalId
First of all, we can notice that given an encoding name as 'iso-8859-X', it is transformed by the Mailman to 'iso8859-X' (without the first dash).
Our previous Exchange version ( Exchange 2003) didn't have any problem with this, but now,
Microsoft Exchange 2010 doesn't like the form of the encoding name without the dash,
and bounces the emails from Mailman.
The strange is that other email systems like Gmail, Yahoo accept the transformed encoding name.
Any help would be appreciated.
Kind Regards
Panagiotis Kontogiannis

Hi Panagiotis,
Base on my search, I found a similar issue which was caused by the antivirus software in exchange server.
I recommend you try to disable all the antivirus services and check if any helps.
The similar thread for you reference:
https://social.technet.microsoft.com/Forums/en-US/5bcf3098-2fe7-442f-a0bd-b720d703c6d0/problem-with-microsoft-exchange-2010-on-sbs-2011-550-560-catinvalidcontentexception?forum=exchangesvrdevelopment
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2010 SP3 and UR6 Query - Order of Install

hi,
I need to update my Exchange 2010 SP2 Servers to SP3 and Update Rollup 6.
Can someone confirm the update order for me?
I have 5 servers;
Live Data Centre:
2 x HUB / CAB (Using Windows NLB)
2 x Mailbox (DAG)
Disaster Recovery:
1 x Multi-Role Server (CAS / HUB and Mailbox) - this is also Part of the DAG
Two Questions:
1.) What is the Order in which I install SP3 on these Servers? Should it be Live Data Centre: HUB / CAS, Mailbox Servers and THEN the Multi-Role Server at DR?
2.) When Upgrading each server, should I do SP3, reboot, check and THEN install Update Rollup 6 - or should I upgrade all Servers to SP3 and then start the process again to get to Update Rollup 6?
Thanks in advance for your help with this query.
Regards,
Adam

1) Internet facing CAS first in each AD site. Order: CAS> HUB> UM> MBX
2) Personally, I would install SP3, reboot, then install SP6, but its really up to you.
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 SP3 RU5 on 2012 r2 - yei or nei

Guys, one question:
On this link:
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
I see that Exchange 2010 SP3 with RU5 is not supported on 2012 r2 and is only supported on 2012 server.
One dumb question: But what if you have 2012 r2 domain controller, can you put exchange 2010 sp3 ru5 there?
bostjanc

Ok, but even if that worked for you it doesn't mean that it is supported (because its not) and it wouldn't be a good idea to put that server in production. If your plan is to stay on Exchange 2010, then you should install it on a supported OS.
Martina Miskovic

Sharepoint 2013 vs Exchange 2010 SP3 search (Error while crawling LOB contents)

Hi there:
We are trying to solve the problem: ERROR CRAWLING LOB CONTENTS when we wish to search Exchange 2010 SP3 public folder content on Sharepoint 2013 Foundation.
Quick briefing:
Followed this instructions:
http://technet.microsoft.com/en-us/library/jj591608(v=office.15).aspx
* Created CRAWL RULE
- Used Domain Admin for content access ---> IS THIS WRONG?
- Domain Admin can access public folder thru Outlook Web Access (checked)
- Included all items in this path
PRINTSCREEN 1
* Added a content source for Exchange Server public folders
- Logged to Outlook Web Access with domain admin, expanded Public folders and opened 1st subfolder in new window and copied the address
- Logged to Outlook Web Access with domain admin, expanded Public folders and opened 2nd subfolder in new window and copied the address
PRINTSCREEN2
* Did a FULL CRAWL
PROBLEM:
- Search results does not throw "correct data". Some items are not being found
CRAWL LOG is reporting: Error while crawling LOB contents
Detailed error message:
https://mail.domain.com/OWA/?ae=Folder&id=PSF.LgAAAAAaRHOQqmYRzZvIAKoAL8RaAwAnt2ed15IATLg8XoXLNj4EAAAAXsN8AAAB&t=IPF.Note
Error while crawling LOB contents.
Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException
The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..:
System.InvalidOperationException An internal server error occurred.
Try again later.; SearchID = 4E8542D3-48EF-404E-8025-8D9AAEFE777A )
We thought it's a throttling issue / found possible solution:
http://powersearching.wordpress.com/2013/07/23/exchange-public-folders-search-fail-error-while-crawling-lob-contents/
Tried it, still same Error messages, problem not resolved.
Any hints? Please advise.
With best regards
bostjanc

Hi Bostjan,
From the error message, the issue might be caused by throttling policy on Exchange side. And the article you posted provides the right solution, some modification to the solution and please try again.
For throttling policy part
1.Execute the command for Set-ThrottlingPolicy
Set-ThrottlingPolicy SharePoint -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited
2.Execute the command Get-ThrottlingPolicy SharePoint to double confirm the policy setting has been successfully executed
For registry key part
1. Start Registry Editor (regedit).
2. Navigate to the following registry subkey:
\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. Right-click ParametersSystem, point to New, and then click Key.
A new key is created in the console tree.
4. Rename the key MaxObjsPerMapiSession, and then press Enter.
5. Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value.
The new value is created in the result pane.
6. Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
7. Right-click the newly created key, and then click Modify.
8. In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
9. Restart the Microsoft Exchange Information Store service.
If it still doesn’t help, please check ULS log for related error message.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

Hi,
We have an issue with our OWA page. We are currently publishing OWA via UAG.
We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7. Since the upgrade, we are keep getting the following error after entering our credentials on the login page. I've tried with every possible browser.
You do not have permissions to view this folder or page
Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues. I can see this on the Active Sessions screen
on Web Monitor.
I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running.
No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer.
Any insight would be helpful? I'm assuming something changed on the Exchange side after the upgrade.
Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
UAG > SP4
TMG > SP2 Rollup 5

I've found a solution; UAG requires Basic Authentication over OWA. For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
http://technet.microsoft.com/en-us/library/ee921443.aspx
Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue. Though beware, you
have do this on all your Client Access servers.

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

Outlook 2013 Category view not updating after Exchange 2010 SP3 RU3

After updating to Exchange 2010 SP3 RU3 last night, users who use categories view in Outlook 2013 are complaining that the view does not update. The alert is received in the notification area and the unread message count next to Inbox updates appropriately.
The view can be force updated by switching between All and Unread, by using Reset View, or closing and opening Outlook. It seems anything that forces a 'redraw' of the view will update it - except for the actual reception of email. I easily replicated
this issue. For reference:
Exchange 2010 SP3 RU3
Windows 7 x64 Ent
Outlook 2013 (15.0.4551.1004) 32-bit
I do see that SP3 RU4 has been released, however the only change listed is a security patch.
Thank you for any ideas.

Hi, Everyone –
This has been a known issue for a very long time – we have people at our workplace that are very disappointed since a feature as great as categorizing email (not using tasks) has become broken and has not even been considered to be fixed for
over half a year. It was not fixed in the updates for Patch Tuesday this week.
I would like to confirm that this is an issue with Outlook 2010 and 2013 when running the latest Exchange 2010 and there is NO FIX
– I have scoured the internet for a solution – all proposed "textbook" solutions do not work and I am positive that the issue can be recreated; however, everyone from Microsoft does not mention trying to recreate the issue at all.
The workaround of creating a rule to send new emails to a category could break other pre-existing rules and cause more frustration and wasted time for users/IT before and after the issue is fixed.
Please fix this issue sooner than later, as the Categories view is completely broken and unusable at this point in time.
Regards,
IT Helper

Active Sync Not Working for NEXUS MOBILE in Exchange 2010 SP3 Enivironment..

HI Exchange Techy's.
We have Exchange 2010 SP3 Servers. Now All mobiles are working fine Through Active Sync Except Google Nexus.
Problem: Account has been activated successfully in Mobile, But Mails are not synchronized.
Kindly help fix me out of this problem.
We are welcome & Appreciate who are giving Comments & Solutions for this problem.
Regards,
One of your Exchange Person
B@[email protected]

Hi,
I'd recommend asking your question over here:
https://social.technet.microsoft.com/Forums/en-us/home?forum=exchangesvrmobilitylegacy&filter=alltypes&sort=lastpostdesc
This forum is meant for feedback on the TechNet website/subscriptions, not product support.
Good luck.
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

Exchange 2010 SP3 RU7 - additionals mailboxes does not refresh automatically

Hello
On Exchange 2010 SP3 RU7 , my additionals mailboxes does not refresh automatically (Outlook 2010 up-to-date).
i need to perform "send/receive" and "update the folder" to get the mail.
Primary mailbox is running correctly and new mails are displayed .
Thanks

Hi,
Based on the description, you added additional mailboxes from Outlook, but messges sent to these additional mailboxes didn't show until you tried the option "update the folder".
How many additional mailboxes did you add?
Did this issue affect all users?
If possible, please remove these additional mailboxes and then re-add them. I recommend you add one additional mailbox first to check if the issue occurs. Then you can add another additional mailbox to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 SP3 - RU3 RU4 Public Folders issues ( not refreshing ) when grouping by Categories for "(None)" Group

After installing Exchange 2010 SP3 RU3, I had an issue in Public Folders, once having group by categories in Outlook, the Group of "(None)" categories is not refreshing when changing flag... I also installed RU4 but nothing changed, any reason
Thx

Hi,
From your description, the group with none categories won’t fresh when changing flag in Category view. If I misunderstood, please point it out.
As you can in the View tab as below, there is Category as well as Flag: Start date or Due Date. It means that grouping per color categories is more or less different from that
grouping by flag.
Should you need more assistance, feel free to tell me.
Regards,
Rebecca Tu
TechNet Community Support

Exchange 2010 SP3 Rollup 7 not showing right version

I have installed Rollup 7. I can see it in programs installed / updates
but when I check the version number via the shell or console it show the number corresponding to sp3 no rollups
tried to re install rollup7, but it fails

There is:
Update Rollup 8 for Exchange Server 2010 SP2,
and Update Rollup 8 for Exchange Server 2010 SP1
But, as far as I know, there is no Update Rollup 8 for Exchange Server 2010
SP3 yet.
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
That's correct Idan. Exchange 2010 SP3 RU7 is the latest - released in August this year:
http://blogs.technet.com/b/rmilne/archive/2014/08/26/exchange-2010-sp3-ru7-released.aspx
Just like in Exchange 2003 & 2007 only service packs increment the version # you see in the management console and shell. Check the exsetup file as mentioned in the first post Idan linked.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

The Test-OrganizationRelationship function on Exchange 2010 SP3 Rollup4 error

Hi
If I run Test-OrganizationRelationship function on Exchange 2010 SP3 Rollup4 the fallowing error appear:
[PS] C:\WINDOWS\system32>Test-OrganizationRelationship -Identity "emag" -UserIdentity [email protected] -verbose
VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Active Directory session settings for
'Test-OrganizationRelationship' are: View Entire Forest: 'False', Default Scope: 'hq.flanco.ro', Configuration Domain
Controller: 'CALYPSO.hq.flanco.ro', Preferred Global Catalog: 'CALYPSO.hq.flanco.ro', Preferred Domain Controllers: '{
CALYPSO.hq.flanco.ro }'
VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Runspace context: Executing user: hq.flanco.ro/FLANCO -
Users/HQ/IT/Marian NICA, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Beginning processing &
VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Instantiating handler with index 0 for cmdlet extension
agent "Admin Audit Log Agent".
VERBOSE: [12:24:44.391 GMT] Test-OrganizationRelationship : Current ScopeSet is: { Recipient Read Scope: {{, }},
Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive
Recipient Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [12:24:44.391 GMT] Test-OrganizationRelationship : Searching objects "[email protected]" of type "ADUser"
under the root "$null".
VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Previous operation run on global catalog server
'CALYPSO.hq.flanco.ro'.
VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Searching objects "emag" of type "OrganizationRelationship"
under the root "$null".
VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Previous operation run on domain controller
'CALYPSO.hq.flanco.ro'.
VERBOSE: Test that organization relationships are properly configured.
VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Resolved current organization: .
VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Calling the Microsoft Exchange Autodiscover service for the
remote federation information.
VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
https://autodiscover.emag.ro/autodiscover/autodiscover.svc.
VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
https://autodiscover.emag.ro/autodiscover/autodiscover.svc.
VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : Generating delegation token for user [email protected]
for application FYDIBOHF25SPDLT.exchangedelegation.emag.ro.
VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The delegation token was successfully generated.
VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service is being called
to determine the remote organization relationship settings.
VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The Client will call the Microsoft Exchange Autodiscover
service using the following URL: https://autodiscover.emag.ro/autodiscover/autodiscover.svc/WSSecurity.
VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service failed to be
called at 'https://autodiscover.emag.ro/autodiscover/autodiscover.svc/WSSecurity' because the following error occurred:
SoapException.Code =
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd:InvalidSecurityToken
Exception:
System.Web.Services.Protocols.SoapHeaderException: An error occurred when processing the security tokens in the
message.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse
response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.Exchange.SoapWebClient.CustomSoapHttpClientProtocol.<>c__DisplayClass4.<Invoke>b__3()
   at
Microsoft.Exchange.SoapWebClient.HttpAuthenticator.NoHttpAuthenticator.AuthenticateAndExecute[T](SoapHttpClientProtocol
client, AuthenticateAndExecuteHandler`1 handler)
   at Microsoft.Exchange.SoapWebClient.SoapHttpClientAuthenticator.AuthenticateAndExecute[T](SoapHttpClientProtocol
client, AuthenticateAndExecuteHandler`1 handler)
   at
Microsoft.Exchange.SoapWebClient.AutoDiscover.DefaultBinding_Autodiscover.GetOrganizationRelationshipSettings(GetOrgani
zationRelationshipSettingsRequest Request)
   at
Microsoft.Exchange.Management.Sharing.TestOrganizationRelationship.<>c__DisplayClass8.<GetInvokeDelegate>b__7(DefaultBi
nding_Autodiscover binding)
   at
Microsoft.Exchange.SoapWebClient.AutodiscoverClient.<>c__DisplayClassf.<InvokeAndFollowSecureRedirects>b__c(IWebProxy
webProxy)
   at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeWithWebProxy(String url, InvokeWithWebProxyDelegate
invokeWithWebProxy)
   at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeAndFollowSecureRedirects(InvokeDelegate invokeDelegate,
Uri url)
   at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeForUrl(InvokeDelegate invokeDelegate, Uri url)
VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : The Autodiscover call failed.
RunspaceId : b3b378f5-d912-4042-b578-e949b54da4c1
Identity    :
Id          : AutodiscoverServiceCallFailed
Status      : Error
Description : The Autodiscover call failed.
IsValid     : True
VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : Ending processing &


It's not this, is it -
http://johanveldhuis.nl/en/error-occurred-processing-security-tokens-message/ ?

Event ID 9877, Exchange 2010 SP3 RU4

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

Hi Deb,
We're getting the same error as you on Exchange 2010. We have exchange 2010 and exchange 2013 running in a coexisting environment. Since we applied Service Pack 1 for Exchange 2013, we've had nothing but issues!
I've tried the rebuild of the index catalogues by following these instructions:
http://ghousewin.blogspot.in/2012/08/not-able-to-search-in-owa-event-id-9877.html
This failed to resolve the issues too. We've rebooted the server, restarted all the search services and still nothing! We're pulling our hair out here!
The only thing I haven't tried is the prepareAD commands in this post:
http://social.technet.microsoft.com/Forums/exchange/en-US/7a4a7400-a582-4f95-9360-6d84e66e87ad/ex2010-2node-dag-search-in-owa-not-working-caused-by-eventid-9877-content-indexing-function
I'm unable to try this during the day as we have no testing
environment and would hate to mess the production environment up if this went wrong.
If you're able to try this during the day, would you let us know how it goes?
Many thanks,
Stephen

Exchange 2010 SP3 (CU

Exchange 2010 SP3 with Update ROllup 8-v2
Event Viewer/APP contains a lot of this errors:
Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: Production Databases
Error Code: 0x80041606
We have tried with runing: C:\Program Files\Microsoft\Exchange Server\V14\Scripts\ResetSearchIndex.ps1 on Exchaneg server and restarting Information Store, but errors still appear.
Any hints how to fix this error?
With best regards
bostjanc

Hi,
Basically there's a problem with the catalog data for the database, we need to recreate it. Please try the following method first to check this issue.
On the Exchange server that's hosting the database that's giving you the error. Start > In the search/run box type services.msc {enter} > Locate the Microsoft Exchange Search Indexer Service and stop it.
Navigate to the folder that holds the problem Database (By default, the path is: C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database). Within the folder you will find another folder called CatalogData-xxxxxxxxxxxxxxxxxx > Delete this
folder.
Then restart the Microsoft Exchange Search Indexer Service.
The catalog will now rebuild.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Exchange 2010 SP3 CU7 Index / Search not Indexing / no result

Similar Messages

Maybe you are looking for