Microsoft KB Archive/283983

= Duplicate Dedicated Content Indexer Names Can Propagate to the Same Workspace =

Article ID: 283983

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft SharePoint Portal Server 2001

-



This article was previously published under Q283983





SYMPTOMS
In a propagation scenario, if two or more dedicated content indexer workspaces that share the same name are set to propagate their catalogs to the same destination workspace, only the most recently propagated catalog is searchable from the destination workspace portal.



CAUSE
This behavior occurs because the most recently propagated catalog overwrites the existing catalog of the same name.



WORKAROUND
If you do not want the catalogs to be overwritten, when you create a dedicated content indexer workspace, ensure that you do not give it the same name as another dedicated content indexer workspace that is currently propagating to the destination workspace.



STATUS
This behavior is by design.



MORE INFORMATION
In some situations, it is useful to create a configuration where multiple dedicated content indexers overwrite each other's catalogs. For example, if you have a dedicated content indexer workspace that is crawling a very large document corpus, and it takes three days to finish indexing this source, the catalog on the destination server gets updated only every three days when a new catalog is propagated. Therefore, users who are searching against the catalog may not find documents that are indexed in the last two days. When you configure an additional dedicated content indexer that has the same name, and the exact same set of content sources for it, if you start its index update at a different time, you can refresh the index on the destination workspace more frequently. For example, if the original dedicated content indexer starts its first index update on Monday, and it propagates its catalog on Wednesday, and then again on Saturday, if an additional dedicated content indexer starts an index update on Tuesday, it would propagate an updated catalog on Thursday, and then again on Sunday. In this scenario, you are refreshing the catalog more often than every three days. You can have up to four dedicated content indexer workspaces propagating to a single destination workspace; if you add an additional dedicated content indexer, you can have even more frequent updates.

Additional query words: SPS Propagate SharePoint Portal Server DCI

Keywords: kbbug KB283983

-

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

© Microsoft Corporation. All rights reserved.