Monthly Archives: May 2013

Fix: SharePoint Designer 2013: The server could not complete your request. For more specific information, click the Details below.


I found this issue in SharePoint Designer 2013 when accessing your SharePoint sites. It will pops up below message box repeatedly until I force to kill the SPDESIGN.EXE from the Task Manager. The message “The server could not complete your request. For more specific information, click the Details button.” is very vague and does NOT tell you what is the root of error.



When you click Details button, it does NOT any information as well.




It’s a simple solution if you know it. Enabling Anonymous Authentication for your SharePoint Web Application in IIS Manager will solve the issue. Microsoft site has further explanation on  the issue and can be found here.


Fix: NodeRunner.exe processes consume lots of RAM (memory) and CPU

I started SharePoint 2013 development recently. Initially, I only got dual core CPU and 4 GB RAM and as you probably know, it runs very slow. I’m not curious about it cause I expect the performance when you install SharePoint 2013 with less than minimum recommended hardware specification.


Then .. I fed up with it and upgrade the RAM to 8 GB, but funny things my development box is still runs very slow. I looked into my task manager and found something like below. Several NodeRunner.exe processes consume lots of Memory and CPU.



  1. Open SharePoint 2013 Management Shell and type in:
    Set-SPEnterpriseSearchService -PerformanceLevel Reduced
  2. Open NodeRunner process configuration file below in Notepad
    C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config.
    Update <nodeRunnerSettings memoryLimitMegabytes=”0″ />.
    This is the configuration to limit NodeRunner process memory usage, replace 0 to acceptable number like 100 or 150.
  3. Restart SharePoint Search Host Controller service.


NOTE: I’ve found out doing the step above will cause an issue (look my experience in provisioning search service application post) when you provision Search Service Application. Therefore, DO NOT DO IT to Production farm. Otherwise, if you have to limit the node runner process, limit it to 1024 MB.


Fix: Attempted to use an object that has ceased to exist.

Last week, I faced this issue for few hours trying to fix this issue since the error message is a bit generic and does not tell you which object that has been ceased. It is difficult to drill down the root of the issue.

The issue will look like this:



In my scenario, I used SPContext object to initialise SPSite object in using statement.

When the code goes outside using scope statement, it will dispose SPContext which is NOT acquired back.

using (SPSite site = SPContext.Current.Site)
   using (SPWeb web = site.RootWeb)
      // your custom code


Update your code to look like below:

using (SPSite site = new SPSite(SPContext.Current.Site.Url))
   using (SPWeb web = site.RootWeb)
      // your custom code
%d bloggers like this: