Microsoft KB Archive/326191

= An Index Propagation Problem Does Not Generate an Error =

Article ID: 326191

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft SharePoint Portal Server 2001

-



This article was previously published under Q326191



SYMPTOMS
When you configure SharePoint Point Portal Server computers to propagate an index from one computer to the other computer, an index may stop responding if a connectivity issue occurs between the servers.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SharePoint Portal Server 2001 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table.

  Version   File name 4629.30  Mssrch.dll NOTE: Because of file dependencies, this update requires Microsoft SharePoint Portal Server 2001 Service Pack 1.



STATUS
Microsoft has confirmed that this is a problem in Microsoft SharePoint Portal Server 2001.



MORE INFORMATION
For example, indexing server A propagates to SharePoint Portal Server computer B. If server A cannot gain access to server B because server B is down or because of a networking issue, and you start a crawl on server A for a propagated workspace, the crawl stops responding.

The content source that you are crawling stays in an indexing state without generating any errors until you manually stop the crawl. You may wait as long as two days without generating an error. Server A tries to determine if it can gain access to server B, and if server A cannot gain access to server B, server A stays at that point, instead of generating an error.

The dedicated content indexer workspace stops responding and tries to propagate to the main SharePoint Portal Server computer if:
 * You disconnect the main SharePoint Portal Server computer, and then start an index on the dedicated content indexer workspace. -and-


 * The dedicated content indexer workspace cannot reach a content source.

If the dedicated content indexer workspace cannot gain access to the main SharePoint Portal Server computer (because the main SharePoint Portal Server is offline), the dedicated content indexer workspace stops and logs an event ID 7012 error message in the Application event log, which is the expected behavior.

Additional query words: SPShang DCI

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbshareptportalsvr2001presp2fix KB326191

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.