This article was previously published under Q266165
This article has been archived. It is offered "as is" and will no longer be updated.
If you develop custom information store providers that support Unicode, when you copy folders that contain subfolders from the Microsoft Exchange Server information store to the custom information store, the subfolders in the sample information store may be created with truncated subfolder names.
This problem can occur because the call to IMAPIFolder::CreateFolder() passes the ulFlags parameters as 0, which implies that the string is American National Standards Institute (ANSI), even though the string that is passed is Unicode. According to documentation, the ulFlags variable should be set to MAPI_UNICODE if the passed-in strings are in Unicode format. If the MAPI_UNICODE flag is not set, the strings are in ANSI format.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
8/10/2000 3:00 AM
Microsoft has confirmed that this is a problem in Microsoft Outlook 2000.