If Office Web Apps isn’t working correctly when it is used together with SharePoint 2013, locate the symptom below and expand the heading to find troubleshooting steps.
- Problem: When you select the "new document" link in a SharePoint library, you are prompted to upload a document instead of having the option to create a new Office document. Choosing (single-clicking) an Office document opens the file in the client application. Previews of Office documents are not displayed
- Problem: You see the error "Sorry, something went wrong" when you try to view an Office document in Office Web Apps.
- Problem: You see the error "File Not Found. The URL of the original file is not valid or the document is not publicly accessible. Verify the URL is correct, then contact the document owner"when you try to view an Office document in Office Web Apps by using a user generated URL.
- Problem: Previews of Office documents don't appear in SharePoint 2013. Instead, they show the error "This content cannot be displayed in a frame."
- Problem: You see the error “A data connection is set to always use connection file and {0:ExcelWebApp} does not support external connection files. The following connection failed to refresh: Data connections.”
Problem: When you select the "new document" link in a SharePoint library, you are prompted to upload a document instead of having the option to create a new Office document. Choosing (single-clicking) an Office document opens the file in the client application. Previews of Office documents are not displayed.
Here are some troubleshooting options to try.Verify that claims-based authentication is used by the SharePoint web application that is used to create the new document
Only web applications that use claims-based authentication can open files in Office Web Apps. To determine the authentication provider for a web application, follow these steps:
- In SharePoint 2013 Central Administration, select Manage web applications.
- Select the web application that you want to check, and then select Authentication Providers on the ribbon.
Make sure that the WOPI zones match on the SharePoint 2013 and the Office Web Apps Server farm.
To do this, run the following command on the SharePoint Server:
Get-SPWopiZone
The result will be one of the following: internal-https, internal-http, external-https, external-http.
Next, run the following command on the SharePoint Server:
Get-SPWOPIBinding
In the output, look for WopiZone: zone. If the results from Get-SPWopiZone do not match the zone that is returned by Get-SPWOPIBinding, you must run the Set-SPWOPIZone -Zone cmdlet on the SharePoint Server to change the WOPI zone to match the result from Get-SPWOPIBinding. For help with using these cmdlets, see Get-SPWOPIBinding, Set-SPWOPIBinding, and Get-SPWOPIZone.
Problem: You see the error "Sorry, something went wrong" when you try to view an Office document in Office Web Apps.
Make sure that you are not logged in as System Account. Whenever the currently logged on user name appears as sharepoint\system, that user can’t edit or view the document. Log in as a different user and try to access Office Web Apps again.
Problem: You see the error "Sorry, there was a problem and we can't open this document" when you try to view an Office document in Office Web Apps.
If you set up Office Web Apps in a test environment that uses HTTP, make sure that you set the AllowOAuthOverHttp setting to True as described in Step 5: Change the AllowOAuthOverHttp setting in SharePoint 2013 to True.
At some point, did you add domains to the Allow List by using the New-OfficeWebAppsHost cmdlet? If so, make sure that you are accessing Office Web Apps from a host domain that is in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run the Get-OfficeWebAppsHost cmdlet. If you have to add a domain to the Allow List, use the New-OfficeWebAppsHost cmdlet.
Problem: You see the error "Sorry, Word Web App can't open this document because the service is busy. Please try again later" when you try to view an Office document in Office Web Apps.
Did you install Office Web Apps Server on a domain controller? Office Web Apps Server cannot run on a domain controller. Office Web Apps Server must be installed on a separate server that is part of a domain. For more information, see Software, hardware, and configuration requirements for Office Web Apps Server.
Problem: You see the error "File Not Found. The URL of the original file is not valid or the document is not publicly accessible. Verify the URL is correct, then contact the document owner"when you try to view an Office document in Office Web Apps by using a user generated URL.
Are you trying to open a document that has a file size that is larger than 10 megabytes from a user generated URL? Make sure the document doesn’t exceed 10 megabytes.
Problem: Previews of Office documents don't appear in SharePoint 2013. Instead, they show the error "This content cannot be displayed in a frame."
Low memory conditions can cause problems with Office document previews. View Hardware requirements—web servers, application servers, and single server installations to see the memory requirements for SharePoint 2013, which are the same requirements that Office Web Apps Server uses.
Problem: You see the error “A data connection is set to always use connection file and {0:ExcelWebApp} does not support external connection files. The following connection failed to refresh: Data connections.”
This happens because Office Web Apps Server doesn’t support the Office Data Connection (ODC) file that stores the data connection information. To fix this problem, follow these steps:
- Open the workbook in an Excel client application.
- Choose the Data tab and then choose Connections.
- Select the data connections listed in the message, and then choose Properties.
- Choose the Definition tab.
- Clear the Always use connection file check box for check box.”
- Re-upload the workbook to the SharePoint document library.
To enable people to interact with workbooks that contain a Data Model or Power View views in a browser window, configure Excel Services in SharePoint Server to display workbooks. This requires a SharePoint administrator to run the New-SPWOPISupressionSetting cmdlet on the server where SharePoint Server is installed. For more information, see New-SPWOPISuppressionSetting and Administer Excel Services in SharePoint Server 2013.
No comments:
Post a Comment