Forum Discussion
SharePoint Server Subscription Edition Search indexing component crashing
Hello,
I installed SharePoint Server Subscription Edition on Windows Server 2022 (standard with desktop experience) and the search service crawling is failing.
The server has 32GB ram.
The MS SQL Server 2022 runs on a separate server, on Windows Server 2022.
I installed the SharePoint update from April 2024, and ran the SharePoint products configuration wizard.
I already applied the 4 security policies as described in the article https://learn.microsoft.com/en-us/sharepoint/troubleshoot/search/parser-server-failed-to-start
I have these errors in the crawl log:
The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = ..... )
The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; ; SearchID = ..... )
In windows event log I have these errors:
Application: NodeRunner.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Microsoft.Ceres.SearchCore.FastServer.Plugin.CreateIndexer()
at Microsoft.Ceres.SearchCore.Indexes.FastServerIndex.GenerationBuilder.EnsureIndexerOpen()
at Microsoft.Ceres.SearchCore.Indexes.FastServerIndex.GenerationBuilder.AddDocument(Microsoft.Ceres.SearchCore.Services.Indexes.FastServerIndex.MdmOperation)
at Microsoft.Ceres.SearchCore.ContentTargets.IndexRouter.IndexBuilderAdder.DoWorkIteration()
at Microsoft.Ceres.Common.Utils.Concurrent.AbstractWorker.Run()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Faulting application name: NodeRunner.exe, version: 16.0.17328.20136, time stamp: 0xc5aeb836
Faulting module name: ntdll.dll, version: 10.0.20348.2400, time stamp: 0x9c244209
Exception code: 0xc0000005
Fault offset: 0x000000000001bdd0
Faulting process id: 0x337c
Faulting application start time: 0x01daa12b85bf944f
Faulting application path: E:\Program Files\Microsoft Office Servers\16.0\Search\Runtime\1.0\NodeRunner.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b34c76ee-a339-4b14-9a24-b6e2f53344cf
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: NodeRunner.exe, version: 16.0.17328.20136, time stamp: 0xc5aeb836
Faulting module name: ntdll.dll, version: 10.0.20348.2400, time stamp: 0x9c244209
Exception code: 0xc0000005
Fault offset: 0x000000000001bdd0
Faulting process id: 0x383c
Faulting application start time: 0x01daa12bbc509dc8
Faulting application path: E:\Program Files\Microsoft Office Servers\16.0\Search\Runtime\1.0\NodeRunner.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 70f2a049-2211-4f2f-aac5-c3c0d9c9e168
Faulting package full name:
Faulting package-relative application ID:
Thank you in advance.
2 Replies
- ErwanBCopper Contributor
Hello Adrian,
I am facing the exact same issue event after unstalling the CU from Augsut 2025.
Did you manage to solve the issue on your environment ?
Thank you
- Adrian-Sergiu NicutaCopper ContributorDoes anyone know is we can debug the noderunner.exe, with debug symbols downloaded from Microsoft?