Article ID: 815924 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft Outlook, you can search for names in a Lightweight Directory Access Protocol (LDAP) address book that you want to insert in the To box, the Cc box, or the Bcc box of an e-mail message. However, if the name that you are searching for contains Double Byte Character Set (DBCS) characters (for example, Japanese or Korean characters), no names appear in the Search Results box as expected.
Service Pack InformationThis problem is corrected in Office XP Service Pack 3.To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/307841/ )How to obtain the latest Office XP Service Pack
Hotfix InformationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Office XP service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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.
After the hotfix is installed, the following files will have the listed attributes or later:
Date Time Size File name -------------------------------------------- 10-Mar-2003 16:44 89,088 Olkintl.msp 13-Mar-2003 23:30 1,767,936 Olkintlff.msp 10-Mar-2003 16:55 1,764,352 Olkintlff.msp 10-Mar-2003 16:47 91,136 Olkintlop.msp
This fix is a post-Office XP Service Pack 2 (SP-2) fix. To install the fix, you must have Office XP SP-2 installed. For additional information about Office XP SP-2, click the following article number to see the article in the Microsoft Knowledge Base:
Date Time Version Size File name ----------------------------------------------------------- 07-Mar-2003 01:26 10.0.5104.0 113,224 Emablt32.dll 28-Feb-2003 01:56 10.0.5025.0 576,072 Emsmdb32.dll 23-Aug-2002 22:58 10.0.4420.0 834,120 Msmapi32.dll 29-Apr-2002 18:44 10.0.4024.0 47,432 Bjablr32.dll 29-Apr-2002 18:44 10.0.4024.0 129,352 Contab32.dll 15-May-2002 00:42 10.0.4109.0 194,888 Emsabp32.dll 23-Jun-2002 03:38 10.0.4219.0 133,704 Emsui32.dll 21-May-2002 04:26 10.0.4115.0 506,184 Mspst32.dll 29-Apr-2002 18:50 10.0.4024.0 55,624 Olkfstub.dll 21-May-2002 04:26 10.0.4115.0 727,368 Outex.dll 10-Jun-2002 21:27 10.0.4205.0 358,984 Pstprx32.dll
325671Additionally, you may have to install Windows Installer 2.0 to install this fix. For additional information about the Windows Installer requirement for post-Office XP SP-2 fixes, click the following article number to see the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/325671/EN-US/ )OFFXP: Overview of the Office XP Service Pack 2
(https://support.microsoft.com/kb/330537/EN-US/ )OFFXP: Office XP Updates and Patches Released After September 2002 May Require Windows Installer 2.0
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 Office XP Service Pack 3.