First, a step by Step guide to highlight important settings.
When FTR is enabled in the SMC, it adds an entry to the settings table in the eB database.
The following SQL should give you the ftrdsn value:
SELECT a.* FROM settings a, setting_defs bWHERE a.setting_id = b.setting_idAND b.code = 'FtrDatasource'
It’s the value that can be found on the FTR property screen (SMC->Servers->[Server]->FTR) where youselect/define the catalog.
As well as updating an entry in the eB database, a new‘linked server’ is created in the SQL Server Management Studio.
The catalog within indexing service is created manually. If you highlight indexing Service within Computer management, you can see that there are columns confirming the total number of docs and the docs to index:
By adding files to an FTR enabled class you should be able to gauge whether the indexing is running, as the numbers of docs should increase.
When an FTR search is performed, it searches the linked server which in turn will link to the indexing service catalog. As the creation of the Indexing Service Catalog on the database server is a manual process, it is possible that the name of the catalog has been misspelt.
If this happens then eB will be trying to contact the name of the Indexing Service Catalog which will not actually exist. And an error in the UI similar to the following may be experienced.
An error occurred while trying to run the report.
Special characters and stop words are not supported in a FTR search. Please remove then and rerun the search. e.g. ~ ! @ # $ % ^ & * ( ).....
Cannot execute the query "SELECT filename FROM SCOPE() WHERE CONTAINS ('FIND')" against OLE DB provider "MSIDXS" for linked server......
So when an FTR query is run in an eB UI, the following query is run on the database. To test that indexing is working outside of eB, you can therefore run the following in the SQL Server Management Studio.
Replace “eBFTR_Insight2010” with your search catalog name (linked server name) and “word” with the keyword you want to test
select * FROM OPENQUERY( eBFTR_Insight2010, 'SELECT filename FROM SCOPE() where CONTAINS(''word'')')
If everything appears to be working, except for PDF’s, then you may have hit one of the known issues. If the FTR Repository is on a UNC path, then the Adobe iFilter does not appear to work. There are alternative iFilters that can be purchased that do work. Although by no means of a Bentley recommendation, users have not experienced any issue with Foxit, but I am sure that there are plenty of others to choose from.