hybrid federated search from SharePoint Server to SharePoint Online inconsistent search result

%3CLINGO-SUB%20id%3D%22lingo-sub-1037962%22%20slang%3D%22en-US%22%3Ehybrid%20federated%20search%20from%20SharePoint%20Server%20to%20SharePoint%20Online%20inconsistent%20search%20result%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1037962%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22body%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20configured%20hybrid%20federated%20search%20from%20SharePoint%20server%20to%20SPO.%20It%20works%20but%20we%20are%20experiencing%20a%20strange%20behavior.%20When%20we%20do%20a%20search%20from%20the%20search%20center%20(SP%20on-prem)%20from%20time%20to%20time%20we%20need%20to%20press%20search%20several%20times%20in%20order%20to%20get%20a%20search%20result%20from%20SPO.%3C%2FP%3E%3CP%3EI%20have%20traced%20it%20down%20in%20the%20ULS%20and%20see%20the%20following%20entry%20every%20time%20when%20the%20search%20fail%20to%20get%20a%20result%20from%20SPO%3A%3C%2FP%3E%3CP%3ENodeRunner.exe%20(0x1C08)%26nbsp%3B%26nbsp%3B%20%26nbsp%3B0x24F4%26nbsp%3B%26nbsp%3B%20%26nbsp%3BSharePoint%20Server%20Search%26nbsp%3B%26nbsp%3B%20%26nbsp%3BQuery%26nbsp%3B%26nbsp%3B%20%26nbsp%3Baqdw1%26nbsp%3B%26nbsp%3B%20%26nbsp%3BMedium%26nbsp%3B%26nbsp%3B%20%26nbsp%3BQueryRouterEvaluator%3A%20Received%20results%20for%20already%20timed%20out%20query%20with%20query%20type%20ResultBlock%26nbsp%3B%26nbsp%3B%20%26nbsp%3B543aaf9c-0a9c-481a-9cfa-dda4fbcc4e5a%3C%2FP%3E%3CP%3EWe%20use%20SP2019%20with%20latest%20CU.%20We%20have%20this%20problem%20in%20two%20different%20environments%20on%202%20different%20o365%20tenants%20and%20data%20centers%20for%20SP%20on-prem.%20I%20have%20attached%20a%20trimmed%20ULS%20log.%20Where%20we%20can%20see%20the%20problem%20occur%202%20times%20and%20by%20the%203%20time%20the%20same%20search%20query%20is%20done%2C%20it%20works%20and%20SPO%20result%20is%20shown%20correctly.%3C%2FP%3E%3CP%3EAnyone%20experienced%20this%20problem%3F%3C%2FP%3E%3CP%3ERgds%20Martin%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1037962%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esearch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1443364%22%20slang%3D%22en-US%22%3ERe%3A%20hybrid%20federated%20search%20from%20SharePoint%20Server%20to%20SharePoint%20Online%20inconsistent%20search%20result%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1443364%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F471628%22%20target%3D%22_blank%22%3E%40Martin_Ericsson%3C%2FA%3E%26nbsp%3BDid%20you%20resolve%20this%20issue%3F%20I%20am%20trying%20to%20set%20up%20outbound%20hybrid%20federated%20search%20and%20I%20am%20getting%20this%20same%20timeout%20error%20in%20the%20ULS%20logs.%20In%20my%20case%2C%20I%20am%20trying%20to%20display%20the%20SP%20online%20search%20results%20in%20a%20result%20block%20and%20the%20majority%20of%20time%20they%20are%20not%20displayed%20at%20all%20and%20only%20the%20on-prem%20results%20are%20displayed.%20Were%20you%20able%20to%20track%20down%20the%20root%20cause%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1443417%22%20slang%3D%22en-US%22%3ERe%3A%20hybrid%20federated%20search%20from%20SharePoint%20Server%20to%20SharePoint%20Online%20inconsistent%20search%20result%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1443417%22%20slang%3D%22en-US%22%3EIn%20this%20procedure%2C%20you%20create%20a%20result%20source%20in%20the%20SharePoint%20Server%20deployment.%20This%20result%20source%20is%20a%20definition%20that%20specifies%20SharePoint%20Online%20as%20a%20provider%20to%20get%20search%20results%20from.%20This%20definition%20specifies%20each%20of%20the%20following%3A%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20SharePoint%20Online%20URL%20to%20get%20search%20results%20from%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20protocol%20for%20getting%20those%20results%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20method%20for%20authenticating%20against%20SharePoint%20Online%3CBR%20%2F%3E%3CBR%20%2F%3EResult%20sources%20can%20be%20created%20at%20the%20Search%20service%20application%20level%2C%20the%20site%20collection%20level%2C%20or%20the%20site%20level.%20In%20this%20procedure%2C%20you%20create%20the%20result%20source%20at%20the%20Search%20service%20application%20level.%20This%20will%20make%20the%20result%20source%20available%20to%20any%20query%20rule%20that%20is%20created%20at%20the%20same%20level%2C%20and%20also%20to%20any%20query%20rule%20that%20is%20created%20for%20a%20site%20collection%20or%20site%20that%20is%20in%20a%20web%20application%20that%20consumes%20the%20Search%20service%20application.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1443532%22%20slang%3D%22en-US%22%3ERe%3A%20hybrid%20federated%20search%20from%20SharePoint%20Server%20to%20SharePoint%20Online%20inconsistent%20search%20result%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1443532%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F493704%22%20target%3D%22_blank%22%3E%40Lewis-H%3C%2FA%3E%26nbsp%3BIn%20my%20case%2C%20the%20result%20source%20and%20the%20query%20rule%20seem%20to%20be%20configured%20correctly%20as%20it%20intermittently%20works%20properly.%20Also%2C%20if%20I%20do%20the%20opposite%20where%20the%20primary%20results%20are%20the%20online%20results%20and%20the%20result%20block%20displays%20the%20on-prem%20results%20then%20it%20works%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20a%20lot%20of%20components%20involved%20here%20and%20most%20of%20them%20are%20not%20easily%20accessible%20(on-prem%20search%20components%2C%20SP%20online%20search%2C%20etc.)%20to%20view%20exactly%20what%20is%20happening.%20I%20was%20interested%20in%20knowing%20what%20causes%20may%20have%20been%20found%20and%20what%20they%20used%20for%20troubleshooting.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,

I have configured hybrid federated search from SharePoint server to SPO. It works but we are experiencing a strange behavior. When we do a search from the search center (SP on-prem) from time to time we need to press search several times in order to get a search result from SPO.

I have traced it down in the ULS and see the following entry every time when the search fail to get a result from SPO:

NodeRunner.exe (0x1C08)    0x24F4    SharePoint Server Search    Query    aqdw1    Medium    QueryRouterEvaluator: Received results for already timed out query with query type ResultBlock    543aaf9c-0a9c-481a-9cfa-dda4fbcc4e5a

We use SP2019 with latest CU. We have this problem in two different environments on 2 different o365 tenants and data centers for SP on-prem. I have attached a trimmed ULS log. Where we can see the problem occur 2 times and by the 3 time the same search query is done, it works and SPO result is shown correctly.

Anyone experienced this problem?

Rgds Martin

3 Replies
Highlighted

@Martin_Ericsson Did you resolve this issue? I am trying to set up outbound hybrid federated search and I am getting this same timeout error in the ULS logs. In my case, I am trying to display the SP online search results in a result block and the majority of time they are not displayed at all and only the on-prem results are displayed. Were you able to track down the root cause?

Highlighted
In this procedure, you create a result source in the SharePoint Server deployment. This result source is a definition that specifies SharePoint Online as a provider to get search results from. This definition specifies each of the following:

The SharePoint Online URL to get search results from

The protocol for getting those results

The method for authenticating against SharePoint Online

Result sources can be created at the Search service application level, the site collection level, or the site level. In this procedure, you create the result source at the Search service application level. This will make the result source available to any query rule that is created at the same level, and also to any query rule that is created for a site collection or site that is in a web application that consumes the Search service application.
Highlighted

@Lewis-H In my case, the result source and the query rule seem to be configured correctly as it intermittently works properly. Also, if I do the opposite where the primary results are the online results and the result block displays the on-prem results then it works fine.

 

There are a lot of components involved here and most of them are not easily accessible (on-prem search components, SP online search, etc.) to view exactly what is happening. I was interested in knowing what causes may have been found and what they used for troubleshooting.