FIX: The SQL Server service stops responding, and event ID 2019 is logged in the System log in SQL Server 2005 or in SQL Server 2008

In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you experience the following symptoms:

• The SQL Server service stops responding.
• The following event is logged in the System log:

  Event ID: 2019
  Description:
  The server was unable to allocate from the system nonpaged pool because the Pool was empty.

• The nonpaged pool consumes lots of memory. You can find this by using the Pool Nonpaged Bytes performance counter for the SQL Server process. Additionally, the Handle Count performance count has a large value.
• When you run the following query, lots of USERSTORE_TOKENPERM type cache entries are in the result.

  USERSTORE_TOKENPERM type cache entries.
  
  SELECT name, count(*) as [Num Entries]
  FROM
  (SELECT
  x.value('(//@name)[1]', 'varchar (100)') AS [Name]
  FROM
  (SELECT CAST (entry_data as xml),in_use_count,original_cost,current_cost
  FROM sys.dm_os_memory_cache_entries
  WHERE type = 'USERSTORE_TOKENPERM') 
  AS R(x,in_use_count,original_cost,current_cost)
  ) a
  group by a.name
  

The SQL Server security cache contains multiple login tokens for a single Windows login. These multiple login tokens cause a token handle leak.

Cumulative update information

The release version of SQL Server 2008

Important You must install this cumulative update package if your computer is running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

SQL Server 2008 Service Pack 1

Important You must install this cumulative update package if your computer is running SQL Server 2008 Service Pack 1.

The fix for this issue was also released in Cumulative Update 3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 2

Important You must install this cumulative update package if your computer is running SQL Server 2005 Service Pack 2.

The fix for this issue was first released in Cumulative Update 13 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3

Important You must install this cumulative update package if your computer is running SQL Server 2005 Service Pack 3.

The fix for this issue was also released in Cumulative Update 4 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

To work around this issue, use one of the following methods.

Method 1

Run the following statement in a job to periodically flush the security cache. This method removes all the entries from the security cache and frees the token handle.

Method 2

Set trace flag 4618 as a startup parameter for the SQL Server service. This method limits the size of the security cache so that the old entries are removed automatically from the security cache when the cache limit is reached.

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

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base: