Authorization Manager closes the LDAP connection when an attempt to read the Authorization Manager store fails on a computer that is running Windows Server 2003 or Windows Server 2008

Consider the following scenario:

• On a computer that is running Windows Server 2003 or Windows Server 2008, some applications use Authorization Manager (AzMan) to validate authorization requests.
• The role assignment is saved in an Authorization Manager store that resides in an Active Directory Application Mode (ADAM) directory.
• The applications frequently read and update the role assignment over a Lightweight Directory Access Protocol (LDAP) connection.

In this scenario, if an attempt to read the Authorization Manager store fails, Authorization Manager closes the LDAP connection. Therefore, application downtime occurs while the Authorization Manager store is being reloaded.

When this problem occurs, the following error is logged in the Authorization Manager log:

This problem occurs because Authorization Manager incorrectly closes the LDAP connection when an attempt to read the Authorization Manager store fails. Authorization Manager is expected to return the error message without closing the LDAP connection.

Important A minor performance reduction may occur after you enable this hotfix. The performance reduction depends on the network latency. More network latency results in more performance reduction.

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: 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 Windows Server 2003 with Service Pack 1 or Windows Server 2003 with Service Pack 2 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You may have to restart the computer after you apply this hotfix if the Azroles.dll file is being used.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Windows Server 2008 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: 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

The MANIFEST (.manifest) files and MUM (.mum) files that are installed for each environment are listed separately.

MUM and MANIFEST files and the associated security catalog (.cat) files are critical to maintain the state of the updated component. The security catalog files are signed by using a Microsoft digital signature. (The attributes of the security catalog files are not listed.)

Windows Server 2008, x86-based versions

Windows Server 2008, x64-based versions

Windows Server 2008, Itanium-based versions

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008

Registry information

The behavior of the hotfix is controlled by a registry entry. After you apply this hotfix, this registry entry is automatically defined.

If you apply a later hotfix that includes the Azroles.dll file instead of applying this hotfix, the later hotfix also includes the current hotfix. However, the registry entry is not automatically defined by that later hotfix.

To enable the hotfix, you must edit the registry manually. To do this, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\AzRoles
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type UseStrongLocking, and then press ENTER.
5. Right-click UseStrongLocking, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: