The exceptions you are encountering with NodeRunner.exe in your SharePoint 2019 Farm can be attributed to several potential issues:
- Access Violations: The exception code
0xc0000005indicates an access violation, which typically occurs when the application tries to access memory that it is not permitted to. This can be caused by bugs in the application code or issues with the underlying system libraries. - Unhandled Exceptions: The exception code
0xe0434352signifies an unhandled Common Language Runtime (CLR) exception, which suggests that there is a .NET exception occurring in the application. This could be due to various reasons, including coding errors or misconfigurations. - Out of Memory: The
System.OutOfMemoryExceptionindicates that the application is trying to allocate more memory than is available. This can happen if the application is processing large datasets or if there are memory leaks in the application. - Stack Overflow: The exception code
0xc00000fdindicates a stack overflow, which usually occurs due to infinite recursion in the code. This can be caused by a logic error that leads to a function calling itself indefinitely.
How to Fix:
- Update Software: Ensure that your SharePoint and all related components are updated to the latest versions. This can often resolve bugs that lead to such exceptions.
- Review Application Logs: Check the SharePoint ULS logs for more detailed error messages that can provide insights into what might be causing these exceptions.
- Monitor Memory Usage: Use performance monitoring tools to track memory usage of the
NodeRunner.exeprocess and identify if there are memory leaks or excessive memory consumption. - Debugging: If you have access to the source code, consider debugging the application to trace where the exceptions are being thrown. This can help identify the root cause of the issues.
- Configuration Review: Double-check the configuration settings for your SharePoint environment, especially those related to the Search Service Application, to ensure they are correct and optimal.
By addressing these areas, you should be able to mitigate the exceptions generated by NodeRunner.exe in your SharePoint environment.
References: