The other day I had a client contact me with an interesting SharePoint issue. Seemingly out of the blue, their SharePoint 2010 server CPU started being consumed by these two main processes with multiple instances:
When I looked into the issue, this is what I saw in task manager:
Whoa, that’s a lot of processes!
And I saw the same thing for conhost.exe, which looked like this:
So what are these processes and what do they do? I will spare you the long version and suffice to say they are related to Sandbox solutions. If you want the details, check out MSDN.
I suppose you could just stop the Sandbox service, however, there's a good chance you’re going to want to use Sandbox solutions at some point. So what else can you do?
I found a post on this issue on the forums that included a solution from Microsoft. It turns out to be a registry permissions issue. Check the following entries. The necessary permissions are specified for the local users group (SERVERNAME\Users):
In each case, the local Users group should have the listed permission. If not, add it. In my case (and others in the post), it was missing in the next to last key:
So let’s fix it. Click Add, and add the local Users group with the correct permission:
Now close the registry editor and open Central Administration. Go into Services on Server, and stop/start the Microsoft SharePoint Foundation Sandboxed Code Service. Now check out Task Manager:
I hope this post is helpful to other SharePoint users out there. If you have any questions about this entry or C5 Insight, please contact us.
Jeff, As I have mentioned, I haven't seen this on SharePoint 2013, so I can't offer a proven solution. However, as I have mentioned to others, try using Process Monitor to try and see what reg keys are getting query failed errors to figure out where you need to tweak the permissions (assuming same cause). And of course I have to say you shouldn't be running this on a domain controller (unless this is just your test or development environment). Just be aware that you can't run like this in production and be supported by MS (see http://support.microsoft.com/kb/2764086). Also, this is all from the User Code host service, which is basically sandboxed solutions. If you don't use any sandboxed solutions in SP2013, try stopping the service (in Central Admin and Windows Services). You can see more detail here: http://blogs.msdn.com/b/sharepointdev/archive/2011/06/13/dual-worker-process-model-for-sandboxed-solutions.aspx. Hope it helps. Doug
In my case was necessary give permission on all path until these items above Works fine for me. SharePoint Server 2013 SP1 with Windows Server 2012 R2
Thanks for the post. It worked.
Thanks a lot..It worked :)
Running Windows Server 2012 R2 & SharePoint Server 2013 SP1, no luck yet, we tried ALL sort of things. no one resolved the issue: Too many SPUCWorkerProcessProxy.exe processes, launching one after another after a couple of seconds, and also when trying to add a sandboxed web part to a page, it says the user code host rejected the request because it is too busy... And it's not busy at all, except for replicating dozens of SPUCWorkerProcessProxy.exe processes... :(
I have everything OK with permission, but still see 100s of these processes. I have disabled Microsoft SharePoint Foundation Sandboxed Code Service and they are gone. It wwring, but we don't use any of these solutions, thereby works for us.
Thanks for the post. I tried the above security changes but no luck. I'm running SharePoint 2013 (Sept 2014 CU 4649) on a domain controller. Are steps different for domain controllers? https://twitter.com/spjeff/status/510776405974474752
Robinio, Assuming you're running Windows Server 2012, those registry keys might be different. I would suggest running the Process Monitor tool (replaced regmon/filemon): http://technet.microsoft.com/en-us/sysinternals/bb896645 If this is the cause, you can filter for just registry errors and try to find what key is causing the failure. Also check the events logs / ULS logs of the server to see if you see any other weird errors. Good luck! Let me know what you find, and I can make a note.
Processes are back!!! ~ 80 SPUCWorkerProcessProxy.exe all permission are set as required. Any suggestions ?
Nilldot, I would recommend the same to you as previously to Robinio. Use Process Monitor to try and see what reg keys are getting query failed errors. So you checked all of the above keys, and they all have users set with either Read or QueryValue, and they all exist? Were any updates to Windows or SharePoint applied? Have you rebooted? Some of those keys are in the SYSTEM registry hive which is only read on boot. Hope it helps. Doug
I had this same problemn on a windows server 2012 R2 running Sharepoint 2013. I used process monitor to fix all the access denied errors on both registy and file system and now it seems to run normally. Unfortunately, I can't tell you which registry keys or file system paths fixed the error because I had so many access denied errors, but at least you know now that it can be fixed :)
THANK YOU :-) Great write-up, Great Solution!!!!
Excellent, Great solution. Thanks! :-)
Though Process Explorer provided detailed information for those processes, I didn't even think about permission issue on those reg entries. I have only 9 instances (before it was ~ 40) currently running. Thank you.
Nice post. I'm running a sharepoint 2013 development environment and i have the same problem. Unfortunately the registry fixes doesn't work in my case. Are there any news about this issue?
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.