How to fix request timed out error in SharePoint 2016 search (There was no endpoint listening)

[Fixed]: How to fix request timed out error in SharePoint 2016 search (There was no endpoint listening)?

No comments

 44,073 total views,  9 views today

How to solve Google web stories amp...
How to solve Google web stories amp error and indexing problem solved

In this troubleshooting technique, we will learn about how to fix the request timed out error in SharePoint 2016 search.

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 athttp://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:
https://blogit.create.pt/fabiocarvalho/2017/02/14/sharepoint-2016-tcpip-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:

PDF Download Image

Download SharePoint Online & Office 365 Administration eBook

Buy the premium version of SharePoint Online & Office 365 administration eBook from here:



Buy SharePoint Online & Office 365 Administration eBook


 

Get the free demo PDF eBook from here:

FREE DOWNLOAD

Send download link to:

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.

 

About Post Author

Do you have a better solution or question on this topic? Please leave a comment