Intermittent outage in SharePoint 2013

Tanmoy Das 801 Reputation points
2021-07-14T09:48:34.083+00:00

Hi All,

We have a fairly large farm with 13 servers, 9 internal and 4 DMZ for internet sites.
recently, we have started noticing intermittent outages on the internet sites which are hosted in the 4 DMZ servers.
Those 4 DMZ servers are also query and index servers and there are other 3 internal servers as query and index. There is only one index partition.
In line with the outage, we have noticed

5586 - Unknown SQL Exception 121 occurred. Additional error information from SQL Server is included below.
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) in the DMZ servers

8313 - At the same time, noticed an error from the internal search servers to the DMZ servers.
A failure was reported when trying to invoke a service application: EndpointFailure
Process Name: w3wp
Process ID: 14300
AppDomain Name: /LM/W3SVC/1246846138/ROOT-1-132706669482484185
AppDomain ID: 2
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:71c626cf6dfe4a298182ecc7392cdf8d#authority=urn:uuid:cee57e4ce01d46fc996b0a48797396f1&authority=https://xxxxxx:32844/Topology/topology.svc
Active Endpoints: 8
Failed Endpoints:1
Affected Endpoint: http://yyyyyy:32843/71c626cf6dfe4a298182ecc7392cdf8d/SearchService.svc

Any idea what could be the possible issue? Can it be related to the firewall or LB?
Why internal query and index servers are trying to communicate with the external DMZ servers using search endpoints, is it because of querying the index partitions in the DMZ servers?

Thanks

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,819 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. CaseyYang-MSFT 10,321 Reputation points
    2021-07-15T03:26:49.61+00:00

    Hi anonymous user,

    Per my research, This issue:"A transport-level error has occurred when receiving results from the server." occurs if the application can't connect to the server. You could try the following steps to troubleshooting.

    1.Make sure that TCP/IP is enabled as a client protocol on the application server.
    2.Check the application's connection string to make sure it's configured correctly.
    3.Try increasing the connection timeout value.
    4.Test the connectivity between the application server and the Azure SQL Database by using SQL Server management Studio (SSMS), a UDL file, ping, or telnet.
    5.As a best practice, make sure that the retry logic is in place.

    For Reference:
    https://learn.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-errors-issues#steps-to-fix-common-connection-issues

    And to solve this error:"A failure was reported when trying to invoke a service application: EndpointFailure". You could try to create a new Application.

    IIS Manager > right click SharePoint Web Services > add application... > copy the full id in the url and add it in Alias > "C:\Program Files\Microsoft Office Servers\15.0\WebServices\SearchService" in Physical path

    For more detials:
    https://gai3kannan.wordpress.com/2015/04/15/a-failure-was-reported-when-trying-to-invoke-a-service-application-endpointfailure-solution-step-by-step/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    If an Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.