XCCC: You Cannot Browse Through a Non-MAPI Top-Level Hierarchy That Contains Non-ASCII Characters on a Japanese-Language Server (309748)


The information in this article applies to:

  • Microsoft Exchange 2000 Server
This article was previously published under Q309748

SYMPTOMS

You may not be able to browse through a non-MAPI top-level hierarchy from a client that connects to a Japanese-language Exchange 2000 server after you:
  • Create an application (non-MAPI) public folder tree with a name that contains non-ASCII characters on a United States English-language Exchange 2000 server.
  • Create a public information store database on the Japanese-language Exchange 2000 server, and then associate that information store with the non-MAPI top-level hierarchy (TLH) that you created on the United States English-language Exchange 2000 server.
When you try to browse through the non-MAPI top-level hierarchy, you may receive the following error message:
503 Service Unavailable
You may receive the following descriptions for errors in the Application event log on the Japanese-language server (these errors have been translated from Japanese into English):
For the following error, as for server directory 'M: \company.org.com\ Tst TLH '
The hypothetical route '/vroot' could not be added,:
The pass which is appointed is not found.
This data is the error cord/code.
Please refer to the sight of the Microsoft online support below concerning the supplementary information regarding this message,:
http://search.support.microsoft.com/search/?adv=1 data: 0000: 03 00 00 00....

The security the invalid binding descriptor 172.30.224.124:443:FANTA1 which is protected (host name disregard) it is in instance 100.
Please refer to the sight of the Microsoft online support below concerning the supplementary information regarding this message,:
Http: Please refer to the sight of the Microsoft online support of the file://search.support.microsoft.com/search/?adv=1:

WORKAROUND

To work around this problem, rename the non-MAPI top-level hierarchy and give it a name that contains only ASCII characters.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

MORE INFORMATION

For additional information about how to browse through a non-MAPI top-level hierarchy, click the article number below to view the article in the Microsoft Knowledge Base:

272183 XCCC: How to Connect to a Non-MAPI TLH in Outlook Web Access

Modification Type:MajorLast Reviewed:7/17/2006
Keywords:kbbug kberrmsg kbpending KB309748
©2004 Microsoft Corporation. All rights reserved.