Article ID: 329660 - View products that this article applies to.
This article was previously published under Q329660
If you added a DirX LDAP v3/X.500 directory to your address book, and you try to open the DirX Address Book in Microsoft Outlook, the addresses do not appear, and you receive the following two error messages:
No entries were found. You may need to supply authentication information in order to be able to access the directory.
The action could not be completed.
If you try to search for a specific address entry in the DirX address book, you receive the following error message
The search could not be completed. MAPI_E_CALL_FAILED
This problem occurs because Outlook cannot handle the Lightweight Directory Access Protocol (LDAP) protocol error code 0x4 that is returned when you request address entries from the DirX directory that acts as the LDAP server. Outlook requests a maximum limit of 100 address entries from the LDAP server. If you request 100 address entries in Outlook, and the LDAP server is configured to return 49 address entries, the LDAP server responds with the 49 requested address entries plus the LDAP protocol error code 0x4 that signals Outlook that the address entry limit was reached. Instead of receiving the requested 100 address entries, you receive 49 address entries.
Outlook cannot handle the LDAP protocol error internally, and you receive the error messages that are mentioned in the "Symptoms" section of this article, but the error messages do not describe the real cause of the problem.
Service Pack InformationThis problem is corrected in Microsoft 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:
(http://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 hotfix 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 ------------------------------------------- 13-Dec-2002 22:38 80,896 Olkintl.msp 13-Dec-2002 22:40 593,920 Olkintlff.msp
Date Time Version Size File name ---------------------------------------------------- 23-Aug-2002 14:58 10.0.4420.0 842,312 Msmapi32.dll 11-Dec-2002 01:26 10.0.4810.0 192,512 Emsabp32.dll 13-Dec-2002 00:58 10.0.4810.0 113,224 Emablt32.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This problem was first corrected in Office XP Service Pack 3.
The LDAP servers that have the size limit set to a value greater than 100 do not exhibit the problem. To resolve the problem without installing the hotfix on the client machines, contact the administrator of the LDAP server to set the limit of returned address entries to a value greater than 100.