Friday, August 17, 2012


My SP2013 server was getting slower and slower and I could not even create a site collection anymore, so I looked into Task Manager and the processes. Found a new one, noderunner.exe, and it was consuming a lot of CPU

That process is the Search service, with a new process name. Restarted the SharePoint Search Host Controller service and the performance looked a bit healthier after that


Anonymous said...

Thanks for this. I have been experiencing the same problem. If I leave the SharePoint server long enough all of the ram is eventually consumed.

Sridhar said...

Thanks this helped

Praveen said...

This is the bug in SharePoint 2013 and I have written the solution on the same here:

Hope it helps to solve the problem for now.

Lise Rasmussen said...

Thanks Praveen :)