OWA for SP2013 Part-4(TroubleShooting some Issues)

Troubleshoot errors in Office Web Apps when it is used with SharePoint 2013

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’re 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:

1.     In SharePoint 2013 Central Administration, click Manage web applications.

2.     Select the web application that you want to check, and click Authentication Providers on the ribbon.

The authentication provider must be displayed as Claims Based Authentication for Office Web Apps to work correctly with the web application. To resolve this issue, you can delete the web application and recreate it using claims-based authentication, or you can change the authentication method of the web application.

Make sure 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 don’t match the zone that is returned by Get-SPWOPIBinding, run the Set-SPWOPIZone -Zonecmdlet on the SharePoint Server to change the WOPI zone to match the result from Get-SPWOPIBinding

Problem: You receive a “Sorry, this document can’t be opened for editing” error when you try to edit an Office document in Office Web Apps.

In some situations, users that are members of Active Directory (AD) Security Groups may be unable to edit documents in the browser. The solution is to ensure the User Profile Service Application (UPA) is properly configured and fully synchronized with user and group memberships.

Problem: You receive a "Sorry, something went wrong" error when you try to view an Office document in Office Web Apps.

Make sure you’re not logged in as System Account because you won’t be able to edit or view a document. Log on as a different user and try to access Office Web Apps again.

Problem: You receive a "Sorry, there was a problem and we can't open this document" error 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 you set the AllowOAuthOverHttp setting to True as described in step 5: Change the AllowOAuthOverHttp setting in SharePoint to true.

If you added domains to the Allow List by using the New-OfficeWebAppsHost  cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s 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. To add a domain to the Allow List, use the New-OfficeWebAppsHost  cmdlet.

Problem: You receive a "Sorry, Word Web App can't open this document because the service is busy. Please try again later" error when you try to view an Office document in Office Web Apps.

·         Did you install Office Web Apps Server on a domain controller, by chance? Unfortunately, Office Web Apps Server can’t run on a domain controller. Office Web Apps Server must be installed on a separate server that’s part of a domain.

·         Make sure you’re running SharePoint 2013 build 15.0.4420.1017 or later. On the SharePoint 2013 server, follow these steps to verify the build number:

1.     Go to Start > All Programs > Microsoft SharePoint 2013 Products > SharePoint 2013 Central Administration.

2.     Choose System Settings > Manage servers in this farm.

Verify the Configuration database version is 15.0.4420.1017 or higher

Problem: You receive a "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" error 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 "This content cannot be displayed in a frame" error.

Low memory conditions can cause problems with Office document previews. Take a look at the Hardware requirements—web servers, application servers, and single server installations to see the memory requirements for SharePoint 2013. These are the same requirements used by Office Web Apps Server.

Problem: You receive “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” error.

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:

1.     Open the workbook in an Excel client application.

2.     Click Data > Connections.

3.     Select the data connections listed in the message, and click Properties.

4.     Click the Definition tab.

5.     Clear the Always use connection file check box for check box.

6.     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.

Disconnect SharePoint 2013 from Office Web Apps Server

 

If, for any reason, you want to disconnect SharePoint 2013 from Office Web Apps Server, use the following command example.

Remove-SPWOPIBinding -All:$true