Problems May Occur When Attaching a File That Has a File Name with Localized and Punctuation Characters from a SharePoint Portal Server (818860)



The information in this article applies to:

  • Microsoft Content Management Server 2002
  • Microsoft SharePoint Portal Server 2001 SP2

SYMPTOMS

When you try to attach a document that contains certain localized characters and punctuation characters in the file name, you may receive the following error message:
Document cannot be copied.
This behavior occurs when you use Microsoft Content Integration Pack 2 for Content Management Server 2002 and SharePoint Portal Server 2001.

CAUSE

The cause of this problem is the URL of the document. On the SharePoint Portal Server, the URL of the document is encoded. When the URL of the document is passed to the internal components, an exception is thrown.

RESOLUTION

The file name must be changed so there are no problematic localized and punctuation characters. After you change the file name, you can attach the document.

STATUS

This behavior is by design. There is a standard way of encoding URLs by using the URLEncode method. However, there is no current standard for decoding.

MORE INFORMATION

When you try to attach a document to a Content Management Server posting, the SharePoint Portal Server Browser dialog box creates a URL that contains a query string. The query string contains information about the document. The attachment process does not succeed if the file name of the document that you try to upload contains any localized and punctuation characters other than a space. The problem occurs when the file name is encoded by the Server.URLEncode function to the %HH text-based representation of its UTF-8 value.

For example, the German character ö in the file name causes the problem.

The problem occurs because Content Integration Pack 2 for Content Management Server 2002 and SharePoint Portal Server 2001 both use the URLEncode function to encode the URL of the file that you select for attachment. A string that contains the encoded URL is then passed to an ASP page. The query parameter of the URL is then passed to one of the internal COM components. Because the COM component tries to open this URL without first decoding the URL, an exception is thrown. The result is the error described earlier in this article.

This has been tested with Japanese and German characters with the same resulting behavior.

Modification Type:MajorLast Reviewed:4/28/2003
Keywords:kbprb KB818860 kbAudDeveloper