Fail to add Managed Property

When adding additional crawled property to Fast search, the search properties file may not pick up the additional addon.

As an example, add an selected DB column on the crawling file. Do an incremental crawl. From the test search page: http://localhost:13280, do a simple search, fields displayed should contain managed property with or without retrieved data. If there is no such an addon property, then there is a issue to your query server.

First check if the managed property has been added to and mapped to the crawled property, then start a crawl.

Additional checks on Index schema. The Index Schema defined in SharePoint Central Administration at the Query SSA's FAST Search Administration section is stored in SQL Server, and deployed to FAST Search through a timer job. It's possible that not all steps of the deployment occur, leading to a newer schema in SharePoint / SQL than the FAST qrserver is using.

To resolve it restart the QR server:
nctrl stop qrserver qrproxy search-1
nctrl start qrserver qrproxy search-1

nctrl restart qrserver

If you ever an error like this: Property doesn't exist or is used in a manner inconsistent with schema settings.

If the files are in place on the FAST Admin node, they can also be pushed to the query servers by running the following in a command prompt at the %FASTSEARCH%\index-profiles directory:

bliss -C deployment-ready-index-profile.xml

Ultimately, the deployment from the configuration stored in SQL can be restarted by opening the FAST Search Server PowerShell and running:

$allmp = Get-FASTSearchMetadataManagedProperty
$firstmp = $allmp[0]
$firstmp.Update()
This will republish the Index Schema without any changes.

If in the search results, you see there are "BADHITS",

The messages generally indicate that files created during an index-profile update have not updated properly, thus causing inconsistency on the system.

To determine if the files were incorrectly generated by the configserver, do the following:

Stop FAST ESP (nctrl stop).
Clear the contents of %FASTSEARCH%\var\searchctrl\etc\* and %FASTSEARCH%\var\etc\*. (The files will be regenerated.)
Start FAST ESP (nctrl start).

After the crawled items are processed, they are stored in an XML-based format (FiXML files). The indexer uses the FiXML files as input to the indexing process.

The indexeradmin resetindex command re-builds the content index from the FiXML files. This is normally needed only if the content index files are corrupted or damaged.