Error during Full-text population

I'm using Full-text in various databases on my servers (SQL2005 on W2K3). On a few databases the Full-text population ends with the error:

'Error '0x80030050' occurred during full-text index population for table or indexed view '[database].[dbo].[table]' (table or indexed view ID '1714105147', database ID '9'), full-text key value 0x00015EE1. Failed to index the row.'

The next log-line lets me know the name of the dll that caused the problem:

The component 'offfilt.dll' reported error while indexing. Component path 'C:\WINDOWS\system32\offfilt.dll'.

There's one solution I read about, but that one is not the case here. That sollution states that this problem occurs when de datatype is not the same as the filetype (e.g. datatype is pdf, documenttype is doc).

What can be the problem here?

Thanks.

I'm getting the same error in a multitude of environments (XP Pro (development/test environment), Windows Server 2003). SQL Server 2005 SP1 has been applied. Also getting on XP Pro system with SP2 applied. However, the OFFFILT.DLL appears to be part of the OS and not SQL Server. The version on my XP Pro is 2003.5.28.0 and is dated 2004-08-04.

I think the problem is with Word (.doc) files as I don't appear to have any problems indexing PowerPoint (.ppt) files.

|||

It sounds like the Microsoft Office Indexing filter DLL is choking on an unrecognised file format. Might you have some very old Word documents in the table, or conversely if there are new Word 2007 documents in there might these be too new?

|||In my case (not the original poster) the files that it is choking on are valid Microsoft Word documents. The documents can be opened in Office 2003. We are avoiding Office 2007 for now. Not every document has a problem. So it is something (style, font, property, ?) in the document that is tripping it up.|||

Ok, it took some time, but here it is:

I had some word-documents with embedded object that were unkown to Word. So I deleted them from the documents. All messages with the error in the original post are gone now. There is however a 'known bug' in Full Text Catalogue (I got the information from Microsoft) which will be patched in SP3. If the Full Text Index is being used very frequent (I'm not sure if that is 500 times a second or 5000000 times...) it gets corrupted.

A few tips here:

Make sure the dll's concerning FTC are in place. You can use this query to see which dll's FTE is using:

select * from sys.fulltext_document_types

Make sure there are no unkown objects in your documents. The error produced, if so, contains a HEX-number which represents the id-column value of the table. You can transform it to a more usable number with this query:

select * from [table] where [id-column] in (cast([HEX-number] as int))

If all this is ok, it's getting more likely that you have the 'known-bug' issue at hand.