Microsoft Knowledge Base Email Alertz

KBAlertz.com: (885955) - Describes a problem that occurs after the primary SMTP address is changed in the Exchange default recipient policy.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 885955 - Last Review: December 3, 2007 - Revision: 2.8

The operation is unsuccessful when you run a population process on a public folder full-text index in Exchange Server 2003

SYMPTOMS

When you run an incremental population or a full population of the full-text index in Microsoft Exchange Server 2003, the population process appears to stop responding (hang). Additionally, you experience both of the following symptoms:
  • If you view the Full-Text Indexing container under the public information store, the Index State item displays a status of Crawling Incrementally in an incremental population scenario. And, the Index State item displays a status of Crawling in a full population scenario. In both of these scenarios, the index state never returns to a status of Idle.
  • No events appear in the Application log until you stop the index population process. In this scenario, the following event appears in the Application log after you stop the index population process:

    Event Source: Microsoft Search
    Event Category: Gatherer
    Event ID: 3052
    Date: date
    Time: time
    Type: Information
    User: N/A
    Computer: Computername
    Description: The current activity on project <IndexProjectName> has stopped.

    However, no event appears that indicates why the index population operation did not succeed.

CAUSE

This problem occurs if you change the primary Simple Mail Transfer Protocol (SMTP) address in the default recipient policy in Exchange 2003.

A full-text index of a public information store in Exchange 2003 depends on the default recipient policy SMTP address. If you modify the primary SMTP address for the default recipient policy, the start address for that full-text index is no longer correct.

Note This problem may also occur if you perform a domain rename operation in your domain.

A full-text index of a private information store is not affected when you modify the primary SMTP address in the Exchange 2003 default recipient policy.

RESOLUTION

To resolve this problem, remove and then re-create the full-text index for the public information store. To do this, follow these steps.

Important The removal and re-creation of the full-text index will make this index unavailable for client access. Additionally, the re-creation of this index may use lots of resources on your Exchange computer. Therefore, we recommend that you perform this procedure during a period of low client activity.
  1. Start the Microsoft Exchange System Manager tool. To do this, click Start, point to All Programs, point to Microsoft Exchange, and then click System Manager.
  2. Expand Servers, expand your Exchange computer, and then expand the storage group that contains the public information store that you want to remove the full-text index from.
  3. Right-click the public folder store that the full-text index is created on, and then click Properties.
  4. Click the Full-Text Indexing tab, click to clear the This index is currently available for searching by clients check box, and then click OK.
  5. Right-click the public folder store that the full-text index is created on, and then click Delete Full-Text Index.
  6. When you are prompted with the following message, click Yes:
    Deleting the full-text index on this store will remove the existing catalog file.

    Do you wish to continue?
  7. When you are prompted with the following message, click Yes:
    This option will stop any in-process full-text indexing. Indexing will continue at the next scheduled time or by manually updating or rebuilding the index.

    Do you want to continue?
  8. Right-click the public folder store that you want to create the full-text index on, and then click Create Full-Text Index.
  9. In the Select the location to create the catalog box, type the path to where you want to create the catalog, and then click OK.
  10. Right-click the public folder store, and then click Start Full Population.
  11. When you are prompted with the following message, click Yes:
    The update process will start immediately and, depending on the size of your store, could take time and server resources.

    Do you want to continue?
  12. When you are prompted with the following message, click Yes:
    The full population of the full-text index will take significantly longer than an incremental population. Are you sure you want to continue?
  13. After the full-text population process is completed, configure and run an incremental population of the full-text index before you enable this full-text index for searching.
For additional information about how to configure full-text indexing in Exchange 2003, see Working with the Exchange Server 2003 Store . To obtain this book, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/1b901872-69a7-439c-b2eb-8288c79a54f4.aspx (http://technet.microsoft.com/en-us/library/1b901872-69a7-439c-b2eb-8288c79a54f4.aspx)

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The Search Administrative Tool (mssearch_admin) is also available to "reset" the full-text index. This tool is included in the Exchange Server All-In-One Tools. To obtain this tool, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=46FD5644-BD0D-4CFA-95F8-64BA34BDE6A7&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=46FD5644-BD0D-4CFA-95F8-64BA34BDE6A7&displaylang=en)
The Search Administrative Tool is intended to let you perform all the following functions:
  • Determine which Exchange stores in your domain have full-text indexes configured.
  • Obtain the status of the existing full-text indexes on the local Exchange computer. It also provides additional information about those full-text indexes.

    Note This tool provides more information about the full-text index than is available through the Exchange System Manager tool.
  • Repair your existing full-text indexes after you perform one or both of the following procedures:
    • A domain rename operation.
    • A modification of the primary SMTP address in the Exchange default recipient policy.
  • Use command-line commands to interact with an existing full-text index. You can perform all the following actions by using a command-line command:
    • Enable the index for searching.
    • Disable the index for searching.
    • Start a full population of the index.
    • Start an incremental population of the index.
    • Pause the current index population operation.
    • Resume the current index population operation.
    • Stop the current index population operation.
    • Reset the index. Use this command as a replacement for the deletion and re-creation of the full-text index.
For additional information about how to deploy or configure Exchange 2003, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/bb123872.aspx (http://technet.microsoft.com/en-us/library/bb123872.aspx)

APPLIES TO
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition
Keywords: 
kbenv kbnofix kbbug kbtshoot kbprb KB885955
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please