Hello,
we use PDF iFilter 64 [https://www.adobe.com/support/downloads/detail.jsp?ftpID=5542] for indexing PDF files to enable FullTextSearch on SQL Server. This works fine with different SQL Server versions (2008, 2012 and 2014) as long as we install this on a server OS like Windows 2008 or Windows2012.
But we have no luck, if we try the same on a client OS like Windows 7 or Windows 8. All mentioned operating systems are used in the 64bit edition.
As some threads mentioned problems with a too long installation path, we tried the default folder first and shortened it to C:\Adobe\iFilter11 on a 2nd approach, no success either.
When checking the 'fulltext document types' everything looks fine.
SELECT document_type, path from sys.fulltext_document_types where document_type = '.pdf'
results in
| .pdf | C:\Adobe\iFilter11\bin\PDFFilter.dll |
But when looking into the FTS-logs after creating the fulltext index all PDF documents in our table give a warning "No appropriate filter was found during full-text index population[...]"
...
2016-01-27 09:45:33.73 spid33s Warning: No appropriate filter was found during full-text index population for table or indexed view '[fts_test].[dbo].[fts_testtable]' (table or indexed view ID '3335123456', database ID '6'), full-text key value '123'. Some columns of the row were not indexed.
2016-01-27 09:45:33.74 spid26s Warning: No appropriate filter was found during full-text index population for table or indexed view '[fts_test].[dbo].[fts_testtable]' (table or indexed view ID '3335123456', database ID '6'), full-text key value '124'. Some columns of the row were not indexed.
...
According to this thread Re: PDF iFilter Support for Windows 8.1 and SQL Server 2014 changing the GUID of the persistent handler should help, but this gives no correction. On the contrary: when checking the fulltext document type (see above) the pdf extension is no longer found after changing the GUID.
Any hints will be appreciated.
tia
Fossi
2
Replies
AdChoices