[Fixed]: How to Fix Request Timed Out Error in SharePoint 2016 Search?

In this troubleshooting technique, we will learn about how to fix the request timed out error in SharePoint 2016 search (there was no endpoint listening). Before getting into the article, let us understand what a request timed-out error is in SharePoint in general or why we get this error.

What is Request timed out error in SharePoint?

A “Request timed out” error in SharePoint occurs when a user request to the SharePoint server takes longer than the server’s configured timeout setting. This error indicates that the server was unable to process the request within a reasonable timeframe, resulting in the termination of the connection. This issue can arise for various reasons, including server performance problems, network latency, or overly complex queries.

Common Causes of Request Timed Out Errors

1. Server Performance Issues:

   • High Load: When the SharePoint server is under heavy load due to numerous simultaneous requests or resource-intensive operations, it may fail to respond in time.
   • Insufficient Resources: Limited CPU, memory, or disk I/O resources can cause delays in processing requests.

2. Network Latency:

   • Slow Network Connections: Poor network performance between the client and the server can result in delays that exceed the server’s timeout settings.
   • Network Congestion: High traffic on the network can cause packets to be delayed or dropped, leading to timeouts.

3. Complex Queries:

   • Inefficient Queries: Large or complex queries, especially those involving extensive joins or large datasets, can take a long time to execute.
   • Large Data Transfers: Operations involving the transfer of large amounts of data, such as bulk uploads or downloads, can exceed the timeout threshold.

4. Configuration Issues:

   • Improper Timeout Settings: Server timeout settings that are too short may not allow enough time for certain operations to complete.
   • Custom Code: Custom solutions or web parts that are not optimized can cause long processing times.

Troubleshooting and Mitigation

1. Optimize Server Performance:

   • Resource Allocation: Ensure the server has adequate CPU, memory, and disk resources.
   • Load Balancing: Implement load balancing to distribute requests across multiple servers, reducing the load on any single server.

2. Improve Network Performance:

   • Reduce Latency: Optimize the network infrastructure to reduce latency and improve connection speeds.
   • Monitor Network Traffic: Use network monitoring tools to identify and address network congestion issues.

3. Optimize Queries:

   • Index Columns: Use indexed columns to speed up query performance in SharePoint lists and libraries.
   • Limit Data: Refine queries to retrieve only the necessary data, reducing the amount of data processed and transferred.

4. Adjust Timeout Settings:

   • Increase Timeout Limits: Modify the server timeout settings to allow more time for complex operations to complete.
   • Review Custom Code: Ensure any custom code or solutions are optimized for performance and do not introduce unnecessary delays.

Specific Solutions for SharePoint

1. Increase Execution Timeout for Web Applications:

   • Modify the web.config file for the SharePoint web application to increase the execution timeout value:
     xml

      

     <httpRuntime executionTimeout="3600" />

2. Optimize SharePoint Lists and Libraries:

   • Use list and library settings to manage large lists, such as enabling list throttling and configuring indexed columns.

3. Monitor and Diagnose with ULS Logs:

   • Use SharePoint’s ULS (Unified Logging Service) logs to identify the root cause of timeouts and address underlying issues.

By understanding and addressing the common causes of “Request timed out” errors, SharePoint administrators can improve the reliability and performance of their SharePoint environments, ensuring a smoother user experience.

Issue Description: Request timed out error in SharePoint 2016 Search (There was no endpoint listening)

Let’s say we have a multi servers farm where all web applications are hosted in WFE and all SharePoint services running in the App server. The server topology is as below:
1. App Server with Search and
2. WFE server.

We have configured the search service application in the application server all components of the search crawl happening fine without any errors. However, if we try to search any item from the SharePoint web application, the search box will try to continue to search the item but after a long time we will see the error “search query time out error timed”.

If we look at the ULS log, we can see the below entry:
:SearchServiceApplicationProxy::GetQueryHealthMonitoringSettingsForComponents–Error occurred: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at appserver:32843/db4796fcfe375bd791f98ec5e485999c/SearchService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because the connected host has failed to respond:32843 at System.Net.Sockets.Socket.DoConnect(EndPoint endpoint snapshots, SocketAddress socket address)

Solution: Request timed out error in SharePoint 2016 (There was no endpoint listening)

This is the port connectivity issue between WFE and APP server. Ask your system/network admin team to configure the 808,32843,32844 port in WFE and APP server.

Here is the link for SharePoint 2016 port details:
SharePoint 2016 – TCP/IP Ports

Summary: Request timed out error in SharePoint 2016 Search

Thus, in this troubleshooting technique, we have learned about how to fix request timed out error in SharePoint 2016 search.

See Also: SharePoint Online Tutorials

You may like the below SharePoint Online tutorials:

• Office 365: Getting started with SharePoint PnP PowerShell – installation
• In 2 steps convert a classic SharePoint page to modern using PnP
• Office 365: Retrieve hub sites and associated sites using PnP Powershell
• Create a modern team site using PnP PowerShell in SharePoint
• In 4 steps access SharePoint online data using postman tool
• SharePoint admin center: Learn SharePoint online administration in an hour – step by step
• SharePoint REST API: GET vs POST vs PUT vs DELETE vs PATCH
• Office 365: Understanding the hub site in SharePoint online
• Overview of search architecture in SharePoint Server

About Post Author

SP Maven

As a SharePoint and Power Platform Maven, my greatest joy comes from sharing my expertise with colleagues, friends, and the tech community, helping them navigate the ever-evolving world of technology and guiding them through the dynamic landscape of modern technology.

See author's posts