SQL Full-Text indexing not populating
- by Sam
Hi,
We installed a clustered SQL 2005 installation on windows 2008 and reattached our san drives from another machine and restored to do a migration to new hardware. There have been a few minor issues, but this one has me stuck.
Trying to populate Full-Text indexes is not working. I create a basic table with some simple text in a new database and get the same results as old indexes.
2010-09-27 10:30:46.85 spid19s Informational: Full-text Full population initialized for table or indexed view '[SQL_DBA].[dbo].[CIS_Report_Executions]' (table or indexed view ID '1767677345', database ID '5'). Population sub-tasks: 1.
2010-09-27 10:31:15.36 spid19s Error '0x80070003' occurred during full-text index population for table or indexed view '[SQL_DBA].[dbo].[CIS_Report_Executions]' (table or indexed view ID '1767677345', database ID '5'), full-text key value 0x000001DF. Attempt will be made to reindex it.
2010-09-27 10:31:15.37 spid19s The component 'MSFTE.DLL' reported error while indexing. Component path 'D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\MSFTE.DLL'.
2010-09-27 10:31:15.37 spid19s Error '0x80070003' occurred during full-text index population for table or indexed view '[SQL_DBA].[dbo].[CIS_Report_Executions]' (table or indexed view ID '1767677345', database ID '5'), full-text key value 0x000001E0. Attempt will be made to reindex it.
The rebuild/repopulate procedure finishes, but I get zero rows in the index. The .dll in the message is present and the service accounts have access to this. My FTData also has data in it, so it seems there wouldn't be permission issue on this folder.
Application throws this error:
“PHP Warning: mssql_query() [function.mssql-query]:
message: Full-text catalog 'ikm_PageIndex_FText' is in an
unusable state. Drop and re-create
this full-text catalog. (severity 16)
in
E:\Inetpub\knowledgebase_insidemesa\lib\database\mssql.php
on line 154”
A microsoft discussion is the only post I found which had claimed to fix this - said it was registry related, but then didn't post the fix.
