Microsoft KB Archive/283996

= The Dedicated Content Indexer Does Not Propagate Search Scopes to the Target Computer =

Article ID: 283996

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft SharePoint Portal Server 2001

-



This article was previously published under Q283996





SYMPTOMS
Search scopes defined on content sources in an index workspace are not available on the destination search server.



CAUSE
This behavior can occur because SharePoint Portal Server does not propagate the search scopes for the content sources in the index workspace to the destination workspace.



WORKAROUND
To work around this behavior and use the search scopes from the content sources in the index workspace, the coordinator for the destination workspace must create fake content sources by using search scopes that match those of the content sources in the index workspace.



MORE INFORMATION
You can configure an index workspace when you want to separate the tasks of searching and indexing (crawling content sources). The index can be propagated to a destination workspace on another SharePoint Portal Server computer, and this server is typically named the &quot;search server&quot;.

In this configuration, resources on the index server and the search server are designated to complete these specific tasks. However, you can only manage content sources and not individual documents in an index workspace.

Additional query words: SPS dci

Keywords: kbbug kbpending KB283996

-

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

© Microsoft Corporation. All rights reserved.