Share via

Search Crawl stuck in "Crawl Completing" state

Gulsan Kemberley 40 Reputation points
2026-02-10T04:22:43.9566667+00:00

Our SharePoint Server 2019 Farm (4-tier architecture) is experiencing a total stall in search indexing. After the application of the October 2025 Cumulative Update, all "Incremental" and "Full" crawls transition to a "Crawl Completing" status and remain there indefinitely. This has led to the Search Index becoming stale and the "Search Service Application" reporting a "Degraded" status in Central Administration.

The Crawl Component logs indicate a failure in the communication between the Crawl Component and the Content Processing Component. We have verified that the Search Host Controller service is running, but the ULS logs show a persistent SocketException when attempting to commit the index to the disk.

Category: Search
EventID: d96a
Level: Critical
Message: "An error occurred in the Search Component: 
Microsoft.Ceres.ContentEngine.Processing.ContentProcessorException: 
The crawl could not be completed because the link between the Index 
and the Content Processing component was severed. 
Exception: System.ServiceModel.EndpointNotFoundException: 
The request to 'net.tcp://1/Ceres/Search/Index' timed out."

Any help ?

Microsoft 365 and Office | SharePoint Server | Development
0 comments No comments
{count} votes

Answer accepted by question author
  1. Jack-Bu 6,370 Reputation points Microsoft External Staff Moderator
    2026-02-10T06:12:34.0466667+00:00

    Hello Gulsan Kemberley

    Thank you for reaching out to Microsoft Q&A.

    I notice that the request is timed out, can you please double check if the connection to port is working. Test-NetConnection (NetTCPIP) | Microsoft Learn

    Test-NetConnection -ComputerName <> -Port <>
    

    You can also check Content Processing and Index components are still functioning.

    Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchStatus -Text
    

    This retrieves a list of information about all search components of the default Search Service Application. Get-SPEnterpriseSearchStatus (Microsoft.SharePoint.Powershell) | Microsoft Learn

    Look for the components and check their status.

    Additionally, you can try these steps:

    Pause crawling

    $ssa = Get-SPEnterpriseSearchServiceApplication 
    Suspend-SPEnterpriseSearchServiceApplication $ssa 
    

    Restart Search services:

    Restart-Service OSearch16 
    Restart-Service SPSearchHostController 
    

    Clone an active topology: This avoids a full rebuild.

    $ssa = Get-SPEnterpriseSearchServiceApplication 
    $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active 
    $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone -SearchTopology $active 
    Set-SPEnterpriseSearchTopology -Identity $clone 
    

    Wait until Get-SPEnterpriseSearchStatus shows all components = Active.

    Then resume crawling:

    Resume-SPEnterpriseSearchServiceApplication $ssa 
    

    I also see that there is new CU, you can consider update to the latest version.

    SharePoint updates - Office release notes | Microsoft Learn

    I look forward for your reply.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.