Wednesday, March 28, 2012

pdf ifilter issue with sp_fulltext_service

Several internet posts I've read describe how to get SQL Server to recognize
a 3rd party ifilter .dll. This involves the use of sp_fulltext_service with
the following syntax:
Exec sp_fulltext_service 'verify_signature', 0
Exec sp_fulltext_service 'load_os_resources', 1
I've used these commands and have been able to get SQL Server and SharePoint
to build an index for pdf documents. Many of these instructions tell you to
reverse the settings after you're finished in order to better secure the
server. Those commands are:
-- Restore the Full-text service settings to their default
Exec sp_fulltext_service 'verify_signature', 1
Exec sp_fulltext_service 'load_os_resources', 0
The problem is, that once you run the above commands and reboot, you no
longer index any new pdf files added to the server. Is this the expected
behavior? If not, what am I doing wrong? I don't want to leave the security
hole open by not running these commands but then you don't index new files.
This is a duplicate post I created because I did not see my original after a
day of waiting. Please disregard this post and use the other. Thanks.
"Dlorbecki" wrote:

> Several internet posts I've read describe how to get SQL Server to recognize
> a 3rd party ifilter .dll. This involves the use of sp_fulltext_service with
> the following syntax:
> Exec sp_fulltext_service 'verify_signature', 0
> Exec sp_fulltext_service 'load_os_resources', 1
> I've used these commands and have been able to get SQL Server and SharePoint
> to build an index for pdf documents. Many of these instructions tell you to
> reverse the settings after you're finished in order to better secure the
> server. Those commands are:
> -- Restore the Full-text service settings to their default
> Exec sp_fulltext_service 'verify_signature', 1
> Exec sp_fulltext_service 'load_os_resources', 0
> The problem is, that once you run the above commands and reboot, you no
> longer index any new pdf files added to the server. Is this the expected
> behavior? If not, what am I doing wrong? I don't want to leave the security
> hole open by not running these commands but then you don't index new files.
>

No comments:

Post a Comment