none
OWA Search not working - Exchange 2007 Indexing Service Issue RRS feed

  • Question

  • Morning Gents,

    Exchange Server 2007 (SP3 on CAS and HUB and SP3 on MBX cluster)

     

    I am having a few issues with the Exchange 2007 Indexing Service.

     

    It all started when I tried to use the search functionality in OWA. I go the following message;

     

    Search results may take a long time to appear because Microsoft Exchange Search is unavailable. Results will not include matches in the e-mail body.

     

    After some searching on Technet, I found the page about using the powershell script:

    ResetSearchIndex.ps1 -force –all

     

    Before I ran the script (on a single database) I wanted to see the status of the crawl in perfmon. I realized that crawl was currently running

    (Add this counter to Perfmon: MSExchange Search Indices\Full Crawl Mode Status. This counter will be 0 before running ResetSearchIndex, go to 1 during the full crawl and then back to 0 after ResetSearchIndex completes.

    So I stopped the MSExchange Search Indexer Service and started it.

     

    I saw all the counters for each database drop from 1 to 0 when the service was stopped.

     

    When the service was started I saw the following messages in the event log for each DB;

    Source: MSExchange Search Indexer    Event ID: 113

    The search index files for Mailbox Database Storage Group X\Mailbox Database X (GUID = xxxxxxxxxxxxxxxxxxxxxxxxxxx) are invalid. They will be deleted and recreated in 30 minutes or soon after the Microsoft Exchange Search Indexer service is restarted.

    After a minute or so, the perfmon counters went back to 1 indicating that a crawl had started.

     

    30 minutes after the 113 event, I saw the following Event’s for each of the DB’s;

    Source: MSFTESQL-Exchange        Event ID: 4133

    Component: MicrosoftIndexer

    Very low disk space was detected for catalog ExSearch-bc4ca191-34c5-4eb1-993b-ca0057254421-cc64dd2d-2428-4f12-bba2-79d6d34c4d27. Please free up some disk space so that indexing can continue.

    OWA search still does not work, and now to boot my perfmon graphs don’t populate with any info ( I can add counters, but the default 4 graphs, CPU, Disk, n/w, memory) are all empty.

     

    Any suggestions?

     

    Thank you in advance

     

     

    Friday, December 2, 2011 7:23 PM

Answers

  • Hello,

     

    You may need to increase the size of the mount point drives M: to resolve this problem. If something does occur at the root of the mount point and start to fill it up, indexing will stop on the databases under the mount point even though they still have more than sufficient room to continue indexing.

     

    Thanks,

    Simon Wu

    Exchange Forum Support

     

    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 tnmff@microsoft.com.

     

     

     

    Monday, December 5, 2011 9:17 AM
    Moderator

All replies

  • Hello,

     

    You may need to increase the size of the mount point drives M: to resolve this problem. If something does occur at the root of the mount point and start to fill it up, indexing will stop on the databases under the mount point even though they still have more than sufficient room to continue indexing.

     

    Thanks,

    Simon Wu

    Exchange Forum Support

     

    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 tnmff@microsoft.com.

     

     

     

    Monday, December 5, 2011 9:17 AM
    Moderator
  • Hello,

     

    Is there any update on this thread?

     

    Thanks,

    Simon Wu

    Exchange Forum Support

     

    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 tnmff@microsoft.com.

     

     

     

     

    Wednesday, December 7, 2011 2:10 AM
    Moderator
  • I must do the same thing happens to me, I generated the same error when doing searches for owa, I apply the command generates the odd search but did not return the result 100% real

    Ing.D Leon

    Tuesday, March 27, 2012 4:41 PM