Article ID: 929046
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
SYMPTOMS
When a Microsoft Windows Server 2003-based computer connects to an SQL database by using SQL integrated authentication, a memory leak may occur in the Microsoft OLE DB provider. This memory leak is not continuous, and memory is consumed in steps. The memory leak occurs in private bytes of the application that connects to the SQL database.
The memory that is allocated by the LsaInitializeSecurityContextCommon function is not always released correctly, and this leads to an exhaustion of a predefined array of virtual memory spots. When this array is exhausted, a new array that is two times the size of the original array is allocated. This array is then exhausted, and this causes all the available memory on the computer to be used.
CAUSE
This problem occurs because the management of the memory that is allocated in the SECUR32!LsaInitializeSecurityContextCommon function and in the SECUR32!DeleteSecurityContext function is not handled correctly when a null pointer is passed to the function. In this scenario, a memory spot is reserved from a list, and the memory spot is not freed.
RESOLUTION
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
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.
Windows Server 2003, 32-bit x86 editions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Secur32.dll | 5.2.3790.2859 | 65,536 | 10-Jan-2007 | 13:07 | x86 | SP1 | SP1QFE |
| Secur32.dll | 5.2.3790.4003 | 65,536 | 10-Jan-2007 | 12:41 | x86 | SP2 | SP2QFE |
Windows Server 2003, 64-bit x64 editions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Secur32.dll | 5.2.3790.2860 | 122,880 | 11-Jan-2007 | 20:03 | x64 | SP1 | SP1QFE |
| Wsecur32.dll | 5.2.3790.2860 | 66,560 | 11-Jan-2007 | 20:03 | x86 | SP1 | WOW |
| Secur32.dll | 5.2.3790.4004 | 122,880 | 11-Jan-2007 | 21:44 | x64 | SP2 | SP2QFE |
| Wsecur32.dll | 5.2.3790.4004 | 66,560 | 11-Jan-2007 | 21:44 | x86 | SP2 | WOW |
Windows Server 2003, 64-bit Itanium-based editions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Secur32.dll | 5.2.3790.2859 | 190,464 | 09-Jan-2007 | 22:03 | IA-64 | SP1 | SP1QFE |
| Wsecur32.dll | 5.2.3790.2859 | 66,560 | 09-Jan-2007 | 22:03 | x86 | SP1 | WOW |
| Secur32.dll | 5.2.3790.4003 | 190,464 | 10-Jan-2007 | 00:13 | IA-64 | SP2 | SP2QFE |
| Wsecur32.dll | 5.2.3790.4003 | 66,560 | 10-Jan-2007 | 00:13 | x86 | SP2 | WOW |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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
Additional query words: LsaInitializeSecurityContextCommon memory leak
Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinservperf kbhotfixserver kbwinserv2003postsp2fix KB929046
