This issue may occur when the exassrch.exe or xvsrch.exe cannot be started on one or more Native Archive servers. The search process may not start if it cannot allocate enough system memory or Query service shared memory.
Users can retry the search when the amount of search activity is reduced. It may help to break up the search into multiple parts. For example, if a search must be run for a ten-year date range, instead of a single search run two searches which each cover a span of five years serially.
If, the problem persists also check:
- Increase the amount of memory allocated by the Query service for search results. From the SourceOne Management Console go to the Native Archive node -> Server Configuration. For each server which has the "Search" role check the value of "Memory Allocated to Search Results (MB)." This value can be raised to a maximum of 500 MB. Restart the Query service on each Native Archive server where this change has been implemented.
- If the QueryMaxFTISearches setting has been changed, reduce the number of simultaneous search processes that can be run simultaneously on each Native Archive. Run the following query against the Native Archive database to return the current value used for each Native Archive server:
SELECT ServerName, ConfigXML.value('(/ExAsSrvCfg/QueryService/QueryMaxFTISearches)[1]','nvarchar(max)') AS QueryMaxFTISearches
FROM ServerInfo (NOLOCK)
WHERE ServerName
LIKE '%-%'ORDER BY ServerName
The default value is "6." If the value has been raised, it might need to be reduced to a lower value. See KB 529208 for instructions on updating the QueryMaxFTISearches setting.