Skip to main content

SharePoint 2013: Unexpected response from server issue and how to fix

From time to time when you do some operations such as search using SharePoint 2013 you may see the following error:

Unexpected response from server. The status code of response is ’500′. The status text of response is ‘System.ServiceModel.ServiceActivationException’



After having this issue on newly installed SharePoint 2013 farm in production environment, I figure it out that Single server is running out of memory. Especially, thanks to one new process noderunner.exe.

Noderunner.exe is the new executable of search service on SharePoint 2013. This process can’t turn it off because Search is one of essential service application in SharePoint 2013, and it is integrated in many features. So, there are some things you can do to reduce the impact of Search on your system.

Solution 1
Reduce the Search Service Performance Level with this PowerShell command:
Set-SPEnterpriseSearchService -PerformanceLevel Reduced
or
Set-SPEnterpriseSearchService -PerformanceLevel PartiallyReduced, which is in between reduced and Maximal

Solution 2
Limit the Memory Footprint of NodeRunner.exe is one thing that is not so recommended. 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.  This configuration file is located at: C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config.  The configuration setting is under the nodeRunnerSettings node and it’s called memoryLimitMegabytes.  Its default value is 0 (unlimited).  Every time you change it, you’ll need to restart all of the noderunner.exe processes.
Labels:

Comments

Post a Comment

Popular posts from this blog

A Step-by-Step guide to use HttpModule in SharePoint with SPContext

I guess you must be familiar with what is HttpModule and how can we leverage it for our web applications. But if not, better have a good read of this article . SharePoint is built on top of .NET, so it has all the rights to use the beauties of .NET. Here I want to demo a simple case of httpmodule on SharePoint. Say if in a company it has lots of site collections and user 'Picky Docky' has access for all of them, for a reason farm administrator want to block him for one of the specific site without change his SharePoint permissions. Here are the steps to do it:-)   Create a empty SharePoint solution add a class file to it named  CustomSecurityModule.cs , code as below Create a feature and scope to "WebApplication" Create a feature receiver. Code as below When activate the feature it will create a modle in the web.config file for the SharePoint web applicaiton you deployed to as below: Enjoy!
2 comments
Read more

SharePoint 2013 online Parent/Child relationship - A step by step demo

SharePoint uses lookup fields to represent the Parent-Child relationship. For child list items it is OK as you can trace back to its parent from the lookup field. For parent the OOB forms are not good enough as they are not displaying the children belong to it. In real world it is often required that when view the parent list item it also displays its children, further more it is great if user can add child list items directly from the parent. In SharePoint on-premise we can use visual web parts and code the parent/child logic and use web part pages to replace the parent item forms. In SharePoint online we can't do server model code and visual web parts, so the solution is almost NO CODE and just a little bit client side scripts, and they work beautifully! Here I will do a step by step demonstration to explain the ideas:   Step 1: Create a parent list called "Category" and a child list called "Product", in Product list add a lookup field to reference Cat...
7 comments
Read more

SharePoint search on local file drive - Why and How

A team member asked me why in some situation we need to use SharePoint search on local file drive as we can do 'search' directly on the folder in windows. I think it is necessary to do some research to show why and why the benifit is to do this. And more importantly - HOW.   WHY? If you've played around with SharePoint local file search the answer is straight-forward: You can let it search multiple local file drives, but using windows you can hardly do this. SharePoint can search 'into' the real content even the keyword is in content of files in zip file . See the comparison I did a search for keyword 'issue':   Window built-in search: SharePoint search: SharePoint search can easily filter the result by type/date etc. SharePoint can show a bit of content from the files found to give a bit more indication. ... HOW  It's hard to find a step-by-step guide talking about how to make it work. That's why here I am:-)   Go to the f...
Post a Comment
Read more