Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message if you try to bind to ADAM by using an account that is locked out or that has an expired password

Error message if you try to bind to ADAM by using an account that is locked out or that has an expired password

View products that this article applies to.

Symptoms

Consider the following scenario:
  • Active Directory Application Mode (ADAM) 1.1 with Service Pack 1 (SP1) is installed on a Microsoft Windows Server 2003-based computer.
  • You try to bind to ADAM on this computer by using an account that is locked out or that has an expired. password
In this scenario, you may receive a Lightweight Directory Access Protocol (LDAP) error message that resembles the following:
LDAP: error code 49 - 80090304: LdapErr: DSID-0C090311, comment: AcceptSecurityContext error, data 20ee, vece 20ee = ERROR_DS_INTERNAL_FAILURE
Note This error message is incorrect. This message occurs only when one of the following scenarios is true:
  • The account password is expired.
  • The account is locked out.
  • The account password must be changed.

↑ Back to the top

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must have ADAM SP1 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Adamdsa.dll1.1.3790.27241,630,72014-Jun-200613:56x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top

More information

This section describes two scenarios in which this problem occurs.

Scenario 1: The password naturally expires

  1. Your account password expires.
  2. You try to bind to ADAM by using your account.
  3. You receive a "20ee" exception error.

LDAP error message

Error <49>: ldap_simple_bind_s() failed: Invalid Credentials Server error: <empty>

Network Monitor trace

00000040                                      38 30 30 39             8009
00000050  30 33 30 43 3A 20 4C 64 61 70 45 72 72 3A 20 44 030C:.LdapErr:.D
00000060  53 49 44 2D 30 43 30 39 30 33 33 36 2C 20 63 6F SID-0C090336,.co
00000070  6D 6D 65 6E 74 3A 20 41 63 63 65 70 74 53 65 63 mment:.AcceptSec
00000080  75 72 69 74 79 43 6F 6E 74 65 78 74 20 65 72 72 urityContext.err
00000090  6F 72 2C 20 64 61 74 61 20 32 30 65 65 2C 20 76 or,.data.20ee,.v
000000A0  65 63 65 00                                     ece.

Security event log message

Event Type: Failure Audit Event Source: Security Event Category: Account Logon Event ID: 680 Description: Logon account: <account> Source Workstation: <workstation> Error Code: <error code>

ADAM event log message

No related internal processing events are logged.

Scenario 2: The administrator forces a password change

  1. You bind to ADAM by using an administrator account.
  2. You force a user to change their password at the next logon by setting the pwdLastSet attribute to 0.
  3. This user tries to bind to ADAM by using the new password.
  4. The user receives a "20ee" exception error.

LDAP error message

0 = ldap_set_option(ld, LDAP_OPT_ENCRYPT, 0) res = ldap_simple_bind_s(ld, 'CN=user@test,CN=users,DC=domain,DC=com', <unavailable>); // v.3 Error <49>: ldap_simple_bind_s() failed: Invalid Credentials Server error: <empty>

Network Monitor trace

00000030                    30 84 00 00 00 68 02 01 05 61       0....h...a
00000040  84 00 00 00 5F 0A 01 31 04 00 04 58 38 30 30 39 ...._..1...X8009
00000050  30 33 30 43 3A 20 4C 64 61 70 45 72 72 3A 20 44 030C:.LdapErr:.D
00000060  53 49 44 2D 30 43 30 39 30 33 33 36 2C 20 63 6F SID-0C090336,.co
00000070  6D 6D 65 6E 74 3A 20 41 63 63 65 70 74 53 65 63 mment:.AcceptSec
00000080  75 72 69 74 79 43 6F 6E 74 65 78 74 20 65 72 72 urityContext.err
00000090  6F 72 2C 20 64 61 74 61 20 32 30 65 65 2C 20 76 or,.data.20ee,.v
000000A0  65 63 65 00                                     ece.

Security event log message

Event Type: Failure Audit Event Source: Security Event Category: Account Logon Event ID: 680 Description: Logon account: <account> Source Workstation: <workstation> Error Code: <error code>

ADAM event log message

No related internal processing events are logged.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: KB919336, kbqfe, kbfix, kbbug, kbwinserv2003sp2fix, kbautohotfix

↑ Back to the top

Article Info
Article ID : 919336
Revision : 3
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 235