The name of the user who created an area appears in the search results instead of the name of the user who is the contact for the area in SharePoint Portal Server 2003

When you search the portal site by using the name of the area as the search criteria, the name of the user who is configured as the contact for the area does not appear. You expect this name to appear next to the link to the area that is returned in the search results. Instead, the name of the user who created the area appears.

This problem occurs in Microsoft Office SharePoint Portal Server 2003 after you follow these steps:

1. You map the ContactName property of the urn:schemas-microsoft-com:sharepoint:portal:area name space to the Author property.
2. You add a keyword and a keyword Best Bet. The title of the keyword and of the keyword Best Bet is the same as the name of the area. The URL of the keyword Best Bet is the URL of the area.

This issue occurs if the ContactName property that you mapped is overwritten. More than one value for the Author property is returned. Therefore, the gatherer component in SharePoint Portal Server 2003 cannot determine the correct value to use.

How to obtain the hotfix

This issue is fixed in the SharePoint Portal Server 2003 post-Service Pack 1 Hotfix Package that is dated December 30, 2004. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: This hotfix applies to new portal sites that you create in your server farm deployment of SharePoint Portal Server 2003. After you apply this hotfix, if the ContactName property is set for an area, the user who is configured as the contact for the area is returned as the author. If the ContactName property is not set for an area, the user who created the area is returned as the author.

To apply this hotfix to existing portal sites on the server farm, you must run the Sp_srGetListingRecord.sql query file that is included in the hotfix package. For more information about how to do this, see the Readme.txt file that is included in the hotfix package.

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