The memory usage of the Lsass.exe process keeps increasing on one or more domain controllers that are running Windows Server 2003 if an application or a service calls the DsrAddressToSiteNamesExW function to translate a list of socket addresses

Consider the following scenario:

• An application or a service is running in a Windows Server 2003-based domain.
• This application or service calls the DsrAddressToSiteNamesExW function to translate a list of socket addresses to their corresponding site names and to their corresponding subnet names.

In this scenario, the memory usage of the Lsass.exe process keeps increasing on one or more domain controllers that are running Windows Server 2003 in this domain. If you use Performance Monitor or Task Manager to monitor the memory leak, you find that the private byte counter of the Lsass.exe process keeps increasing on the affected domain controllers.

After most of the available memory is consumed, you may encounter one or more of the following issues:

• Authentication requests against the affected domain controllers fail.
• The performance of the affected domain controllers continuously decreases.
• Some applications or services that are running on the affected domain controllers may encounter function failure or may encounter an exception because of low available memory.

The DsrAddressToSiteNamesExW function does not release allocated memory space for site names correctly. This behavior causes a memory leak.

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 the problem described in this article. 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, the domain controller must be running Windows Server 2003 Service Pack 2 (SP2).

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other 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.

For all supported x86-based versions of Windows Server 2003 SP2

For all supported Itanium-based versions of Windows Server 2003 SP2

For all supported x64-based versions of Windows Server 2003 SP2

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

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

For more information about the DsrAddressToSiteNamesExW function, visit the following Microsoft Web site: