After this error message there will be another error identifier like DM_FULLTEXT_E_BAD_SDC_PHRASE or DM_FT_INDEX_F_FULLTEXT_ENGINE_INIT_ERROR or some other.
Resolution of the problem depends on the error message we got. If we dont want the Full text search, then we can disable the full text search by editing the dfc.properties file at WDK application level.
Add the following line at the dfc.properties file
dfc.search.fulltext.enable = false
After changing the configuration, restart the app server and try the search again.
To resolve DM_FT_INDEX_F_FULLTEXT_ENGINE_INIT_ERROR or DM_FULLTEXT_E_BAD_SDC_PHRASE
Verify whether dm_attributemapping.xml file is present at the content server machine. If not get the file from somewhere else and put it in the fast40 directory.
To update:
API>retrieve,c,dm_ftengine_config
API>set,c,l,param_value[18]
SET>"Whatever correct path in your env to the dm_AttributeMapping.xml"
API>save,c,l
API>reinit,c
Restart docbase.
Note: If we upgraded the docbase from 6.5 to 6.6, update param_value[5] instead of param_value[18]