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

Similar Messages

  • Office Web Apps Farm Connection Issue SharePoint 2013

    I have servers owa1 and owa2. Owa1 is acting as host and owa2 I joined to office web apps farm that’s is to owa1. 
    Both these are in office web apps farm and load balanced. Now my question is: From SharePoint Server when I connect , how should i connect while execute PowerShell command in SP server, in the syntax
     –servername parameter what should I specify do I need to specify the FQDN of the server name or host name (officewebapps.jdax.corp.local, this is host record created in DNS by mapping to VIP Of the load balancer (owa1 and owa2).
    Please help me.
    Thanks, Ram Ch

    You need to use URL officewebapps for parameter InternalURL
    ew-OfficeWebAppsFarm [-AllowCEIP <SwitchParameter>] [-AllowHttp <SwitchParameter>] [-AllowHttpSecureStoreConnections <SwitchParameter>] [-CacheLocation <String>] [-CacheSizeInGB <Nullable>] [-CertificateName <String>] [-ClipartEnabled <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DocumentInfoCacheSize <Nullable>] [-EditingEnabled <SwitchParameter>] [-ExcelAllowExternalData <SwitchParameter>] [-ExcelConnectionLifetime <Nullable>] [-ExcelExternalDataCacheLifetime <Nullable>] [-ExcelPrivateBytesMax <Nullable>] [-ExcelRequestDurationMax <Nullable>] [-ExcelSessionTimeout <Nullable>] [-ExcelWarnOnDataRefresh <SwitchParameter>] [-ExcelWorkbookSizeMax <Nullable>] [-ExternalURL <String>] [-FarmOU <String>] [-Force <SwitchParameter>] [-InternalURL <String>] [-LogLocation <String>] [-LogRetentionInDays <Nullable>] [-LogVerbosity <String>] [-MaxMemoryCacheSizeInMB <Nullable>] [-MaxTranslationCharacterCount <Nullable>] [-OpenFromUncEnabled <SwitchParameter>] [-OpenFromUrlEnabled <SwitchParameter>] [-OpenFromUrlThrottlingEnabled <SwitchParameter>] [-PicturePasteDisabled <SwitchParameter>] [-Proxy <String>] [-RecycleActiveProcessCount <Nullable>] [-RemovePersonalInformationFromLogs <SwitchParameter>] [-RenderingLocalCacheLocation <String>] [-SSLOffloaded <SwitchParameter>] [-TranslationEnabled <SwitchParameter>] [-TranslationServiceAddress <String>] [-TranslationServiceAppId <String>] [-WhatIf [<SwitchParameter>]]
    Hope below article should help you in detail:
    http://blogs.technet.com/b/jenstr/archive/2013/03/18/creating-an-office-web-apps-server-2013-farm-with-2-machines.aspx

  • Office Web Apps Farm Across Multiple Data Centers?

    I have not been able to find any definitive information about this but the article below seems to suggest what I have in mind is not recommended.  I am not sure about supported.
    "Stick to one data center.  Servers in an Office Web Apps Server farm must be in the same data center. Don’t distribute them geographically. Generally you need only one farm, unless you have security needs
    that require an isolated network that has its own Office Web Apps Server farm."
    http://technet.microsoft.com/en-us/library/jj219435.aspx#topology
    What I have is two very well connected data centers located in the same metro area.  We will be deploying a Lync EE pool at each site and use pool pairing for DR.  What I am wondering is should I:
    Create a single Office Web Apps farm with the server from each data center as members?
    Create a farm in each site with a single member, but both farms sharing the same URL?
    Create a farm in each site with a single member, but both farms have different names.  This seems unnecessarily ugly, but throwing it out there.
    Since Lync is using Office Web Apps in read only mode the question is different than if SharePoint were involved.  However, I can't rule out this farm also being used for SharePoint down the road.
    The LB/RP device of choice is Citrix NetScaler.  Another thought I had is can that be configured so incoming requests for Office Web Apps at each data center can prioritize traffic to the server or farm within that data center?  If that is unavailable
    then switch to the server at the other data center?
    Thanks.

    Hi,
    An Office Web Apps farm can be deployed to provide functionality for multiple sites.
    Also you can deploy one Web Apps farm on each site.
    So I think you can choose to deploy with the option one and three as you said.
    Here is a case about deploying Lync deploy Office Web Apps server may help you:
    http://social.technet.microsoft.com/Forums/lync/en-US/7e67bacf-4895-4bdb-95b8-0aff8a0c575f/geographical-placement-of-office-web-app-servers?forum=lyncdeploy
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync Office Web App Farm External Access using IIS ARR

    When i try to present a powerpoint app when logged in externally i get an error saying that it could not connect to the office web app server.  I need some help with (maybe screenshots) of what the reverse proxy settings should be. Here is some info
    so maybe someone can fill in the blanks.  
    My Office web app server has a private address and sits on the inside. The DNS name is owasrv.mydomain.com 
    The internal url is https://owasrv.mydomain.com
    The external url is https://wacsrv.mydomain.com
    i have a public A record pointing to wacsrv.mydomain.com and my ssl cert has a SAN entry for wacsrv.mydomain.com
    ***NOTE our public and private domain names are the same...that is not a mistake.
    I mostly need help with the what to put in for the url rewrite rules and what to put in when creating the server farm.  Also is it OK that the name of my server is different than the external url address.
    Gerald Csakany

    Hi Gerald,
    Did you follow this guide here http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx
    and mainly the section down the bottom which refers to publishing the WAC by matching this pattern ((?:^en-us/|^hosting/|^m/|^o/|^oh/|^op/|^p/|^we/|^wv/|^x/).*)
    and moving the rule to the top?
    What happens when you try to browse to https://wacsrv.mydomain.com/hosting/discovery from external?
    They can be different, I usually make them the same for simplicity, but as long as they're set on the Webfarm it shouldn't be an issue.
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
    Georg Thomas | Lync MVP
    Blog www.lynced.com.au | Twitter
    @georgathomas
    Lync Edge Port Check (Beta)

  • Office Web Apps Farm - undo the AllowHTTP switch

    I allowed HTTP while troubleshooting a cert issue, only to discover that the argument doesn't take a $false option.
    It seems to be enable-only.   Now I want to disable it.  Can I do this via PS or must I do a registry hack?

    Try:
    set-OfficeWebAppsFarm -AllowHttp:0
    or
    set-OfficeWebAppsFarm -AllowHttp:$false
    Notice the ":" instead of a space.
    Please mark posts as answers/helpful if it answers your question.
    Blog
    Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

  • 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

  • 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 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

  • Sharepoitn 2013 - Office Web Apps Licensing

    Dears,
    I do have the license key with me for the office web apps 2013. The office web apps are working with our SharePoint 2013 portal without any issues. We were able to view the documents but couldn't edit the documents which are hosted in our portal.
    How can i apply the license key for office web apps? do i need to execute any power shell commands? please advice.
    thanks in advance,
    Ammar

    thanks Steven for your reply and appreciate the same.
    but i need to know where exactly i should pass the licensing value as a parameter or the exact way to apply the license.
    when i was searching i found the below link:
    http://blogs.msdn.com/b/microsoft_press/archive/2013/02/04/from-the-mvps-installing-office-web-apps.aspx
    under licensing it was mentioned like below:
    Licensing
    So the Office web apps farm is up and running and you have enabled editing. There is though another step before your users will be able to actually edit documents with Office Web Apps; you need to license the users for editing.
    This is achieved by running a series of PowerShell commands on the SharePoint 2013 Central Administration server:
    Get-SPUserLicense
    $x = New-SPUserLicenseMapping -SecurityGroup <ADsecuritygroup> –License OfficeWebAppsEdit
    $x | Add-SPUserLicenseMapping
    Enable-SPUserLicensing
    Is that correct? is anyone executed the above command?
    please advice.
    thanks in advance,
    Ammar

  • SharePoint 2013 and MS Office Web Apps - error in sharepoint's url calls OWAps

    I have new SharePoint 2013 Server farm and one dedicated Office Web Apps (OWAps) server.
    This farm is placed in one domain (Acompany.local). There is other domain BCompany.local whitch has both trusted to first domain (two diffirent forests, two company's branches).
    Users from second domain BCompany.local well see intranet portal, build in sharepoint in the first domain (url like http://intranet.Acompany.local).
    But, when they try to use OWAps, f.e. whatching preview or try to open docs for edit in browser - they see error in frame.
    I'm looked it in google chrome's developer tools and find' that sharepoint use wrong url to call OWAps - like http://owaps/... instead of http://owaps.Acompany.local/...
    When I created new office web app farm by:
    New-OfficeWebAppsFarm -InternalURL "http://owaps.Acompany.local" - ExternalURL "http://owaps.Acompany.local" -AllowHttp -EditingEnabled
    And in sharepoint farm new SWOPI binding by:
    New-SPWOPIBinding -ServerName "http://owaps.Acompany.local" -AllowHTTP
    Get-SPWOPIBinding tell that all SWOPI bindings are http://owaps.Acompany.local, but in devtools I continue to see wrong http://owaps/... url
    Any idea to fix this behavior?

    The reason WAC is recommended to be installed on a dedicated server is that it recreates the IIS sites/settings. This is why you're seeing the setting reset itself after restart.
    What I'd probably recommend is creating a script that queries the WAC URL on a regular basis.
    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 server for Lync DNS question

    We are going to deploy an Office Web Apps server for our Lync 2013 clients, available internally and externally. We do not have a split-horizon DNS so it is not possible for wac.foo.com to have a different IP for internal vs. external clients. What is the
    best setup for our scenario? It looks like we can only add one address in the Lync topology builder, so would it make sense to send everybody to the external wac.foo.com regardless of whether they are internal vs. external? Or is there a better option?
    Thanks,
    Matt

    It might be easiest to use pin-point DNS.  Create an internal zone called wac.foo.com with a blank A record that points to the internal IP address of the OWAS/WAC server.  This way, wac.foo.com will resolve to the correct
    internal address, but you're not setting up a split zone for the rest of foo.com.
    This trick can come in handy for publishing other items without recreating the entire zone, it's a nice one to keep in your back pocket.
    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".
    SWC Unified Communications

  • 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

  • Should the Edit in Browser link appear when Office Web Apps is read only?

    Hi,
    We have deployed an Office Web Apps farm in read only mode for licensing reasons.
    There is a binding between SharePoint 2013 and the Office Web Apps farm, everything is working well, except the option to Edit Office documents using Office Web Apps is quite prominent on the ECB menus and document previews.
    Is anyone able to advise whether this is expected behaviour? When the link is clicked a friendly error message states that licensing doesn't support editing, which is correct. I'm just trying to see if the user experience can be improved by a setting that
    we've missed somewhere along the line.
    Thanks in advance.

    Hi,
    Per my knowledge, if you have configured Office Web Apps for SharePoint, the Edit in Browser option will appear in the ECB menu regardless of the licensing of the Office Web Apps.
    So I recommend to use CSS code to hide the Edit in Browser option if you do not want the user to use it.
    Edit the page of the document library view page, and then add a Content Editor web part to the page.
    After that add the code below to the Content Editor web part:
    <style>
    a[Title="Edit in Browser"]{
    display:none !important;
    </style>
    Thanks,
    Victoria
    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]
    Victoria Xia
    TechNet Community Support

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

  • Office Web Apps 2013 Error

    Hi all,
    Currently we are facing a problem in our Sharepoint 2013 environment with Office Web Apps Server.
    Initially we connected the Office Web Apps farm to the Sharepoint farm and it worked well, but suddenly, we are not able to see the previews of the documents in the hover pannel or openning the documents in a new window or same window (doesn´t matter). We
    receive the following error message:
    Sorry, something went wrong
    An error has occurred on the server.
    This with a correlation error code, if we search this error code in Sharepoint we find the following information:
    WOPIFrame - Unhandled exception: System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract], cannot be used for communication because it is in the Faulted state. at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed() at System.ServiceModel.ChannelFactory.EnsureOpened() at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via) at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel() at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst) at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext) at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo) at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user, String applic...
    ationContext, DateTime& validTo) at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl) at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, String proofKeyId, SPUrlZone zone, Int64& ttl) at Microsoft.SharePoint.Utilities.SPWOPIHost.GetWOPITargetInternal(HttpContext httpContext, SPWeb web, Object& spPrimeObject, SPWOPIAction& requestedAction, SPRegionalSettings spSettings, String& wopiAppUrl, String& wopiFavIconUrl, String& wopiAccessToken, Int64& wopiAccessTokenTtl, String& errorMessageToDisplay, String& redirectUrl) at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoadHelper(WOPIFrame frame) at Microsoft.SharePoin...
    t.ApplicationPages.WOPIFrameHelper.OnLoad(WOPIFrame frame)
    anyone has faced a problem like that?
    Thanks in advance

    Stephan,
    1.  with the Get-OfficeWebAppsMachine command I can see that Health Status report as Unhealthy, but the reason for that is the certificate, it does not include the fqdn of the office web apps machine (Yes, I know that this is not the optimal configuration)
    2. If we try to navigate trought the URL
    https://..../hosting/discovery it shows the xml file of the owa server, no problem here
    3. Get-spwopibinding shows all the bindings configured as default, we haven't done changes here
    4. get-spwopizone = external-https the sharepoint platform is published as extranet trought a TMG, office documents can be accessed externally by WOPI server
    5. I have tried both methods, with true and false with the same result, I have tried to reboot several times the WOPI server.
    And for the final question, yes I have checked the event logs, but shows nothing, I think that is more a problem of Sharepoint previews than other problems

Maybe you are looking for