Office Web Apps HTTPS setup

We are trying to setup SharePoint 2013 and WAC 2013 servers in a test lab that uses HTTPS to communicate, however we're experiencing issues trying to connect to it from SharePoint 2013. We setup the internal and external HTTPS urls on WAC and provide the
wildcard self-signed certificate, setting AllowHTTP to false, then rebooted. The bindings on the IIS Site then update to include 443.
However, when we try to create the wopizone on the SP box, using new-SPWOPIBinding -Servername xxx it can't seem to see the server properly. We get:
WARNING: The server did not respond. Trying again (attempt 1 of 5).
WARNING: The server did not respond. Trying again (attempt 2 of 5).
WARNING: The server did not respond. Trying again (attempt 3 of 5).
WARNING: The server did not respond. Trying again (attempt 4 of 5).
WARNING: The server did not respond. Trying again (attempt 5 of 5).
New-SPWOPIBinding : Sorry, we have encountered an error and New-SPWOPIBinding
has failed. If you are using a server configured with HTTP, you must include
the -AllowHTTP parameter.
At line:1 char:1
+ New-SPWOPIBinding -ServerName devowasp.tfl.gov.uk
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.Share...tNewWOPIBinding
   :SPCmdletNewWOPIBinding) [New-SPWOPIBinding], SPCmdletException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewWOPIB
   inding
We've rebooted both boxes and can browse to https://xxx/hosting/discovery fine from the SP box. We've also checked the Certs and tried doing self signed certs for the FQDN instead of wildcards, with no effect.
We can't use HTTP in the test lab for WAC because SharePoint 2013 is using HTTPS. Is this a common issue and has anybody seen a fix for it?
Thanks,
RT

Take a look at the following walkthrough. I suspect your problem is using self signed certs and wildcards. this article will give you the specifics.
http://blogs.technet.com/b/justin_gao/archive/2013/06/30/configuring-office-web-apps-server-communication-using-https.aspx
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

Office Web Apps Server IIS site disappeared?

I deployed an Office Web Apps server on a dedicated VM to be used for Lync 2013. After the initial installation / set up, I confirmed the discovery URL. It worked fine.
However, after one point in time, PowerPoint Presentations stopped working. When trying to share a PPT presentation, the Lync client popped up a message saying "Sorry, we couldn't upload <ppt file name> because we're having trouble connecting
to the service. If this keeps happening, try contacting your support team". I've done many many Lync and Office Web Apps install myself previously, and never had a message pop up like the one I saw in this case.
I tried going to the Web Apps discovery URL again, and it didn't get anywhere. I got on the Web Apps server and all the IIS sites were wiped.
I tried uninstalling the Office Web Apps server and reinstalling, but from that point on, IIS sites for Web Apps just would not appear under IIS manager.
Has anyone had similar issue with Office Web Apps?
Thanks,
Andrew Shin, TechNet Forum replies

Hello,
Maybe the windows update is active and configured to Automatically download and installed update of Office Web Apps and this behavior just breaking your setup.
Try
remove the farm of WAC
Install SP1
and start new deployment of farm.
Link SP1
http://www.microsoft.com/en-us/download/details.aspx?id=42547
How update your farm Office Web Apps
http://technet.microsoft.com/en-us/library/jj966220(v=office.15).aspx
Hugs[]s
Robson Hasselhoff - Follow me @Robk9e

SharePoint 2013 cannot view PDF documents in mobile browser with office web apps

Hi,
I'm receiving the following error when viewing SharePoint 2013 PDF documents in a mobile browser after clicking on the filename:
"Viewing of .pdf files has been disabled in Microsoft Word Mobile Viewer. Please get in touch with your helpdesk."
My Question
Is viewing PDF documents in mobile browsers with Office Web Apps SP1 actually supported? If so, how can I enable it? I've already have pdf viewing working in non-mobile browsers. Word documents open just fine on mobile browsers too.
I'm getting conflicting answers for pdf mobile viewing support from various sources:
You've got Microsoft toting that they've added in PDF viewing on any device for Office Web Apps
http://blogs.office.com/2013/07/03/pdfs-in-the-word-web-app/
A MS support person saying saying it is not supported
http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2013/12/31/enabling-pdf-previews-in-document-libraries-with-office-web-apps-2013-in-sharepoint-2013-open-link-does-not-work-from-preview.aspx
Another person implying that it should work because you can disable pdf browsing for mobile browsers only
http://blogs.technet.com/b/office_resource_kit/archive/2013/07/24/control-whether-pdfs-open-in-word-web-app-or-the-default-pdf-reader.aspx
What I've tried
When I started looking into this there was a mobile WOPI entry:
Application     : WordPdf
Extension       : PDF
ProgId          :
Action          : mobileView
IsDefaultAction : False
ServerName      : 20SP8
WopiZone        : internal-http
I tried experimenting with tweaking this binding by changing the DefaultAction to true, and even removing it altogether via:
Get-SPWopiBinding -Action "MobileView" -Application "WordPDF" | Remove-SPWopiBinding -Confirm:$false
But I still get the same message.
I removed all the WordPdf bindings and re-added them via:
New-SPWOPIBinding –ServerName "<myserver>" –Application "WordPDF" -AllowHTTP
No dice. In fact the mobileview binding doesn't even come back... but I guess that is a different issue altogether.
Version
SharePoint 2013 (SP1)
Office Web Apps Server (SP1)
Farm Setup
Internal facing only
2 front end servers, 1 app server, 1 office web apps server

I think the PDF support, if it exists, in only in Office 365. Always remember that the Office 365 and on premises versions will never be in sync. On premise is updated using periodic service packs and Office 365 has continuous updates. (I've heard every
10 days.)
In my Office 365 / IE 10 tests, the PDFs open in the browser's default PDF viewer, in my case FoxIt Reader. So I can't prove one way or the other about support in Office Web Apps.
Mike Smith TechTrainingNotes.blogspot.com

Office web apps server 2013 install issue

Dear All,
when i install office web apps server in a new server(OS:Windows Server 2008 SP1) with PowerShell Scripts it keep the installing status for more than four hours .
what should i do now ,i think it should not take such long time as i do the same installing in the other server before which takes less than 1 hours.
beg your suggestions!

Hey
please take these points into your considerations:
- OWA server can be installed on Windows server 2008 R2 or Windows server 2012
- Log in as administrator and preferred to use domain administrator account specially to create new office web apps farm
- run the script
Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core
It takes approximately 20 minutes :)
Also check this link for Required Server Roles, and Features for Office Web Apps
http://technet.microsoft.com/en-us/library/jj219435.aspx
Ahmed Said Moussa SharePoint Consultant

Office Web Apps - Preview not appearing when acccessing via HTTPS

I have installed Sharepoint 2013 and Office Web Apps, set the wopibinding, and set the wopizone to be https-external. Everything seems to work fine if accessing the web app using HTTP (can open, edit, preview office web app (WAC) documents)... but if
I access via HTTPS then I run into a mixed content error when trying to preview the WAC documents... I can open them and edit them without issue using office web apps inside the browser though just not preview.
If I select "New document" it also takes a while to load and displays a blank pop up window... assume it must be related
Error message:
XMLHttpRequest cannot load http://xxxx.org.nz/Docs/_layouts/15/inplview.aspx?List={6E…65723B96E}&ViewCount=1&IsXslView=TRUE&IsCSR=TRUE&IsRibbon=TRUE&Cmd=EcbView.
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://xxxxxx' is therefore not allowed access.
[blocked] The page at 'https://xxxxx.org.nz/xx.aspx' was loaded over HTTPS, but ran insecure content from 'http://xxxxxx/Docs/_layouts/15/WopiFrame.aspx?sourced…%20big%20wide%20inter%20web%2Edocx&action=interactivepreview&wdSmallView=1':
this content should also be loaded over HTTPS.

Hi ,
Before you configure SharePoint 2013 to use Office Web Apps Server via HTTPS, make sure that you have set up Office Web Apps Server by following the steps in Deploy
a single-server Office Web Apps Server farm that uses HTTPS or Deploy a multi-server, load-balanced Office Web Apps Server farm
that uses HTTPS.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Office Web Apps is HTTP, But, Want to change it to HTTPS - How ?

Forum,
We have deployed and configured a single Office Web Apps server farm to use HTTP, Using TechNet instructions e.g.:
New-OfficeWebAppsFarm -InternalURL "http://servername" -AllowHttp -EditingEnabled
New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP
Set-SPWOPIZone -zone "internal-http"
AllowOAuthOverHttp to True
And everything is working perfectly fine !
We now need to change it to use HTTPS and we have a certificate for that. But, Since it has been already configured with HTTP and it already has a configured binding, How can I change all this to HTTPS ?

you can try rebuilding the binding at SharePoint server -
https://technet.microsoft.com/en-us/library/ff431687
Remove-SPWOPIBinding -All:$true
New-SPWOPIBinding -ServerName <WacServerName>
Get-SPWOPIZone
// Take note of the WOPI zone that is displayed.
Set-SPWOPIZone -zone "external-https"
//If the results from Step 3 show that internal-https and the SharePoint farm is internal only, you can skip this step. If you have a SharePoint farm that’s internal and external, you need to run the following command to change the zone to external-https.
Or try by Rebuilding the OfficeWebApps Farm -
http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2013/12/20/office-web-apps-2013-rebuild-your-farm-in-a-few-easy-steps.aspx
Take farm offline
Remove each machine (parent and child) from the farm
Recreate the farm - New-OfficeWebAppsFarm -InternalUrl "https://server.domain.com" -EditingEnabled -CertificateName *.domain.com
Rebuild the bindings on SharePoint Server : As explained above
Thanks
Ganesh Jat [My Blog |
LinkedIn | Twitter ]
Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

SharePoint 2013 SP1 and Office Web Apps SP1 not working using HTTP

Hi I had problems installing and configuring Office Web Apps 2013 SP1 integrated with SP 2013 SP1.
Do you know if there is any issue?
This is the error in the owa side:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/24/2014 10:04:54 PM
Event time (UTC): 4/24/2014 9:04:54 PM
Event ID: 86c0893b9e89427babde2c4e931e0a28
Event sequence: 17
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/wv-1-130428459380785645
Trust level: Full
Application Virtual Path: /wv
Application Path: C:\Program Files\Microsoft Office Web Apps\WebWordViewer\
Machine name: SPS-OWAS01
Process information:
Process ID: 13696
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpUnhandledException
Exception message: Exception of type 'System.Web.HttpUnhandledException' was thrown.
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlersPossiblyUnderLock(Boolean onPageThread)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlers(Boolean onPageThread)
Unable to determine zone from request
at Microsoft.Office.OpenWebApplication.WopiOM.DecomposeWopiUrl(List`1 actionList, HttpRequest request, WopiAction currentAction, String extension, Boolean forceSsl)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSUrlAdapter.ChangeActionInWacUrl(HttpRequest request, WacUrlApplication application, WacUrlAction currentAction, WacUrlAction targetAction)
at Microsoft.Office.Web.WordViewer.Controls.Application.RegisterApplicationInit()
at Microsoft.Office.Web.Common.AApplication.OnPreRender(EventArgs e)
at Microsoft.Office.Web.WordViewer.Controls.Application.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
at System.Web.UI.Page.Render(HtmlTextWriter writer)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL:
http://sps-owas01/wv/wordviewerframe.aspx?ui=en-US&rs=en-US&WOPISrc=http://sharepoint.internal/_vti_bin/wopi.ashx/files/8b568ecdf89c44d8afd4132bc0b82b32&sc=http://sharepoint.internal/SitePages/Home.aspx&wdEnableRoaming=1
Request path: /wv/wordviewerframe.aspx
User host address: 10.10.199.27
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 7
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlersPossiblyUnderLock(Boolean onPageThread)
at System.Web.UI.Page.LegacyPageAsyncInfo.CallHandlers(Boolean onPageThread)
Custom event details:
José Quinto Zamora SharePoint and Search Specialist MCITP and MCPD in SharePoint 2010
http://joSharePoint.com

It show me also this message:
<meta content="width=device-width" name="viewport" /><style></style>
Server Error in '/wv' Application.
Unable to determine zone from request
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Office.OpenWebApplication.DiscoveryEntryNotFoundException: Unable to determine zone from request
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[DiscoveryEntryNotFoundException: Unable to determine zone from request]
Microsoft.Office.OpenWebApplication.WopiOM.DecomposeWopiUrl(List`1 actionList, HttpRequest request, WopiAction currentAction, String extension, Boolean forceSsl) +598
Microsoft.Office.Web.Apps.Environment.WacServer.WSUrlAdapter.ChangeActionInWacUrl(HttpRequest request, WacUrlApplication application, WacUrlAction currentAction, WacUrlAction targetAction) +161
Microsoft.Office.Web.WordViewer.Controls.Application.RegisterApplicationInit() +1766
Microsoft.Office.Web.Common.AApplication.OnPreRender(EventArgs e) +1531
Microsoft.Office.Web.WordViewer.Controls.Application.OnPreRender(EventArgs e) +17
System.Web.UI.Control.PreRenderRecursiveInternal() +113
System.Web.UI.Control.AddedControl(Control control, Int32 index) +12375740
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +150
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +246
System.Web.UI.Page.Render(HtmlTextWriter writer) +40
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +150
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5363
José Quinto Zamora SharePoint and Search Specialist MCITP and MCPD in SharePoint 2010
http://joSharePoint.com

Office web apps feature not working after setup and configuration?

Hi I have installed the SP1 update and since then my office web apps features are not coming up in SharePoint. After running the updates and attaching the farm back i see the bindings and settings are applied but somehow the office web apps features are
not coming up in SharePoint. Can someone let me know what might be the issue?

Did you delete and recreate the WAC farm after you updated?
See: https://technet.microsoft.com/en-us/library/jj966220.aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Office Web Apps 2013 installation issue in HTTPS

Hi,
I'm trying to install Office Web Apps Server in HTTPS mode but keep getting an error. When I run the command New-SPWOPIBinding -ServerName owaserver, it says "WARNING: The server did not repspond. Trying again (attempt 1of 5)." When I go into Event
Viewer, I see this error for each attempt:
An operation failed because the following certificate has validation errors:
Subject Name: CN=<url>, OU=Domain Control Validated - RapidSSL(R), OU=See
www.rapidssl.com/resources/cps (c)12, OU=<OU>, SERIALNUMBER=<serial number>
Issuer Name: CN=RapidSSL CA, O="GeoTrust, Inc.", C=US
Thumbprint: <thumbprint>
Errors:
SSL policy errors have been encountered. Error code '0x2'..
I've installed the Root CA from the provider, registered the .cer files in CA -> Security -> Manage Trusts, and via PowerShell. I've reset IIS multiple times and rebooted the OWA server and the WFE. I'm not sure if it's an issue with the cert or a
SharePoint issue.
Thanks

Did you register your certificate with the New-OfficeWebAppsFarm command (-CertificateName) when you set up your Office Web Apps farm?
http://technet.microsoft.com/en-us/library/jj219436.aspx
- Xenox G.

Exchange Office Web Apps Preview Does not work in OWA (web)

I have setup Exchange 2013, Lync 2013, SharePoint 2013, IIS as a Reverse Proxy Server, an Office Web Apps Server, etc, etc. Everything is setup to use SSl (https) and everything works great EXCEPT... Office Web Apps... and ONLY via Exchange and OWA (exchange
browser-based access).
I can login via the intranet or Internet for everything (SharePoint, Outlook, and Lync) and Office Web apps functionality works flawlessly for all... except for Exchange and OWA.
If I login in to a web-based Exchange seeion, everything works right and I can see the various attachments.
For all other scenarios, Office Web Apps works (SharePoint, Outlook, Lync, etc), but in owa (web version of Outlook) I see that Office Web Apps is triggered (I see the Office Web Apps text and the dots that indicate something is loading)... However, it just
crashes and eventually times out (see image):
If I look in the error logs for the Web Apps Server I see this:
Essentially, it looks like that owa uses a distinctly different path to load the attachments into the Web Apps Server such that the file is not found!
What is happening? Why does Exchange OWA (web version of Outlook) somehow use a different path that fails to locate attachments in Office Web Apps, but Lync, Outlook, and SharePoint (both in Intranet and Internet) work perfectly?
This is VERY frustrating. Can anyone help?
Please?
Clearly, the reverse proxy is working, the certificates are working, OAuth is working, etc. It seems there must be some variable/path that is only defined in Exchange for OWA that uses a different path for Office Web App attachments and that path is WRONG!
Please, help!
Thanks

Hi,
Thanks for sharing. It’s glad to hear the good news.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Office Web Apps Server June 2013 Cumulative Update Excel Freeze Pane and Hide/Un-hide Feature Missing

Hi,
I have recently updated the Office Web Apps Server to the June 2013 Cumulative Update (KB2817350) which was published with the new features that allow rendering of freeze pane, hide/un-hide the excel worksheet and row/columns, Header
Row Snapping, Sorting, Data Validation and Autocomplete. i have followed the TechNet article (http://technet.microsoft.com/en-us/library/jj966220.aspx)
to update the office web apps server. Current setup is a SharePoint 2013, SQL 2012 and Office Web Apps server. All server are installed on Windows server 2012.
3vild3vil

Hi,
Sorry to inform you that these new features are specific to cloud Excel Web App in both SkyDrive and Office365. There is no update available for on-premise Excel Web Apps installed locally
yet. Thank you for your understanding.
http://blogs.office.com/b/microsoft-excel/archive/2013/06/26/we-ve-updated-excel-web-app-what-s-new-as-of-june-2013.aspx
Miles LI TechNet Community Support

Office Web App Server 2013: cannot edit word document with own WOPI Server

Hi all,
I tried to build our own WOPI Server to connect to Office Web App Server 2013 SP1. Viewing documents
in IE was possible quite easy to achieve. Now it comes to editing.
When I try to edit a document, I got a german message “Sie verfügen leider nicht über die Berechtigung zum Bearbeiten dieses Dokuments“.
This means something like „Sorry, you do not have any permission to modify this document”.
I enabled editing on the OWAS-Server while setup procedure
(Until now, I only have an InternalUrl but no ExternalUrl.)
PS C:\ > New-OfficeWebAppsFarm –InternalUrl “https://win-owas...”
–CertificateName "win-owas…" –EditingEnabled
ULS log shows
BaseDocument says editing is not supported [WebEditingEnabled: True] [SupportsEditing: True] [PinnedUsersRights: Read]
So far, I implemented these three REST service methods:
[OperationContract]
[WebInvoke
"GET":"api/wopi/files/{name}?access_token={access_token}"
"GET":"api/wopi/files/{name}/contents?access_token={access_token}"
"POST":"api/wopi/files/{name}/contents?access_token={access_token}"
Office Web App Server was downloaded from “Microsoft Volume Licensing Center”. I installed latest updates from Microsoft.
Did anybody succeed in writing to own WOPI an can give me some hints?
Thank you in advance.

Hi,
The discovery xml contains many lines. The one for editing docx is:
<action
name="edit"
urlsrc="https://win-owas.cado.camos.de/we/wordeditorframe.aspx?"<ui=UI_LLCC=""&><rs=DC_LLCC=""&><showpagestats=PERFSTATS=""&>"
ext="docx" requires="locks,cobalt,update"/>
I am calling it this way:
<iframe
src="https://win-owas.cado.camos.de/we/wordeditorframe.aspx?WOPISrc=http%3a%2f%2fpc-ms.cado.camos.de%3a8000%2fWOPI%2fapi%2Fwopi%2Ffiles%2FAbout_Keyboard_Input.docx&access_token=5268690b-19c6-496d-8ae6-b694f8e7bd0c"
I’m not sure whether or not I implemented "locks,cobalt,update" correct, but I do not see any ‘edit-’network traffic from OWAS-Server to WOPI-Server. So I cannot debug anything. I will (re)check the articles you mentioned.
Thank you for your help.

Office Web Apps 2013 - Excel, fine, Word & Powerpoint, unable to view.

Hi All,
I am having an infuriating issue where by the following occurs when opening documents via OWA:
Excel - Preview, no problem, opening, no problem, editing, no problem (even when accessing oData connections for PWA).
Word - Preview, errors, opening, errors, editing (incredibly!!) works.
PowerPoint - Nothing works...
I think I have read every blog post on every error I am receiving in the ULS but nothing is resolving. It is on a VMware VM and I had to reinstall OWA after it was noted that it has rather surprising behaviour if OWA is not installed on the system drive.
I have installed each hotfix/update and tested after each with no joy...
Three (possibly misleading) error categories:
From OWA log:
Cannot create WOPI Proof Token - could not find valid old proof key;
From SP log:
WOPI Proof: Missing Header;
Useragent not available, file operations may not be optimized (doubt this is causing my problem but the quality of errors in the logs is so bad it may well be).
For context, the service account for OWA is local admin on the box and has full access to the content databases on the SQL server.
The symptoms of the error are the biggest concern given the degrees of success I am having with the different apps (kind of rules out security or setup if Excel works fine and Word sort of works).
Any help will be very much appreciated and may stop my increasing baldness with the amount of hair I am pulling out!!
Thanks in advance.
Sam

Hi Sam,
According to your description, my understanding is that Office Web Apps does not work for viewing Word & PowerPoint.
For troubleshooting your issue, please access the Office Web Apps Server discovery URL to verify that the Office Web Apps Server farm is working for Word & PowerPoint:
http://servername/hosting/discovery
Also please add the OWA url into your “Trusted Sites” in IE.
Reference:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_28102553.html
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Eric Tao
TechNet Community Support

Office Web Apps farm - how to make it high available

Hi there,
I have deployed OWAs for Lync 2013 with two servers in one farm. When I was testing, e.g. the case when other server is down I found out the following error:
Log Name:      Microsoft Office Web Apps
Source:        Office Web Apps
Date:          17/03/2014 22:59:54
Event ID:      8111
Level:         Error
Computer:      OWASrv02.domain.com
Description:
A Word or PowerPoint front end failed to communicate with backend machine
http://OWASrv01:809/pptc/Viewing.svc
Does that means, that OWAs cannot setup as high avaiable when using standalone OWAs only? Above error appeared when the server OWASrv01 was rebooting.
Petri

Hi Petri,
For your scenario, you have achieve a  high performance for your Office Web Apps farm but not high availability.
For performing a high availability Office Web Apps farm, you can refer to the blog:
http://blogs.technet.com/b/meamcs/archive/2013/03/27/office-web-apps-2013-multi-servers-nlb-installation-and-deployment-for-sharepoint-2013-step-by-step-guide.aspx
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers
if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Eric Tao
TechNet Community Support

Office Web Apps 2013: SSLOffLoad, Cannot connect Sharepoint.

Hi,
Background.
We have a 2 machine SharePoint 2013 farm and a 2 machine Office Web Apps Farm, both of which are behind a load balancer. Our public DNS holds the records for the two farms: webapps.company.com and sharepoint.company.com. However these domains are not in
the internal DNS and cannot be resolved internally. I've put these in the hosts file on the respective machines, so they can talk to each other.
I'm now at the point where I need to connect SharePoint to the OWA farm. I've followed the guide here: http://technet.microsoft.com/en-us/library/jj219455%28v=office.15%29.aspx
and setup the OWA farm by the specification under the heading "Deploy a multi-server, load balanced, office web apps server farm that uses HTTPS".
My creation string
New-OfficeWebAppsFarm -InternalUrl https://machinename.domain.com -ExternalUrl https://webapps.comapny.com -SSLOffloaded -EditingEnabled
That went ok and the farm is created. I then added the second machine
New-OfficeWebAppsMachine -MachineToJoin "machinename.domain.com"
Now that the farm is created i went ahead and ran
New-SPWOPIBinding -ServerName machinename.company.com
But that just gave me "WARNING: The Server did not respond. Trying again"
Adding the -AllowHttp flag let me continue, but that ended up giving me error when i created or opened a document in Sharepoint.
So my guess is that i need to figure out why i cannot use New-SPWOPIBinding -ServerName machinename.company.com without -AllowHTTP.
It was my understanding that we don't have to setup SSL on the individual farm server as the load balanser woudl take care of that.
Any ideas as to why New-SPWOPIBinding -ServerName machinename.company.com won't work?
Thank you for taking the time to read my post
Regards.

http://social.technet.microsoft.com/wiki/contents/articles/19039.sharepoint-2013-how-to-enable-office-web-apps-to-work-in-both-internal-and-external-environments.aspx
Because I’ve not configured my OWA machine to be published to the Internet so I have to use its Internet-public IP. It’s not a recommended best practice. In your case, the external URL would be http://owa.abc.com
. Above I’m not using SSL certificate
to encrypt data over the Internet. Just add CertificateName parameter if you want to use whether CA-issued certificate
or self-signed certificate. Finally, check both internal URL (http://app03/hosting/discovery
) and external URL (http://198.xxx.xxx.xxx/hosting/discovery
) to confirm everything is working
well. Your screen should display XML structure.
Now you need to re-bind all SharePoint machines to WAC farm using New-SPWOPIBinding (http://technet.microsoft.com/en-us/library/jj219441.aspx
). Next, you just need to set the WOPI
zone for external use even there is an internal use in your SharePoint environment.
1
Set-SPWOPIZone –zone “external-http”
Finally, configure Excel service and then upload an Excel workbook into a document library and check it. Below are the screenshots of OWA working on both internal and external environment.
http://blogs.technet.com/b/ken_prices_sharepoint_blog/archive/2014/01/15/explaining-the-use-of-internal-and-external-wopi-zones-for-office-web-apps.aspx
If this helped you resolve your issue, please mark it Answered

Office Web Apps HTTPS setup

Similar Messages

Maybe you are looking for