When you filter an Index search by a view in a Lotus Notes content source on a server that is running SharePoint Portal Server 2003, all the items in the content source are indexed

When you filter an Index search by a view in a Lotus Notes content source on a server that is running Microsoft Office SharePoint Portal Server 2003, all the items in the content source are indexed. However, when you filter the search by a view, only those items that appear in the Lotus Notes view should be indexed.

This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest SharePoint Portal Server 2003 service pack, you do not have to install the hotfix.

Service pack information

This problem is corrected in SharePoint Portal Server 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for SharePoint Portal Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
After you install the service pack, follow the steps that are listed in the "How to enable this hotfix" section of the article to set the Databases registry key and to activate the hotfix.

Hotfix information

How to obtain the hotfix

This issue is fixed in the SharePoint Portal Server 2003 hotfix packages 919175 and 898547. For more information about the English version of this hotfix package, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the German and the Spanish versions of this hotfix package, click the following article number to view the article in the Microsoft Knowledge Base: Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

How to enable this hotfix

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click to select the following registry key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SPSSearch\Notes Configs\Servers\servername
3. After you select the key that is specified in step 2, point to New on the Edit menu, and then click Key.
4. Type Databases, and then press ENTER.
5. Click Databases, point to New on the Edit menu, and then click Key.
6. Type the name of the database that you want to search, and then press ENTER.
7. Click the database key that you specified in step 6, point to New on the Edit menu, and then click Key.
8. Type ExclusionProperties, and then press ENTER.
9. Click the ExclusionProperties key, point to New on the Edit menu, and then click String Value.
10. Type the property name that you want to exclude, and then press ENTER. Then, change the property value to the value that you want to exclude.
    
    For example, to change the property value to exclude the Internal Domain category, follow these steps:
    1. Type Category, and then press ENTER.
    2. Right-click Category, and then click Modify.
    3. In the Value data box, type Internal Domain, and then click OK.
11. Repeat steps 9 and 10 for each property name and value that you want to exclude.
12. On the File menu, click Exit to quit Registry Editor.
13. Reset the Index, and then perform a full crawl of the server that is running SharePoint Portal Server 2003.

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

This problem was first corrected in SharePoint Portal Server 2003 Service Pack 3.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.