locked
Installed Sharepoint 2013 Foundation on WIndow 2010 server -- Issues activating sandbox solutions RRS feed

  • Question

  • I have several Sharepoint 2010 Foundation solutions(wsps).   They activate withou issues in Office/365 sites that have been upgraded to Sharepoint 2013 (although I am told its not exactly Sharepoint 2013 but close).   However on a new Sharepoint 2013 Foundation site I installed on a Windows Server 2012 server I can not activate these solutions (although there are other simpler wsp that I could activate).

    The activation error is Sorry Something went wrong. unknown exception in sandbox worker process.  Here is the ULS log trace

    -  - An unknown exception occurred while executing a sandboxed code solution request in the worker process.\r\n|0 - userCodeWrapperType.FullName = "Microsoft.SharePoint.UserCode.SPUserCodeFeatureCallOutWrapper", userAssemblyGroup = ".UserCodeAssemblyGroupId = ", GroupId = "5CC4316D56C049059A2B3F8A2DF77937-64H18khiUct086o7UWw5NISbr1upFDAyV9bSukL+QXk="", .RootDirectoryPath = "C:\ProgramData\Microsoft\SharePoint\UCCache\8CF9F53D8AAFD55\5CC4316D56C049059A2B3F8A2DF77937%2D64H18khiUct086o7UWw5NISbr1upFDAyV9bSukL%2BQXk%3D-2"", siteCollectionId = a09390a5-6ab3-42f7-bd76-b927f57c838a - Inner Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.Remoting.RemotingException: An attempt to connect to the remote activator failed with exception 'System.Runtime.Remoting.RemotingException: Cannot resolve 'channel' template reference: 'http client'.   
     at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ReportUnableToResolveTemplateReferenceError(ConfigNode node, String referenceName, RemotingXmlConfigFileData configData)   
     at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ProcessChannelsChannelNode(ConfigNode node, RemotingXmlConfigFileData configData, Boolean isTemplate)   
     at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ProcessChannelsNode(ConfigNode node, RemotingXmlConfigFileData configData)   
     at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ProcessApplicationNode(ConfigNode node, RemotingXmlConfigFileData configData)   
     at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ParseConfigNode(ConfigNode rootNode)   
     at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ParseDefaultConfiguration()   
     at System.Runtime.Remoting.RemotingConfigHandler.LoadMachineConfigIfNecessary()   
     at System.Runtime.Remoting.RemotingConfigHandler.FindDelayLoadChannelForCreateMessageSink(String url, Object data, String& objectURI)   
     at System.Runtime.Remoting.RemotingServices.CreateChannelSink(String url, Object data, IMessageSink& chnlSink)   
     at System.Runtime.Remoting.RemotingServices.Unmarshal(Type classToProxy, String url, Object data)   
     at System.Runtime.Remoting.Activation.LocalActivator.DoRemoteActivation(IConstructionCallMessage ctorMsg)'.   
     at System.Runtime.Remoting.Activation.LocalActivator.DoRemoteActivation(IConstructionCallMessage ctorMsg)   
     at System.Runtime.Remoting.Activation.LocalActivator.Activate(IConstructionCallMessage ctorMsg)   
     at System.Runtime.Remoting.Messaging.ClientContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)   
     at System.Runtime.Remoting.Activation.ActivationServices.Activate(RemotingProxy remProxy, IConstructionCallMessage ctorMsg)   
     at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg)   
     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)   
     at Microsoft.SharePoint.SPSite_SubsetProxy..ctor()     -
     -- End of inner exception stack trace ---    Server stack trace:    
     at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)   
     at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)   
     at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)   
     at System.Activator.CreateInstance(Type type, Boolean nonPublic)   
     at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)   
     at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)   
     at System.Activator.CreateInstance(Type type, Object[] args, Object[] activationAttributes)   
     at Microsoft.SharePoint.SPSite.__CreateInstance_SPSite(Boolean forStaticMethod, Object[] constructorParameters)   
     at Microsoft.SharePoint.SPSite.RegisterCallContextUserCodeToken__Inner(Byte[] userCodeToken)   
     at Microsoft.SharePoint.SPSite.RegisterCallContextUserCodeToken(Byte[] userCodeToken)   
     at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.SetBinaryTokens(Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)   
     at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)   
     at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)   
     at Microsoft.SharePoint.UserCode.SPUserCodeAppDomain.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)   
     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxyForShim.ExecuteInternal(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)   
     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxy.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)   
     at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)   
     at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)    Exception rethrown
     at [0]:    
     at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)   
     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)   
     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.ExecuteDelegate.EndInvoke(IAsyncResult result)   
     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String currentAffinity, SPUserCodeExecutionContext executionContext)


    Earllibby

    Monday, December 3, 2012 10:26 PM

Answers

  • Again, installing SharePoint 2013 on a DC is not supported.  If you've installed it this way for production, you'll need to move your SharePoint 2013 installation to a separate server.

    SharePoint - Nauplius Applications
    Microsoft SharePoint Server MVP
    MCITP: SharePoint Administrator 2010

    -----------------------
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Marked as answer by earllibby Saturday, March 2, 2013 5:16 PM
    Saturday, January 26, 2013 8:26 PM
    Moderator

All replies

  • Hi,

    Have exactly the same issue. But in my case I suppose it's the single server installation issue (SharePoint 2013 on DC). What environment do you have?

    Saturday, January 19, 2013 1:43 PM
  • I have also encountered the same issue. I noticed a few more things . This happens only for sandbox solutions with features that have event receivers (I have also tested the same scenario with a blank solution with one feature with event receiver). For some reason, the SPUC service fails to load the assembly of the sandbox solution. (see details at the end of post)

    The environment where this happened was also a single server installation(SP 2013, Win Server 2012 on DC), but configured under a single account.

    I have tested the same solution on a different environment (SP 2013, Win Server 2008 R2 on DC), but configured properly with several accounts - SP_Services,SP_Admin,SP_Farm,SP_PortalAppPool,SP_ProfilesAppPool,SP_Search etc.

    Here - it works just fine!.

    Therefore, it must be a configuration/ environment issue, but I still haven't found the exact cause of the problem. Any ideas?

    Here are some logs from the same correlation, that occur before the RemotingException:

    Failed to load receiver assembly "{assemblyname}" (ID: 84272442-4750-4133-b1cd-4c7d028b1080).: System.IO.FileNotFoundException: Could not load file or assembly '{assemblyname}' or one of its dependencies. Das System kann die angegebene Datei nicht finden.  File name: '{fileName'    
     at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)    

    I have checked the UCCache folder, and the assemblies are there. The account under which SPUC process runs under also has enough privileges.

    Another error on the same correlation thread is this one:

    UserAgent not available, file operations may not be optimized.    bei Microsoft.SharePoint.SPFileStreamManager.CreateCobaltStreamContainer(SPFileStreamStore spfs, ILockBytes ilb, Boolean copyOnFirstWrite, Boolean disposeIlb)     bei Microsoft.SharePoint.SPFileStreamManager.SetInputLockBytes(SPFileInfo& fileInfo, SqlSession session, PrefetchResult prefetchResult).


    Tuesday, January 22, 2013 12:13 PM
  • Hi.

    I am facing the same issue. But I have installed a single server instance properly with all the service accounts (via AutoSPInstaller). I am using Windows Server 2012. I currently suspect Windows Server 2012 to be the source of this issue (for what ever reason). I will now try to setup a SP2013 machine on Windows Server 2008 R2.

    Tuesday, January 22, 2013 4:24 PM
  • A colleague of mine just tested it on his machine, running on Windows Server 2008 r2, and he has also no problems with sandboxed Solutions on SharePoint 2013 using feature event receiver. I don't say, this is a solid proof but I say, this looks more and more like a Windows Server 2012 issue.
    Tuesday, January 22, 2013 8:11 PM
  • Was the Win Server 2012 installation on a machine with DC? Because i don't think this is supported anymore with SP 2013.

    http://blogs.msdn.com/b/syedi/archive/2012/07/26/sharepoint-2013-preview-stand-alone-server-set-up-facts-and-fallacies.aspx

    http://sharepoint-tutorial.net/post/2012/07/18/install-sharepoint-2013-domain-controller.aspx

    Because in the environment where I noticed this behavior, it was a machine with Win Server 2012 on DC. I will try the same scenario on a machine with Win Server 2012 without DC.

    As you said, it looks like a Win Server 2012 issue.

    Wednesday, January 23, 2013 7:35 AM
  • Yep, was with a DC. Actually, I just created a complete new standalone dev machine on Windows Server 2008 r2 with all the usual stuff (DC, SQL, Server, different service accounts (AutoSPInstaller), etc.) and my first test worked like a charm. My colleague is nearly finished with his dev Image (single server installation) on Windows Server 2012 (also with all the usual stuff on a dev server) with low security service account wise. He will test a very basic sandboxed solution with feature receiver soon. I would bet, that he will run into the same problem, as we did.

    Maybe this is something related to DC + Windows Server 2012. This is a good hint, thanks  R Tut :-)

    Thursday, January 24, 2013 9:21 AM
  • Ok, we just did a restest on a new Windows Server 2012 dev image (standalone) with the exact same error from above. As side note, this time we did not use the AutoSPInstaller but did everything by hand.
    Thursday, January 24, 2013 10:01 AM
  • the same issue for me. I also use single server with DC (windows server 2012). so something is different - question is what.
    Saturday, January 26, 2013 7:15 PM
  • Again, installing SharePoint 2013 on a DC is not supported.  If you've installed it this way for production, you'll need to move your SharePoint 2013 installation to a separate server.

    SharePoint - Nauplius Applications
    Microsoft SharePoint Server MVP
    MCITP: SharePoint Administrator 2010

    -----------------------
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Marked as answer by earllibby Saturday, March 2, 2013 5:16 PM
    Saturday, January 26, 2013 8:26 PM
    Moderator
  • I have resolved this problem by reinstalling Sharepoint Foundation 2013 on server that is not the Domain Controller.

    Earllibby

    Saturday, March 2, 2013 5:17 PM
  • Shame this issue is another 'un-supported configuration and ignore' answer as this is now breaking the Microsoft CRM List Component for SharePoint 2013 (native CRM / SharePoint integration) under the same circumstances! If anyone from the product group is out there this will come up a fair bit over the next few months as Dynamics CRM pre-sales teams come up against this issue on their demo environments.

    http://social.microsoft.com/Forums/en-US/crm/thread/57bb32e2-07f5-4b24-9344-f34160883ec7 My connected post on the CRM forums.

    Wednesday, April 17, 2013 4:12 PM
  • It isn't "unsupported and ignore", the unsupportability is specifically called out in the technical documentation for SharePoint 2013.

    "Unsupported', in Microsoft parlance, also generally means "PSS will only not support you if they determine something you've done that falls into the 'unsupported' realm is the source if the issue you're encountering".


    SharePoint - Nauplius Applications
    Microsoft SharePoint Server MVP
    MCITP: SharePoint Administrator 2010

    -----------------------
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Wednesday, April 17, 2013 5:06 PM
    Moderator
  • While I agree that this is clearly called out in the documentation (as I included in bold at the top of my post around it in the CRM forums) and while I understand that there are limits to the testing schedules that are practical and generally determine supported configurations that should be available, what I was really asking is: I have a non-production demonstration environment that will be a right pain to reconfigure and use in this manner, are there any bodges that will make work please ?
    Friday, April 19, 2013 2:13 PM
  • And I think the answer to that is, if you have a demo environment, and it works for you, great.  If not, and you can identify a work around, great.  However, if this is a production environment, and you want to engage PSS, then you do need to walk that supportability line.

    SharePoint - Nauplius Applications
    Microsoft SharePoint Server MVP
    MCITP: SharePoint Administrator 2010

    -----------------------
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Wednesday, April 24, 2013 7:28 PM
    Moderator
  • You may find this strange, but I was able to add my sandboxed solution to the page by enabling verbose logging on Sandboxed Service.  I thought it was a fluke, but I reset IIS, rebooted the server , and tested again...and it continued to work. My server is built with W2K12, DC, SQL Server 2012, and SharePoint 2013.
    • Proposed as answer by Adam Toth Wednesday, October 2, 2013 10:11 PM
    Monday, August 12, 2013 2:01 AM
  • +1 for the verbose logging recommendation! It actually works. Totally ridiculous!
    Wednesday, October 2, 2013 10:12 PM
  • Yep, worked for me too...crazy!
    Tuesday, October 29, 2013 12:05 AM
  • Worked for me too
    Friday, December 27, 2013 6:19 PM
  • You may find this strange, but I was able to add my sandboxed solution to the page by enabling verbose logging on Sandboxed Service.  I thought it was a fluke, but I reset IIS, rebooted the server , and tested again...and it continued to work. My server is built with W2K12, DC, SQL Server 2012, and SharePoint 2013.
    Same issue. but w2008r2sp1 + sql2008r2sp2 on dc "verbose" settings did`t help
    Monday, April 6, 2015 6:11 AM