The InitializeSecurityContext function fails with a status of "STATUS_INSUFFICIENT_RESOURCES (0xC000009A)" when the token size of a security principal is greater than 20,000 bytes in Windows Server 2003

View products that this article applies to.

Symptoms

Consider the following scenario:

In a Windows Server 2003 environment, the InitializeSecurityContext function is called by a kernel mode component.
The token size of an affected security principal is greater than 20,000 bytes.

In this scenario, the InitializeSecurityContext function fails with a status of "STATUS_INSUFFICIENT_RESOURCES (0xC000009A)."

This issue may also cause some other problems. For example, if you try to access a file share resource on a Windows Server 2003-based computer, you may receive the following error message:

Insufficient system resources exist to complete the requested service

↑ Back to the top

Cause

This problem occurs when Local Security Authority (LSA) allocates some user mode memory that is used to map SecBuffer data back to the caller in kernel mode. However, the calculation to request additional memory is incorrect, and the request may fail if part of the requested memory range is being used.

Note LSA makes the allocation request only if the buffer size is greater than 20,000 bytes.

↑ Back to the top

Resolution

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 Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed. 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

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.