Web Content Source that Contains DBCS Characters in Its Name Is Not Indexed Correctly (318775)



The information in this article applies to:

  • Microsoft SharePoint Portal Server 2001

This article was previously published under Q318775

SYMPTOMS

You may experience the following behaviors in the Japanese-language version of SharePoint Portal Server:
  • When create a Web content source to a shared folder that contains Double-Byte Character Set (DBCS) characters in its name, and entry similar to the following appears in the detailed log:

    URL is excluded because the URL extension is restricted as defined in the file type rules.

  • When you search the Web site, no documents are returned in the search results.

CAUSE

This problem may occur if the following conditions are true:
  • The name of the shared folder contains Double-Byte Character Set (DBCS) characters.

    -and-
  • The documents that you search for are contained in the folder.
When the name of a folder contains DBCS characters, SharePoint Portal Server incorrectly processes the names of the files that are contained in the folder. As a result, the files in the folder are not indexed.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SharePoint Portal Server 2001. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

312963 How to Obtain the Latest SharePoint Portal Server 2001 Service Pack

The Global version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Version         File name
   --------------------------
   10.145.4629.10  Mssph.dll 
				
Note: Because of file dependencies, this update requires Microsoft SharePoint Portal Server 2001.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SharePoint Portal Server 2001 Service Pack 2.

Modification Type:MinorLast Reviewed:4/28/2003
Keywords:kbSharePtPortalSvr2001SP2fix kbbug kbfix kbSharePtPortalSvr2001preSP2fix KB318775