Sharepoint 2013- Automation Service Failing with Error Code 10
I am failing to convert a word document to pd in SharePoint 2013. I am getting an error code 10.
Looking at the uls logs i see two things one is this error and other it is running in sandbox mode eventhough it is know.
Failed to get child process name: System.ComponentModel.Win3
at System.Diagnostics.NtProce
at System.Diagnostics.Process
at Microsoft.Office.Web.Commo
AppWorker:ee4edc2e-da3a-4c
Looking at the uls logs i see two things one is this error and other it is running in sandbox mode eventhough it is know.
Failed to get child process name: System.ComponentModel.Win3
at System.Diagnostics.NtProce
at System.Diagnostics.Process
at Microsoft.Office.Web.Commo
AppWorker:ee4edc2e-da3a-4c
ASKER
Bembi,
The weird thing is sandbox services is turned off on the servers. There is not command line to turn off sandbox in sharepoint 2013 as compared to sharepoint 2010, plus the service is running under the farm account so it has full rights to the server.
The weird thing is sandbox services is turned off on the servers. There is not command line to turn off sandbox in sharepoint 2013 as compared to sharepoint 2010, plus the service is running under the farm account so it has full rights to the server.
ASKER
I am another error- There is an uninitialized worker that took too long to connect back. [Worker Guid: 2c31e987-bf15-4c23-9f7b-66
The service is SharePoint User Code host....
And in the SharePoint Admin, services on server, you see it as "Microsoft SharePoint Foundation Sandboxed Code Service".
Farm Admin as identity may be not the best idea, but is a different topic.
The sandbox is used for any installed App. In SharePoint 2010 we had farm solutions and user solution. While the farm solutions had full access to the server object model, the user solution ran in the sandbox which limited access. What was called user solution is SP2010 is now the App Host, and is more or less the same limited environment with access only to the client object model, but not to the server object model. This is due to the fact, that in a cloud based environment, where several different "customers" are running on the same farm, you cannot allow one "customer" to get full control to all farm applications. The sandbox is the host, where client Apps can run without affecting any other web application on the farm environment.
This separation make the sandbox host more essential than before, because no App can run if the sandbox host is not available.
Analysing the ULS logs has always to do with the correlation ID. If you have an error and a correlation ID, you can filter the ULS logs to this correlation ID to see the whole sequence of the error. To whenever you see errors or exceptions in the ULS logs, copy the correlation ID into the filter and have a look on the sequence to get an idea, what happened before the error.
Coming back to the error above, we have a access denied error (0x80004005). This can be an error connected with permissions, but also possibly to the not running sandbox host.
See this article to explain the sandbox host
(here also called SharePoint User Code Service (SPUCHostService.exe).
https://msdn.microsoft.com/de-de/library/ff798382.aspx
And in the SharePoint Admin, services on server, you see it as "Microsoft SharePoint Foundation Sandboxed Code Service".
Farm Admin as identity may be not the best idea, but is a different topic.
The sandbox is used for any installed App. In SharePoint 2010 we had farm solutions and user solution. While the farm solutions had full access to the server object model, the user solution ran in the sandbox which limited access. What was called user solution is SP2010 is now the App Host, and is more or less the same limited environment with access only to the client object model, but not to the server object model. This is due to the fact, that in a cloud based environment, where several different "customers" are running on the same farm, you cannot allow one "customer" to get full control to all farm applications. The sandbox is the host, where client Apps can run without affecting any other web application on the farm environment.
This separation make the sandbox host more essential than before, because no App can run if the sandbox host is not available.
Analysing the ULS logs has always to do with the correlation ID. If you have an error and a correlation ID, you can filter the ULS logs to this correlation ID to see the whole sequence of the error. To whenever you see errors or exceptions in the ULS logs, copy the correlation ID into the filter and have a look on the sequence to get an idea, what happened before the error.
Coming back to the error above, we have a access denied error (0x80004005). This can be an error connected with permissions, but also possibly to the not running sandbox host.
See this article to explain the sandbox host
(here also called SharePoint User Code Service (SPUCHostService.exe).
https://msdn.microsoft.com/de-de/library/ff798382.aspx
ASKER
Bambi-
Are you saying I need to run the sandbox host services on the server to get this working.
Are you saying I need to run the sandbox host services on the server to get this working.
Yes...
AppWorker:.....WordServerW
By the way, can be also disabled...
https://gallery.technet.microsoft.com/office/Remove-Sandbox-Mode-for-9c8ac750
Even you second message you can find there...
AppWorker:.....WordServerW
By the way, can be also disabled...
https://gallery.technet.microsoft.com/office/Remove-Sandbox-Mode-for-9c8ac750
Even you second message you can find there...
ASKER
Bembi- That doesn't work on Sharepoint 2013. I have Microsoft looking into this now too.
OK, if it doesn't work for 2013, just get the Sandbox Host up and running,
As I stated before, some services are relying on this service.
As I stated before, some services are relying on this service.
ASKER
Microsoft is looking at the issue now, it is not the sandbox host service either. I turned on that service. Thanks for your help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Resolution provided by troubleshooting with Microsoft Support.
In ULS log, ou have to look at the same correlation ID. So if both errors have the same correlation ID and the sandbox is involved, I would assume that the sandbox identity may not have to permissions to write the result.