Fix: Unable to activate worker process proxy object within the worker process

Issue:

We have encountered an issue that the Sandbox Worker Process (SPUCHostService.exe) of SharePoint 2010 wasn't able to initialize itself on several servers. As a result Sandboxed Solutions couldn't be used. We've found the following entries in the SharePoint ULS:

-  Unable to activate worker process proxy object within the worker process: ipc://1787a8e0-45c3-48dc-9b3c-a60e8b4d6199:7000

-  Error activating the worker process manager instance within the worker process.

- Inner Exception: System.InvalidOperationException: Unable to activate worker process
proxy object within the worker process:
 ipc://1787a8e0-45c3-48dc-9b3c-a60e8b4d6199:7000     at
 Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()         

- Process creation/initialization threw an exception. Stopping this process.
"ipc://aec755bf-3ac8-4c2e-b5a4-9198b1bf027e:7000" - Stopping shim process. Shim process name: "SPUCWorkerProcess" Shim PID: "0x1868"
Shim service url: "ipc://aec755bf-3ac8-4c2e-b5a4-9198b1bf027e:7000" - Stopping proxy process. Proxy process name: "SPUCWorkerProcessProxy" Proxy PID:
"0x0AB0" Proxy service url: "ipc://1787a8e0-45c3-48dc-9b3c-a60e8b4d6199:7000" - Error activating the worker process manager instance within the worker process.

- Starting worker process threw - Inner Exception: System.InvalidOperationException: Unable to activate worker process proxy object within the worker process: ipc://1787a8e0-45c3-48dc-9b3c-a60e8b4d6199:7000 at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies() - CreateSandBoxedProcessWorker() is called
- Created desktop: Service-0x0-2bea3589$\Microsoft Office Isolated Environment

Fix:

After trying to fix the issue for several hours, we tried to disable the "Check for publisher's certificate revocation"-setting for the Service Account of the Sandbox and this solved the issue. You can do this by changing the following key in the registry:

HKEY_USERS\[SID OF THE SERVICE ACCOUNT]\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
The value of "State" needs to be set to "0x00023e00".

You can get the SID of the Service Account with PowerShell:

$(Get-SPManagedAccount -Identity "THE SERVICE ACCOUNT").Sid.Value


Hope this helps!

---

Created by Sven Häfker

Comments

[Kommentiert von: Mario Cortés Flores]

thanks Sven, your solution fix it, good job!!