Office Web apps error in Sharepoint
I’ve been struggling with Sharepoint and the Office web apps to show word and excel files in the browser. If you have too, take this journey with me as we try to solve it.Server side solutions
First of all, take a look at this article: Deploy Office Web Apps.In summary, make sure you’ve done these things:
- Manage services on this server:
1) Click Start, point to All Programs, Microsoft SharePoint 2010 Products, and then SharePoint 2010 Central Administration.
2) On the SharePoint Central Administration home page, in System Settings, click Manage services on this server.
3) On the Services on server:page, start Excel Calculation Services, Word Viewing Service, and PowerPoint Service. The OneNote Web App does not use a SharePoint service.
. - Manage service applications:
1) Click Start, point to All Programs, Microsoft SharePoint 2010 Products, and then SharePoint 2010 Central Administration.
2) On the SharePoint Central Administration home page, in Application Management, click Manage service applications.
3) On the Service Applications page, click New, and then click Word Viewing Service.
4) In the Word Viewing Service Application dialog box, in Name, type Word Viewing Service Application. In Application Pool, select Use existing application pool, and then in the listbox, select SharePoint Web Services Default. In Add to default proxy list, verify Add this service application’s proxy to the farm’s default proxy list is selected (default), and then click OK.
5) On the Service Applications page, click New, and then click PowerPoint Service Application.
6) In the PowerPoint Service Application dialog box, in Name, type PowerPoint Service Application. In Application Pool, select Use existing application pool, and then in the listbox, select SharePoint Web Services Default. In Add to default proxy list, verify Add this service application’s proxy to the farm’s default proxy list is selected (default), and then click OK.
7) On the Service Applications page, click New, and then click Excel Services Application.
8 ) In the Excel Services Application dialog box, in Name, type Excel Services Application. In Application Pool, select Use existing application pool, and then in the listbox, select SharePoint Web Services Default. In Add to default proxy list, verify Add this service application’s proxy to the farm’s default proxy list is selected (default), and then click OK.
- Activate the Office Web Apps Feature:
1) In a browser, in the SharePoint site, click Site Actions (for example, go to the central administration page), and then click Site Settings.
2) On the Site Settings page, in Site Collection Administration, click Site Collection Features.
3) On the Features page, for Office Web Apps, click Activate
. - OR with powershell to activate the Office Web Apps Feature on all site collections:
Click Start, point to All Programs, Microsoft SharePoint 2010 Management Shell.
$webAppsFeatureId = $(Get-SPFeature -limit all | where {$_.displayname -eq “OfficeWebApps”}).Id
Get-SPSite -limit ALL |foreach{Enable-SPFeature $webAppsFeatureId -url $_.URL }
If you are running the Office Web Apps on a DC, then take a look at this article: Installation Notice for SharePoint 2010 Public Beta
In summary, make sure you’ve done these things:
- If you are using SharePoint on DC, the following Windows PowerShell command would need to be run to enable Sandboxed Solutions.
$acl = Get-Acl HKLM:SystemCurrentControlSetControlComputerName
$person = [System.Security.Principal.NTAccount]“Users”
$access = [System.Security.AccessControl.RegistryRights]::FullControl
$inheritance = [System.Security.AccessControl.InheritanceFlags]“ContainerInherit, ObjectInherit”
$propagation = [System.Security.AccessControl.PropagationFlags]::None
$type = [System.Security.AccessControl.AccessControlType]::Allow
$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)
$acl.AddAccessRule($rule)
Set-Acl HKLM:SystemCurrentControlSetControlComputerName $acl
. - If you are trying to use Office Web Apps on DC(Office Web
Application need to be installed seperately, like a language pack or an
update. Please also note that Office Web Application cannot be installed
on needs to follow the same edit of config.xml
to install on Windows 7), then the following commands need to be run to
make the services work. Please note that in different languages,
Service Application names could be localized. You can find them out by
Get-SPServiceApplications, and then change the names in the script as
necessary.
Please do note that Office Web Apps is not supported on a DC. So this configuration should never be used in production.
$e = Get-SPServiceApplication | where {$_.TypeName.Equals(“Word Viewing Service Application”)}
$e.WordServerIsSandboxed = $false
$e.WordServerIsSandboxed $p = Get-SPServiceApplication | where {$_.TypeName.Equals(“PowerPoint Service Application”)}
$p.EnableSandboxedViewing = $false
$p.EnableSandboxedEditing = $false
$p.EnableSandboxedViewing
$p.EnableSandboxedEditing #(Please use the below script for PowerPointServiceApplication – You need to enter “Y” for the answer of each cmd)
Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedViewing $false
Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedEditing $false
- In the server’s c:windowssystem32inetsrvconfigapplicationHost.config
Add the line below in the end of the dynamicTypes.
IISRESET
If after that, opening an Excel document in sharepoint gives you this error: “Unable to process the request. Wait a few minutes and try performing this operation again.”
- Click Start, point to All Programs, Microsoft SharePoint 2010 Products, and then SharePoint 2010 Central Administration.
- On the SharePoint Central Administration home page, in Application Management, click Manage web application –> Sharepoint – 80—> click Service connections- check/select that excel service.
___________________________________________________________________________________
Also, Check if you are opening your document in protected view. To disable this, follow these steps (from Sharepoint 2010 – how to):
- Run one of the Office 2010 application (e.g. Word 2010).
- Click on File menu, and select Options.
- In the “Options” dialog, select Trust Center in the left pane.
- Click on Trust Center Settings in the right pane.
- Select Protected View in the left pane of “Trust Center” dialog.
- Disable any of all of the protected view options as below by unticking the check boxes:
- Enable Protected View for files that fail validation
- Enable Protected View for files originating from the Internet
- Enable Protected View for files located in potentially unsafe locations
- Enable Protected View for Outlook attachments
After this point, most doc, docx and xlsx files will open, though there are still some persistent ones that fail to open.
Opening a Word doc gives this error: “Word Web App cannot open this document for viewing because of an unexpected error. To view this document, open it in Microsoft Word.”
Apparently this happens when the extension isn’t supported by the Web Apps. Yet, the doc format should be supported, since Microsoft says this about it:
“Doc can be viewed in Word Web App. Word Web App converts the DOC-file to a DOCX-file so it can also be edited.”
See an overview of all the supported file types here.
Note that xls is not supported by the Office Web Apps, not for viewing or editing. This format is only supported on their SkyDrive.
___________________________________________________________________________________
Make sure that you check your permissions. For this, read: Account permissions and security settings (SharePoint Server 2010).
This wasn’t a part of my problem, though.
___________________________________________________________________________________
Have a look at the logs of Sharepoint.
A very nice way to view them in realtime and record certain action is the ULS Viewer.
In the Logs of Sharepoint (default in C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14LOGS), I found this:
Librarian.BeginGetItem(F5a78dec131294bd88974b77dc36ee258mf05929c85d10495083846cfb9519854bm9b1ce232beae4457ab0bc9bbbf4c501fm, Png, docdata.xml) bdbb85bf-03a5-49c1-ba53-1d24350ceb8e
ViewStore.BeginGetItem(F5a78dec131294bd88974b77dc36ee258mf05929c85d10495083846cfb9519854bm9b1ce232beae4457ab0bc9bbbf4c501fm, Png, docdata.xml) bdbb85bf-03a5-49c1-ba53-1d24350ceb8e
ViewStore.SetCompleted(F5a78dec131294bd88974b77dc36ee258mf05929c85d10495083846cfb9519854bm9b1ce232beae4457ab0bc9bbbf4c501fm, Png, docdata.xml) – status = ConversionError bdbb85bf-03a5-49c1-ba53-1d24350ceb8e
Librarian.SetCompleted(F5a78dec131294bd88974b77dc36ee258mf05929c85d10495083846cfb9519854bm9b1ce232beae4457ab0bc9bbbf4c501fm, Png, docdata.xml) – status = ConversionError bdbb85bf-03a5-49c1-ba53-1d24350ceb8e
So, it seems that my issue is related to a ConversionError.
This seems consistent with what Microsoft says about DOC files: “Word Web App converts the DOC-file to a DOCX-file so it can also be edited.”
I read this about it: “Worker processes: The Word Viewing service application and the PowerPoint service application uses worker processes to convert documents and presentations into a series of PNG images or into XAML (if Silverlight is installed), and temporarily stores output locally on-disk. Administrators can configure worker process settings to optimize performance by using SharePoint Central Administration and by using Windows PowerShell.”
Which makes me next step installing Silverlight. Close IE and Install Silverlight. Afterwards, restart it, then the error will change into:
ViewStore.SetCompleted(F5a78dec131294bd88974b77dc36ee258m1d5b8f44cba04d6d8ea29c2e96ab6c3fmc29170dd4f924af69ed2f40ad4367e83m, Silverlight, docdata.xml) – status = ConversionError 3aa0ec44-999c-46e9-ac1d-24ee6ea878d7
Librarian.SetCompleted(F5a78dec131294bd88974b77dc36ee258m1d5b8f44cba04d6d8ea29c2e96ab6c3fmc29170dd4f924af69ed2f40ad4367e83m, Silverlight, docdata.xml) – status = ConversionError 3aa0ec44-999c-46e9-ac1d-24ee6ea878d7
Source: http://heidibrebels.be/blog/archives/2011/office-web-apps-error-sharepoint
No comments:
Post a Comment