FIX: You experience an application memory leak when you use the IIS Active Directory Service Interfaces provider to query the metabase in Internet Information Services 6.0

When you use the Microsoft Internet Information Services (IIS) Active Directory Service Interfaces (ADSI) provider to query the metabase in Internet Information Services 6.0, you experience an application memory leak. The process leaks approximately 100 kilobytes (KB) of memory every time that the metabase is queried.

This issue occurs if the Background Intelligent Transfer Service (BITS) Server Extensions are installed on the computer.

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:

Hotfix information

Prerequisites

No prerequisites are required.

Restart requirement

You may be prompted to restart the computer after you apply this hotfix. If you are prompted to restart the computer, you must restart the computer to complete the installation of 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.

Microsoft Windows Server 2003, Itanium architecture

Microsoft Windows Server 2003, x64

Microsoft Windows Server 2003, x86

To work around this issue, unregister the Bitsmgr.dll file. To unregister the Bitsmgr.dll file, click Start, click Run, type regsvr32 /u %windir%\bitsmgr.dll, and then click OK.

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 Microsoft Windows Server 2003 Service Pack 2.

This issue occurs when you use a metabase path that is similar to the following. This issue does not occur if you use a metabase path that is similar to the following.