Wednesday, June 26, 2013

SharePoint Developer is not able to link and mistake information is blank

When trying to link using SharePoint Designer 2010 to a SharePoint 2010 hosting server that is low on available physical RAM, you may receive the mistake “The hosting server could not complete your request”, despite the fact that the site is still running via the web browser.


The server could not complete your request.

However, the details offered in the “Details” area are anything but useful, as it is absolutely vacant.


Blank error dialog

Using a smelling system such as Fiddler2 or Wire shark to look at the demands that are being sent to the hosting server shows that the following POST declaration is getting an HTTP 500 error:

POST http://site.com/_vti_bin/client.svc/ProcessQuery HTTP/1.1
HTTP/1.1 500 System.ServiceModel.ServiceActivationException

Browsing directly to the webservice then reveals the true root of the issue:
Memory gates checking failed because the free memory is less than 5% of total memory.
“Memory gates checking failed because the free memory is less than 5% of total memory.  As a result, the service will not be available for incoming requests.  To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.”
SharePoint Designer can hit a server quite hard with a large number of very resource-expensive requests, so this memory gate protects an already heavily-loaded server from getting pushed over the edge, causing it to start returning errors in normal user-space.  While it does give a setting to change as a workaround, this is not the correct solution, as it puts the stability of the environment at risk.  Either find out what is burning so much RAM, do what you can to offload heavy applications or services to other machines, or bite the bullet and add more RAM. Memory gates checking failed because the free memory (539389952 bytes) is less than 5% of total memory.  As a result, the service will not be available for incoming requests.  To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.

No comments:

Post a Comment