Article ID: 312748 - Last Review: June 11, 2002 - Revision: 1.2

BUG: Garbage Characters Are Displayed in a File Name When It Is Stored to WebDAV

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q312748
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry
Expand all | Collapse all

SYMPTOMS

When you store documents that have double-byte character set (DBCS) characters in the file name to a WebDAV repository from the BizTalk Mapper or the BizTalk Editor, the actual file name that is stored in WebDAV may contain garbage characters.
Back to the top

CAUSE

This problem may occur if there are incorrect settings that relate to WebDAV and DBCS characters in Microsoft Internet Information Services (IIS).
Back to the top

RESOLUTION

To resolve this problem, make the following modifications to the registry of the IIS server that houses the WebDAV repository:

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters\FavorDBCS
  3. On the Edit menu, click Modify, type 0, and then click OK.
  4. Quit Registry Editor.
After you make this change, restart IIS.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in Microsoft BizTalk Server 2002.
Back to the top
APPLIES TO
  • Microsoft BizTalk Server 2002 Standard Edition
Back to the top
Keywords: 
kbbug kbpending KB312748
Back to the top