Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A memory leak occurs in the FDHOST.exe process in SQL Server 2008 or in SQL Server 2008 R2


Symptoms

Consider the following scenario:

  • You run an instance of SQL Server 2008 or SQL Server 2008 R2.

And:

  • You run the Full-Text Filter Launcher (FDHOST Launcher) service under a local system account on a domain controller.

Or:

In this scenario, when you perform a population for a large full-text index, you may notice the following symptoms:

  • A memory leak occurs in Fdhost.exe process.
  • The population experiences Access is denied.
  • The operating system becomes unresponsive.
  • The Process(Fdhost.exe):Virtual Bytes counter increases. Howeverm the counter never fully shrinks as expected.

↑ Back to the top


Cause

The behavior occurs because the Full-Text Filter Launcher service is running under an account that has insufficient permissions and privileges. This prevents SQL Server from shutting down the inbound shared memory (ISM) connection with the Fdhost.exe process. This condition prevents the release of the ISM reserved memory for the Fdhost.exe process.

↑ Back to the top


Resolution

If SQL Server is running on a domain controller, configure the FDHOST Launcher service to run under a domain account or a local service account. Additionally, verify that the privileges documented in the Setting Up Windows Service Accounts topic are offered.


For further information refer to the Security Recommendations section under the following topic in SQL Server 2008 Books Online:

The MSSQLFDLauncher$instancename service, for example "NT Service\MSSQLFDLauncher$SQL2K8" should also have the following local policies:

  • Replace A Process Level Token
  • Bypass Traverse Checking
  • Adjust Memory Quotas for a process
  • Logon as a service

Note You must restart the SQL Server service after granting any of the missing rights to the Full-Text search service account.

The following screenshots show a Full-Text service account configured as a Local Service account and the rights assigned to the same in Local Security policy:

 

↑ Back to the top


More Information

Note that some Windows built-in accounts, when used as the SQL Server service startup account or the Full-Text Filter Launcher service startup account, may not have the needed privileges, as documented in the Setting Up Windows Service Accounts topic.

Note This issue has been fixed in SQL Server 2012.

For additional information on configuring FDHost Launcher service, check the following article in the Microsoft Knowledge Base

2159124 How to setup the FDHOST Launcher service to work properly

 

↑ Back to the top


Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2014053
Revision : 1
Created on : 1/8/2017
Published on : 10/30/2013
Exists online : False
Views : 776