Hot answers tagged fast-search
Your understanding is not correct. So rule, if a crawl is running and schedule for another crawl schedule (Lets say full) on the same content source is approached then running crawl always took the priority & continue. Now Full crawl will be skipped and wait for the next schedule which is next week in your case. If you don't want to overlap them then i ...
When you do an index reset with FAST in central admin you also have to clear the content collection using powershell from one of the FAST servers. This ensures the crawl database and index are in sync.
Filter out all The queryable managed Properties from this list and you have all the default ones: https://technet.microsoft.com/en-us/library/jj219630.aspx Then there are all the autogenerated ones, which you can get my listing all queryable properties in you environment, UI or PowerShell.
As filetable stored the data on the fileshare then you can create the content source for file share and crawl the items from that location. how to configure the Search for fileshare read this. http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/07/01/how-to-configure-enterprise-search-to-index-a-file-share.aspx Another option i am thinking may ...
As the error suggests, increase the time out value from Search Administration Page Central Administration -> Manage Service Applications -> Search Service Application Farm Search Administration Timeout change value Another option is by changing the IE proxy settings Internet options Connections LAN Settings Uncheck Automatically detect Settings Save. ...
I would create a Scope that has these site collections listed as include rules. Then there is no need to remove the existing content source, the scope is just a subset of that index.
Only top voted, non community-wiki answers of a minimum length are eligible