Office Web Apps server / Lync server 2013

Hi I have installed a Lync 2013 Server and Office Web Apps Server. Configured Lync topology, Office Web Apps farm and certificates.
However when i start the services i get this error message in the log saying Office Web Apps discovery failed.
Event ID: 41033
Description:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
Attempted Office Web Apps Server discovery Url:
Received error message: Invalid Uri syntax for WAC configuration
The number of retries: 1,
Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.
Resolution:
Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
I can access the OWAS server Url from Lync Server
Connecting to the HTTPS discovery URL is working fine, and brings up the XML-page (after i click "show all content").
The two servers are located on the same internal network, DNS resolves fine both ways, and no firewall rules blocks any connections between the two. Can anyone please help me figure this out?
Only identical problem found online is here (Invalid Uri syntax for WAC configuration):
http://blogs.technet.com/b/dodeitte/archive/2012/09/10/office-web-apps-server-amp-lync-server-2013.aspx
He resolved the problem by assigning a new OAuthTokenIssuer certificate. This however did not fix the problem in my case.
Regards
Sverre A. Veel

Hi,
In addition, please make sure you have restarted front end and office web apps server after reissuing the certificate.
Kent Huang
TechNet Community Support

Similar Messages

Office Web Apps Error after SP 2013 September 2014 CU

Hello Everyone,
I have a single front end and single SQL server for my SharePoint 2013 deployment. I also have Office Web Apps setup and running. However after installing SP 1 and the latest September 2014 CU it appears our users are seeing the below prompt
when open a Word doc in Office Web Apps.
However I am finding that if they use IE 9 or 10 and even Firefox everything works normal. This appears to be affecting just Word.
As for my Office Web Apps server it is still at Version 15.0.4420.1017 (RTM)
If I need to update my Office Web Apps server what order should i do. SP1, July, then Sept?
Thanks,
Ian...

You need to apply office web app update.
It should be in below order.
Office web app Sp1
September 2014 update
If this helped you resolve your issue, please mark it Answered

Using Office Web Apps Server with SharePoint Foundation 2013

I want to know whether I can configure Office Web Apps server to edit Excel documents on a SharePoint Foundation 2013 site.
I came across a TechNet article that states that "When used together with SharePoint Server 2013, Office Web Apps Server provides updated versions of Word Web App, Excel Web App, PowerPoint Web App, and OneNote Web App".
However, later in the same article, it states "If your organization licenses Office 2013 through a Volume Licensing program, you can enable Office Web Apps editing for SharePoint 2013 on-premises" (without mentioning Foundation or Server).

Hi Lemesnil,
The Office Web App server should support the Edit licenses for SharePoin Foundation 2013, Office Web App is free to
download, you can also try installing and configuring in a test environment, see more from the below article applied to SharePoint Foundation 2013.
http://support.microsoft.com/kb/2886404/en-us
http://blogs.technet.com/b/speschka/archive/2012/12/31/enabling-licensing-and-editing-for-office-web-apps-in-sharepoint-2013.aspx
Anohter useful article aobut how to license Office Web App server, you can take a look.
http://blogs.technet.com/b/volume-licensing/archive/2013/05/22/how-to-license-office-web-apps-server.aspx
Thanks
Daniel Yang
TechNet Community Support

Office web apps Server for Sharepoint 2013

Hello,
I used the following article to install office web apps server and hook it up to a test sharepoint server:
http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx. The OWAS service was verified as working by loading:
https://owas.companyname.com/hosting/discovery
For the sharepoint configuration phase, the following commands were run on the sharepoint machine:
1) New-SPWOPIBinding -ServerName "owas.companyname.com" -- (owas.companyname.com) is the host name of the owas server)
2) Get-SPWOPIZone
3) Set-SPWOPIZone -zone "external-https"
However, office documents are still launching in the desktop office applications, not in the browser. Any ideas of what else I may need to do?
thanks,
Sherazad

Hi ,
According to your description, my understanding is that you fail to configure Office Web Apps for your SharePoint 2013.
How about run Get-SPWOPIZone? If you can get a result, it says that your SharePoint have connected with Office Web Apps.
Then you can run below command to change the zone to internal-https.
Set-SPWOPIZone -zone "internal-https"
Reference:
http://technet.microsoft.com/en-us/library/ff431687(v=office.15).aspx
http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
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

Using office web apps with SharePoint 2013

Hi,
I would like to use office web apps in our SharePoint 2013 environment. I would like to know if OWA has to have a dedicated server or can I install it on the SharePoint 2013 app server.
Sherazad

With SharePoint 2013, Office Web Apps cannot be installed on the SharePoint Server, it must be installed on its own server, not shared with any other IIS-based service (it essentially "takes over" IIS).
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.

Open Documents with Office Web App - SharePoint 2013

We have configured Office Web App for our SharePoint 2013 Farm and in Site settings, Site Collection Features, have disabled "Open Documents in Client Applications by Default" . Out of 15 sites, all documents in 13 sites open in Office
Web App. One of the 2 sites where the document still open using Client Application is a Wiki site.
Advanced propertied for the libraries settings has been set to "Use the server default (Open in the browser)". Anything else to check to open documents in Office Web App?
Thanks
MP

Hi,
As I understand, you encountered the issue when you want to open documents with Office Web App.
Check things below:
1. In the library setting->advanced setting, you can choose the open in the browser to see if the same situation will occur.
2. Check if you have not enable the Open Documents in Client Applications by Default feature.
If you choose Activate to enable the Open in Client feature (documents will open in the client application), or
Deactivate to disable the Open in Client feature (documents will open in the browser).
You can go to Site setting->site collection administration->site collection feature->Open
Documents in Client Applications by Default to set the feature.
The article below is about how to set the default open behavior for browser-enabled documents.
https://technet.microsoft.com/en-us/library/ee837425(v=office.15).aspx
The article below is about how to configure office web apps for SharePoint 2013.
Configure Office Web Apps for SharePoint 2013
Best regards
Sara Fan
TechNet Community Support

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

Exchange and Office Web Apps Integration - Wrong Url to Outlook Web App port 444

Hi,
I'm trying to setup Office Web Apps integration with Exchange 2013. Office Web Apps are working fine with SharePoint 2013 and the WAC servers are listed as in a healthy state.
When trying to open an office document from OWA I get the usual "Sorry...we ran into a problem. Please try again"
However I have noticed that the URL that OWA is passing WAC is in the format: https://exchangeservername.domain.com:444/owa/[email protected]/wopi/files...
This is the backend server address! All the internal and external urls for owa, ecp, ews etc are set to https://mail.domain.com and they all seem to be working fine. Client Access and Mailbox roles are on the same server.
If I change the url to https://mail.domain.com/owa/[email protected]/wopi/files... then the office file opens correctly in Office Web Apps
How do I correct the URL that OWA is sending Office Web Apps?
Thanks!

Hi DJL,
If everything works well except open document via OWA, it seems Exchange server 2013 has been configured correctly.
Please follow me to check Office Web Apps Server settings and Integration.
OWAS settings
1. Certificate:
Come from a trusted CA, include FQDN of OWAS farm in SAN field.
Exportable private key.
Friendly name must be unique within Trusted Root Certificate Authorities store.
2. Farm:
New-OfficeWebAppsFarm with following parameters
-InternalURL is the FQDN of the server that runs OWAS
-ExternalURL is the FQDN so that OWAS can be access on the Internet
-CertificateName is the friendly name of the certificate to be used for HTTPS
3. Explore this URL https://mail.domain.com/hosting/discovery
If OWAS works well, you can see a WOPI-discovery XML file in web browser.
Integration
1. Configure OWAS URL via EMS,
Set-OrganizationConfig –WACDiscoveryEndpoint https://mail.domain.com/hosting/discovery
2. WAC stands for Web Access Components.
Check App Log the 140 and 142 Event IDs for MSExchange OWA.
142 means the discovery of the OWAS was successful, 141 means something went wrong.
3. Enable OWAS.
By default, OWA Virtual Directory is already enable WAC Viewing on both public and private computer.
Please run "Get-OwaVirtualDirectory | FL *wac* "to check whether both “WacViewingOnPublicComputersEnabled” and “WacViewingOnPrivateComputersEnabled” parameter is True.
4. Method to collect logs on OWAS.
Run following command in OWAS powershell prompt:
Get-OfficeWebAppsFarm | FL *log*
More details to refer:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-2013-office-web-apps-server-integration.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Office Web Apps Integration in a Test Environment

I am trying to test Office Web Apps in an Exchange 2013 test environment and therefore have setup my farm for HTTP only. I have set the WAC Discovery End Point on the Exchange server and I can browse to the XML successfully however when I preview files
they are still being displayed using Web-Ready Document Viewer. I have checked the Event Log and found event ids 140 and 141.
Event 141 lists the following error - There was a failure connecting to or otherwise retrieving Data from the Wac Discovery Service. We will fall back to stellent. Successfully retrieved configuration data from http://server01/hosting/discovery, but
retrieved discovery xml does not contain an external https net zone node.
Do I need to configure HTTPS with a certificate in order to get this working in a test environment or should it work with HTTP?
Thanks

Hi Luke,
Based on my research, I found some people solved this issue via resarting MBX server and CAS server on Exchange 2013 server.
Similar thread for your reference:
Exchange 2013 and Office Web Apps Server Integration
http://social.technet.microsoft.com/Forums/en-US/927a84db-cf54-4546-8b94-374c64eaac2d/exchange-2013-and-office-web-apps-server-integration?forum=exchangesvrgeneral
Please also double check whether there is anything missing during the integration. Offical articles for your reference:
Deploy Office Web Apps Server
http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx
Office Web Apps Server Integration
http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Office Web Apps - working in other browsers but not Internet Explorer

Hi there,
I have office web apps on my SharePoint 2013 environment. The previews work file when hovering next to a document but if I try to open it, I get "Sorry, we ran into a problem". It looks as though Excel files open okay but I
have tested Word and Powerpoint documents and I get this error. Also, it only appears to happen in Internet Explorer - Google Chrome and Firefox are okay. Any ideas?

Thanks for the advice. I installed the hoftix (on the OWA server) and now it appears to really be broken - nothing is opening using office web apps anymore.
I found this blog with the same errors I am getting - I'm guessing I will need to uninstall etc. too??
http://blogs.technet.com/b/dodeitte/archive/2013/03/29/issue-with-automatic-updates-enabled-amp-office-web-apps-server-2013-update.aspx

Office Web App Load balancing Question

I am going to install office web app in load balanced farm behing f5. There are few questions i want to ask:
Do i first put servers in load balancer and start installing office web app or after installation of office web app in one server put that in load balancer and add another one or put both in load balancer and start installing.
While i tried without putting servers in load balancer with offload ssl parameter , when i tried to join second server in the farm it gave me error destination unreachable. Is it because with offload ssl parameter it is looking for load balancer or something
else? I checked port 809 from the servers and also verified the user was local admin in both machines.
Any insight will be helpful.
Adit

Pls refer below link for configuration of NLB for OWA servers:
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
Please ensure that you mark a question as Answered once you receive a satisfactory response.

Office web Apps server Lync 2013 Certificate

Hi,
I'll be installing Office web app (OWA) server with Lync 2013 std edition. External users access is disabled but federation is enabled, mean OWA will be exposed to internet as wabweb.contoso.com, the interal host name of OWA server is owa.contoso.local
Does the certificate on the on OWA server need to have owa.contoso.local and certificate principle name and wabweb.contoso.com as SAN? or only owa.contoso.local is enough?

It really depends on how you publish the server to the internet. You have some options. If you are publishing this via a reverse proxy, internally you would have a private cert with .local on it and the public name on the reverse proxy. If you are
punching a firewall hole/NAT directly to the server your best option is to use a public cert on that server directly.
That all said, personally I like to make both the internal and external farm URL the same, and use a public cert on the server (if no reverse proxy is in play). So I would actually enter the OWAS Farm as wabweb.contoso.com in topology builder, than
when creating the farm via PowerShell make that both the internal and external URL and get a certificate with a single name on it of wabweb.contoso.com.
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Using Office Web Apps Server 2013 without SharePoint, Lync, or Exchange

I'm trying to use the Office Web Apps Server 2013 as an online viewer of Office documents (using the Online Viewer). I've set up a New-OfficeWebAppsFarm with editing disabled, no UNC paths, and an external URL with SSL Offloaded to my Load balancer.
I don't want to use it with SharePoint, Lync or Exchange. Just use it to view documents online (similar to Google Docs Viewer).
However, when I point the Office Web Apps Server to a remote file online (e.x. a DOC hosted on a website), I get an error opening it.
I've checked the health statuses of my OWA Servers, and it says Healthy.
When I check the Event viewer of my OWA Server, I see 501 WOPI errors:
Could not contact WOPI End Point. Error details - 'NotImplemented url - https://sample-owa-url.com/oh/wopi/files/@/wFileId?wFileId=http%3A%2F%2Fwww%2Eimr%2Esandia%2Egov%2Fimrtemplate%2Edoc&access_token=1&access_token_ttl=0'.
It seems OWA is trying to connect to the path /oh/wopi/files.... but the server is responding NotImplemented.
What do I have to get this to work?
Thanks for any help!

Did you ever find an answer? I have the exact same Issue.
I have 2 WAC servers behind a load balancer with SSL offloaded to the LB. Both servers report healthy with Get-OfficeWebAppsMachine
Works fine with SharePoint 2013.
When I use it with a remote file, served using HTTP with no authentication (anonymous), I get a generic "Sorry there was a problem and we can't open this document..." error.
In the ULS and event viewer, I see the WOPI error and 501 which basically says:
Could not contact WOPI End Point. Error details - 'NotImplemented url - https://sample-owa-url.com/oh/wopi/files/@/wFileId?wFileId=http%3A%2F%2Fwww%2Blah%2Ecom%2FWordDocument%2Edocx&access_token=1&access_token_ttl=0'.
I also sometimes see this:
<HealthMessage>WordViewerWfeWatchdog reported status for WebWordViewer in category 'WfeRedirect'. Reported status: /default.aspx returned a 404, which means that we didn't have where to redirect.</HealthMessage>
The very interesting part s that I have a dev server, with OWA (WAC) installed, thats not going through a LB and does not use SSL, that works just fine with the same public url word document.

High availability for Lync 2013 persistent chat server and office web app server

I have 1500 users, need HA in primary data center and DR also. looking for HA and DR solution for persistent chat server and office web app server.
is below correct?
1. 2 persistent chat server in a pool of primary data center and 1 in DR. can this be reduced or any changes?
2. 2 Office web app server in a pool of primary data center and 1 in DR. can this be reduced or any changes?
also do i need HLB for both roles?

1) In Lync Server 2013, there are improvements in both high availability and disaster recovery:
High availability improvements: SQL Server mirroring is used to provide high availability for the Persistent Chat Server content database and Persistent Chat compliance database within a data center (in-site).
Disaster recovery improvements: Persistent Chat Server supports a stretched pool architecture that enables a single Persistent Chat Server pool to be stretched across two sites (that is, a single logical pool in the topology, with servers in the pool physically
located across two sites). SQL Server Log Shipping is used for cross-site disaster recovery.
For more information about high availability and disaster recovery, see
Configuring Persistent Chat Server for High Availability and Disaster Recovery in the Deployment documentation.
2) for HA & DR, you can 2 Office web app server in a pool of primary data center and 1 in DR. and You will need HLB for office web app servers
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
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Load balancing and HA for office web apps server Lync 2013

Hi,
I have 12000 users, 3 FE servers in a pool, 2 edge server in a pool, HA required, IM/presence, A/V, WEb conferencing required. plan to have 2 office web apps server a farm with HA, below are my queries
1. which type of load balancing i need....DNS or HLB for office web app servers? if its HLB then is it mandatory?
2. i have already 2 HLB for FE pool .. one for externa url , one for internal URL...can i use the same HLB for office web app servers ?
3. one more question regarding EDGE pool load balancing, can i use the same HLB in EDge pool also that i am using for FE pool?

Hi,
1. which type of load balancing i need....DNS or HLB for office web app servers? if its HLB then is it mandatory?
WebApps runs on https and you cannot load balance http traffic using DNS load balancing. you need to have a HLB.
2. i have already 2 HLB for FE pool .. one for externa url , one for internal URL...can i use the same HLB for office web app servers ?
you can use the same HLB for that
3. one more question regarding EDGE pool load balancing, can i use the same HLB in EDge pool also that i am using for FE pool?
for that one, you probably need a separate HLB.
Z-Hire -- Automate Lync User Account creation process ( AD / Exchange / Lync )

Office Web Apps server / Lync server 2013

Similar Messages

Maybe you are looking for