olaf_joerk
asked on
Indexsearch in Exchange2010 finds only results of the last days
Hi,
I had to remove the Update-Rollup 4 of Exchange 2010 SP1 because it caused problems with the index. After removing it, I realized that if somebody searched something in Outlook or OWA only the results of the last couple of days were shown. What I did so far:
After this scripts execution nothing changed. All the other output seems to be normal.
Is this problem known to anybody? Is there a way to reset the index more "secure" than with this script?
Thanks for your Help.
Olaf
I had to remove the Update-Rollup 4 of Exchange 2010 SP1 because it caused problems with the index. After removing it, I realized that if somebody searched something in Outlook or OWA only the results of the last couple of days were shown. What I did so far:
[PS] C:\>Get-MailboxDatabase MailboxDatabase1 -status | fl *index*
IndexEnabled : True
[PS] C:\>Test-ExchangeSearch -identity f.surname -Verbose
Database Server Mailbox ResultFound SearchTime Error
InSeconds
-------- ------ ------- ----------- ---------- -----
MailboxDa... EXCHANGESERVER Surname, Firstname True 2,933
[PS] C:\>Get-MailboxDatabaseCopyStatus | Format-Table Identity,Active
DatabaseCopy,ContentIndexState -Auto
Identity ActiveDatabaseCopy ContentIndexState
-------- ------------------ -----------------
MailboxDatabase1\EXCHANGESERVER exchangeserver Healthy
[PS] C:\>.\ResetSearchIndex.ps1 -force
Der MSExchangeSearch-Dienst wurde beendet. (service stopped)
MSExchangeSearch-Dienst gestartet (service started)
After this scripts execution nothing changed. All the other output seems to be normal.
Is this problem known to anybody? Is there a way to reset the index more "secure" than with this script?
Thanks for your Help.
Olaf
ASKER
Thanks Rancy,
sorry, my fault. We already have SP2 RU2. RU3 was not recommended and RU4 caused the problem. There is RU5 released, but one had to remove RU2/1 before installation. When I read the release notes, I'm not sure if it will fix the problem. It's a production server with limited down time ... Do you think RU5 will do it? No way to reconstruct the index?
Olaf
sorry, my fault. We already have SP2 RU2. RU3 was not recommended and RU4 caused the problem. There is RU5 released, but one had to remove RU2/1 before installation. When I read the release notes, I'm not sure if it will fix the problem. It's a production server with limited down time ... Do you think RU5 will do it? No way to reconstruct the index?
Olaf
Look RU5v2 is a cumiliation of all earlier RU's so it should ideally fix those issues ..... I would still suggest to check if there is some AV on the server and we can disable and try to install RU3 on the concerned servers
- Rancy
- Rancy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
But this article only helps fine which Catalog belongs to which DB .... doesnt does anything more
- Rancy
- Rancy
ASKER
I found the solution somewhere else. May be it will help others here.
- Rancy