none
Intermittent "The current operation timed-out after 15 seconds" Errors RRS feed

  • Question

  • I have been running into an issue with our SharePoint 2013 farm where search results will intermittently error out while displaying "The current operation timed-out after 15 seconds."  Digging into the ULS, I see that the logs shows the following message immediately after the 15 seconds: "Query router timed out after waiting for substrate query for 15000 ms."  In addition to this item, there are a handful of exceptions that also note they reached the timeout as well (e.g. Original error: System.ServiceProcess.TimeoutException: The current operation timed-out after 15 seconds) though none of them seem to give out any other information besides this.  I did try and edit the search results webpart to allow 60 seconds for the timeout (via the instructions found here: http://blog.metrostarsystems.com/2014/05/06/sharepoint-2013-search-results-webpart-timeout/), but the search results continue to timeout even after the 60 second time frame.

    This is the point where things get complicated.  These periods of working and not working will occur throughout the day.  Sometimes search will be working just fine.  Other times it will almost completely stop working except for a handful of search terms that always seem to return results.  At times a term will return results then later on return with the 15 second timeout.  There are also times where searching for a term yields the timeout but searching for the same term with an asterisk before it WILL return results (e.g. *term).  I have not noticed any patterns to the time of day or the behavior of what works and what doesn't.  At this point, I have the following questions:

    • What might be wrong with my search service?
    • Is there anything I should be looking for in the ULS or Event Viewer that might provide me with more information than exception messages about a timeout being reached?
    • Is there any way I might be able to reduce this issue down to one server or a subset of servers (say, the query processing component on a web front end) that might be causing issues, and if so, how?

    Some more information pertaining to the environment:

    • The farm contains five web front ends and three application servers (two of which provide indexing)
    • The total amount of searchable items is small (less than 30,000 items)
    • The search queries are not complex, 90% of the time they contain just a single search term

    • Edited by Wedge A Wednesday, March 2, 2016 7:48 PM Added 60 second timeout information
    Wednesday, March 2, 2016 7:46 PM

Answers

  • You probably need to check your search topology and need to apply few fixes to your farm to get best performance for search. 

    Instead of writing all of this here I am posting the links to few ignite sessions which will help you find out what's wrong.

    https://channel9.msdn.com/Events/Ignite/2015/BRK3176

    https://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC375?ocid=relatedsession


    Jerry Yasir - Office Server & Services MVP/MCT Hewlett Packard Enterprise - If this reply helped you resolve your issue, please propose as answer. It may help other community members. Thanks!

    Wednesday, March 2, 2016 10:43 PM

All replies

  • You probably need to check your search topology and need to apply few fixes to your farm to get best performance for search. 

    Instead of writing all of this here I am posting the links to few ignite sessions which will help you find out what's wrong.

    https://channel9.msdn.com/Events/Ignite/2015/BRK3176

    https://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC375?ocid=relatedsession


    Jerry Yasir - Office Server & Services MVP/MCT Hewlett Packard Enterprise - If this reply helped you resolve your issue, please propose as answer. It may help other community members. Thanks!

    Wednesday, March 2, 2016 10:43 PM
  • Hi Wedge,

    I am also facing this issue. Could you please let me know how can i increase the timeout for this?

    Can you please provide me the steps?

    Monday, October 9, 2017 9:18 AM