FIX: Error message when you run a full-text query in SQL Server 2008 after you register an IFilter: "No appropriate filter was found during full-text index population for table or indexed view"

Article translations Article translations
Article ID: 972650 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario. You install Microsoft SQL Server 2008 on a computer that is running Windows Vista Business Service Pack 1, Windows XP, or Windows Server 2003. You register an IFilter in SQL Server 2008. When you run a full-text query, you receive the following error message:
No appropriate filter was found during full-text index population for table or indexed view 'TableName' (table or indexed view ID 'ViewID', database ID 'DatabaseID'), full-text key value 'FileName'. Some columns of the row were not indexed.

Additionally, this error message is logged in the SQL Server 2008 Errorlog file.

For example, you install Microsoft XML Paper Specification Essentials Pack (XEP) version 1.0 on the computer. Then, you register the XPS filter in SQL Server 2008. When you run a full-text query, you will experience this issue. You will experience this issue, if you register a third-party IFilter.

CAUSE

This problem occurs because SQL Server generates an incorrect path for the .dll file for the IFilter. SQL Server interprets the environment variable as part of the path, instead of interpreting the environment variable as the actual path. For example, SQL Server reads the following path from the registry:
%SystemRoot%\System32\XpsFilt.dll

However, SQL Server generates the following incorrect path for the .dll file for the IFilter:
C:\Windows\system32\%SystemRoot%\System32\XpsFilt.dll

RESOLUTION

SQL Server 2008

Important You must use this fix if you are 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:
971490 Cumulative update package 6 for SQL Server 2008
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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must use this fix if you are running SQL Server 2008 Service Pack 1.

The fix for this issue was first released in Cumulative Update 4 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:
973602 Cumulative update package 4 for SQL Server 2008 Service Pack 1
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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
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.

WORKAROUND

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

To work around this issue, follow these steps:
  1. Locate the .dll file for the IFilter for the document. For example, you may want to locate the XpsFilt.dll file for XPS documents. For more information about how to find the .dll file for the IFilter for a document, visit the following Microsoft Web site:
    http://msdn.microsoft.com/en-us/library/ms692488.aspx
  2. In Registry Editor, locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\
  3. Locate the following IFilter persistent handler GUID:

    {1E4CEC13-76BD-4ce2-8372-711CB6F10FD1}
  4. In this registry subkey, change the value of the path of the XpsFilt.dll file from %SystemRoot%\System32\XpsFilt.dll to XpsFilt.dll.
  5. Restart the SQL Server service.
  6. Examine the path of the XpsFilt.dll file by running the following statement:
    select document_type, path from sys.fulltext_document_types
    The result should show the correct path. By default, this path should be C:\Windows\system32\XpsFilt.dll .
  7. Right-click the table that is associated with the full-text search catalog, point to Full Text Index, and then click Start Full Population.

STATUS

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

REFERENCES

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:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


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:
822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, 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

Properties

Article ID: 972650 - Last Review: July 21, 2009 - Revision: 1.1
APPLIES TO
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB972650

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com