In my very new, lab install of SharePoint 2013 in Windows 2012, I get this error message when trying to post to the newsfeed

SharePoint returned the following error:

Unexpected response from server. The status code of response is '500'. The status text of response is 'System.ServiceModel.ServiceActivationException'. Contact your system administrator for help in resolving this problem.

So far, I have:

  • Checked that the ASPNetCompatibilityEnabled = true
  • Checked the memory (50% free memory).
  • Changed performance level (Set-SPEnterpriseSearchService -PerformanceLevel Reduced as mentioned here.
  • Disabled MDS (Disable-SPFeature -Identity 87294C72-F260-42f3-A41B-981A2FFCE37A -Url XXX).

Those changes haven't helped.

  • 1
    what about the Distributed cache? is Cache cluster up and running? try to reset it then test it.
    – Waqas Sarwar MVP
    Jun 5, 2014 at 21:08
  • 1
    @WaqasSarwarMCSE: Thanks. The Distributed Cache is running (I restarted it anyways). No luck. Is there any way to get more information in some log or something? the error message is really obscure.
    – rufo
    Jun 6, 2014 at 14:42
  • 1
    enable the verbose logging and then try to reproduce the issue.
    – Waqas Sarwar MVP
    Jun 6, 2014 at 14:49
  • Ok. That helped.
    – rufo
    Jun 6, 2014 at 19:21
  • you get more details about the error and are you able to fix it?
    – Waqas Sarwar MVP
    Jun 6, 2014 at 19:22

6 Answers 6


Got the same issue because of RAM is Full. so i restarted SQL Server that resolves my issue.

  • Just check your Developer tools Console (press F12 in broser)
  • for me it was calling the some SharePoint client.svc at below address http://XXXXXXX:82/Test/_vti_bin/client.svc/ProcessQuery

  • and when opened in the browser it was complaining about like below error

    A binding instance has already been associated to listen URI 

    http://XXXXXX:82/_vti_bin/client.svc. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config.

  • finnaly removing application and recreating on another port and attaching the WSS_contents resolved the problem


After following the suggestion to use verbose logging I found that

A failure was encountered while attempting to create the site, wildcard inclusion used to create personal sites does not exist

I added the wildcard on the site and now the newsfeed is working (still need to fix other things but this helped).

I used this information to setup the logging.


To add to the answer above, you can include the wildcard for the personal sites by doing the following:

Run Get-SPManagedPath -HostHeader

If this does not show

personal WildcardInclusion

in the results then enter the command

New-SPManagedPath -RelativeURL "personal" -HostHeader

Run Get-SPManagedPath -HostHeader again to ensure that that has been added

Full details can be found here


When I restarted "SharePoint Search Host Controller" service it worked for me. May be due to less space on "C" drive hard disk causes a issue.


I restarted "SharePoint Search Host Controller" in the services and it started working for me.

Before I restarted it, the memory utilization was 100% which was causing the issue

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.