SharePoint 2013 Error: Unexpected response from server. The status code of response is '500'. The status text of response is System.ServiceModel.ServiceActivationException.
Usually this occures due to server is running out of Memory
You can fix it by reducing the Search service Performance or you can limit the Node runner
Solution 1.
Reduce the Search Service Performance
PS : Set-SPEnterpriseSearchService -PerformanceLevel Reduced
If this does not solve the problem then you can opt for Solution 2.
Solution 2.
There is a configuration setting for NodeRunner.exe’s configuration file that can limit RAM usage of a single process to specific value in megabytes. his configuration file is located at: C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config.
<!-- Settings enforced by the node runner itself. -->
<!-- These settings can also be set using command line arguments with the same name. -->
<nodeRunnerSettings memoryLimitMegabytes="0" />
The configuration setting is under the nodeRunnerSettings node and it’s called memoryLimitMegabytes. Its default value is 0 (unlimited).
Set it to 50 or 100 and save the file. After that restart the Sharepoint Search Host Controller Service.
This will resolve the issue.
Note : Solution 2 is not recommended approach by Microsoft.
Usually this occures due to server is running out of Memory
You can fix it by reducing the Search service Performance or you can limit the Node runner
Solution 1.
Reduce the Search Service Performance
PS : Set-SPEnterpriseSearchService -PerformanceLevel Reduced
If this does not solve the problem then you can opt for Solution 2.
Solution 2.
There is a configuration setting for NodeRunner.exe’s configuration file that can limit RAM usage of a single process to specific value in megabytes. his configuration file is located at: C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config.
<!-- Settings enforced by the node runner itself. -->
<!-- These settings can also be set using command line arguments with the same name. -->
<nodeRunnerSettings memoryLimitMegabytes="0" />
The configuration setting is under the nodeRunnerSettings node and it’s called memoryLimitMegabytes. Its default value is 0 (unlimited).
Set it to 50 or 100 and save the file. After that restart the Sharepoint Search Host Controller Service.
This will resolve the issue.
Note : Solution 2 is not recommended approach by Microsoft.
No comments:
Post a Comment