MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
You are not able to use an OpenLDAP server from Microsoft Outlook 2002 or Microsoft Outlook 2003.
When you use an OpenLDAP Server version 2.2.29, the LDAP search fails. The server is returning the error "unavailable critical extension in context". If you run a network capture, the OID 1.2.840.1135184.108.40.2069 is causing the trouble. This OID is for the pagedResultsControl. The following is the error message that you receive: The search could not be completed. MAPI_E_CALL_FAILED (even if you did not configure a MAPI account in the current profile). Outlook Express is able to process LDAP queries.
Outlook 2002 and Outlook 2003 support the Virtual List Views (VLV) LDAP extension. This LDAP extension makes it possible for Outlook to present LDAP query results in a more efficient way for most LDAP server implementations. The pagedResultsControl control is not supported by all LDAP servers.
For Outlook XP, download and install SP3 for Outlook XP, then modify the Microsoft Windows registry.
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.
Please visit this page before continuing.
For Outlook 2003, you must manually modify the Microsoft Windows registry directly: 1. Quit all Office programs. 2. Click Start, and then click Run. 3. In the Open box, type regedit, and then click OK. 4. Click the following key for Outlook XP: HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\LDAP For Outlook 2003, the key is: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\LDAP 5. With the LDAP key selected, point to New on the Edit menu, and then click DWORD Value. 6. Type DisableVLVBrowsing, and then press ENTER. 7. With the DisableVLVBrowsing DWORD Value selected, click Modify on the Edit menu. 8. In the Value data box, type 1 and then click OK. 9. On the File menu, click Exit 10. Restart the computer
According to the page , Outlook 2003 can create an address list that you can use to browse an LDAP server address list. This browsing feature set permits you to see a list of addresses when you open the address book, click anywhere in the address list, and then type a single character to move down the address list to the entries that start with that letter. For Outlook 2003 to provide this functionality for an LDAP server address list, the LDAP server must support either the Virtual List View (VLV) extension or a combination of two LDAP controls (the paged results and the server-side sort controls).
Some versions of OpenLDAP servers do not provide the pagedResultsControl OID (according to RFC 2696). Therefore, they cannot process the Microsoft Outlook 2002 or Microsoft Outlook 2003 LDAP queries.