Microsoft KB Archive/323612

= &quot;Can't Contact LDAP Directory server (81)&quot; error message when you write an e-mail message in Outlook 2002 =

Article ID: 323612

Article Last Modified on 10/11/2005

-

APPLIES TO


 * Microsoft Outlook 2002 Standard Edition

-



This article was previously published under Q323612



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
When you compose an e-mail message in Outlook in an Offline state and your profile is configured to use an LDAP provider, you may receive the following error message:

Microsoft LDAP Directory: Can't Contact LDAP Directory server (81)



CAUSE
This problem may occur if your profile is configured to use an LDAP provider. When you log on to Remote Mail in Outlook (even when you log on Offline), Outlook tries to access the LDAP server. This error message may occur if all the following conditions exist:
 * You log on to Remote Mail Offline.
 * Your computer does not currently have access to the location where the LDAP server exists.
 * You create an e-mail message, and then press CTRL+K for name resolution or Outlook performs name resolution.



Service Pack Information
This 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:

307841 OFFXP: How to Obtain the Latest Office XP Service Pack

Hotfix Information
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.

Part 1: Download and Install the Fix
A 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 Office XP service pack that contains this fix.

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/contactus/?ws=support

Note 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 English version of this fix should have the following file attributes or later:   Date         Time   Size       File name 21-Feb-2003 23:40  5,210,692  Outlookff.msp After the hotfix is installed, the English version of this fix will have 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.   Date         Time   Version      Size       File name 19-Sep-2002 15:23  10.0.4517.0    105,032  Envelope.dll 09-Jan-2003 16:31  10.0.4907.0    346,696  Exsec32.dll 08-Aug-2002 21:22  10.0.4406.0    137,800  Impmail.dll 23-Jan-2003 19:04  10.0.4921.0    543,304  Outlcm.dll 20-Feb-2003 19:20  10.0.5018.0  6,314,568  Outllib.dll 11-Oct-2002 16:14  10.0.4608.0     92,744  Outlmime.dll 20-Feb-2003 19:20  10.0.5018.0     47,688  Outlook.exe 08-Nov-2002 15:47  10.0.4705.0    121,416  Outlph.dll 25-Nov-2002 12:50  10.0.4721.0     47,688  Recall.dll

Part 2: Activate the Fix
After you download and install the fix, you must create the   value to activate the fix:  Click Start, and then click Run. In the Open box, type regedit, and then click OK. Click the following registry key:

 

 With the   key selected, point to New on the Edit menu, and then click DWORD Value. Type DisableLDAPWhenOffline, and then press ENTER.</li> With   selected, click Modify on the Edit menu.</li> In the Value data box, type 1, and then click OK.

Note To activate the fix, change the Value data box to 1. To turn off the setting, change the Value data box to 0 .</li> On the File menu, click Exit to quit Registry Editor.</li></ol>

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:

325671 OFFXP: Overview of the Office XP Service Pack 2

Additionally, 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:

330537 OFFXP: Office XP Updates and Patches Released After September 2002 May Require Windows Installer 2.0

<div class="status_section">

STATUS
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.

Additional query words: kb2HR1 FIX

Keywords: kbhotfixserver kbqfe kbconfig kbemail kberrmsg kbofficexppresp3fix kbbug kbfix kbofficexppresp2fix kbofficexpsp2fix KB323612

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.