Follow Me

Never install SharePoint 2013 on a Domain Controller

By Stefan Feenstra   /     Jul 18, 2013  /     SharePoint 2013  /     , , , ,

Please keep in mind when you want to create a Single Server installation of SharePoint 2013 that you don’t install SharePoint 2013 on a Domain Controller. Some features of SharePoint 2013 don’t work when you install it on the Domain Controller. Today I found one:

When I tried to activate my Sandboxed Solution on my single server SharePoint 2013 installation it failed with the following error:

An attempt to connect to the remote activator failed with exception 'System.Runtime.Remoting.RemotingException: Cannot resolve 'channel' template reference: 'http client'.

An attempt to connect to the remote activator failed with exception ‘System.Runtime.Remoting.RemotingException: Cannot resolve ‘channel’ template reference: ‘http client’.

Then I tried to activate the same solution on a SharePoint 2013 installation with a seperate domain controller server and it worked! And when you leave the feature event receiver commented out it’s also working on the single server installation.

3 Comments

  1. Luis Says: 17-04-2014 10:40

    Thank you Stefan, I got this error today and I was wondering if it was my solution’s code or just a sh2013 error.

    Reply this comment
  2. Matthew Chestnut Says: 10-09-2014 22:25

    Strangely enough, this fixes the problem for me on SharePoint 2013 instance installed on a Windows Domain Controller:

    Set-SPLogLevel -Identity “SharePoint Foundation:Sandboxed Code Service” -TraceSeverity “Verbose”
    Restart-Service -Name “SharePoint User Code Host”

    Reply this comment
    • Matthew Chestnut Says: 11-08-2015 19:56

      But, the “set verbose logging” trick will not work with SharePoint 2013 under Windows Server 2012 R2 when it is a domain controller. It *does* work under Windows Server 2012 when it is a domain controller.

      Reply this comment

Post a Comment

Your email address will not be published. Required fields are marked *

*