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.

Similar Messages

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

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

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

Office Web Apps for Hosted Environments

Hi there,
I have a some servers that host two different SharePoint Farms and currently one is connected to an OWA server -
http://blogs.technet.com/b/justin_gao/archive/2013/06/30/configuring-office-web-apps-server-communication-using-https.aspx
I want my second farm to use OWA too and was wondering if it is possible to use the same OWA server for this? So, can I create two Office Web App Farms on the same server?

Yes you can use OWA for multiple environments. You can refer to below links:
http://social.technet.microsoft.com/Forums/en-US/78f678cb-69fc-48e6-9f4d-6985154f2d0c/office-web-apps-with-multiple-sp-farms?forum=sharepointadmin
http://blogs.technet.com/b/office_resource_kit/archive/2012/09/11/introducing-office-web-apps-server.aspx
Please ensure that you mark a question as Answered once you receive a satisfactory response.

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 - Office Web Apps was unable to find the specified certificate

Hello,
Let me start by saying I did not see a forum listed for Office Web Apps and figured the SharePoint forum would be the second best place to post this. With that said, here's my issue...
I installed OWA 2013 on a Windows Server 2012 (not R2) VM and installed all the prereqs as described here: http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx Since this is a test environment, I'm planning on using a self-signed
cert which appears to be supported based on info found here: http://technet.microsoft.com/en-us/library/2e147f11-6f47-46bc-90bf-b2f179958d11(v=office.15)#certificate.
I created the cert using the following command:
New-SelfSignedCertificate -DnsName owa.test.local -CertStoreLocation cert:\LocalMachine\My
I then edited the cert's properties in the Cert Manager MMC snap-in and added a friendly name of "2014_OWA_Cert". I then proceeded to try and create the OWA farm by running:
New-OfficeWebAppsFarm -InternalUrl "https://owa.test.local" -CertificateName "2014_OWA_Cert" -EditingEnabled
This produces the following error:
New-OfficeWebAppsFarm : Office Web Apps was unable to find the specified certificate.
At line:1 char:1
+ New-OfficeWebAppsFarm -InternalUrl "https://owa.test.local" -CertificateNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [New-OfficeWebAppsFarm], ArgumentException
+ FullyQualifiedErrorId : CertificateNotFound,Microsoft.Office.Web.Apps.Administration.NewFarmCommand
What gives?

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
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 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.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

Office Web Apps 2013 - Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word

Hello
I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.
The error message I get for WORD, PDF and Excel files is:
The ULS logs on the WFE give me this:
WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
01/08/2014 11:01:58.01*   w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             afk59   Monitorable
WOPI                             agxqc   Medium     WOPI Signature verification
attempt failed with public key 01/08/2014
11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             agxqc   Medium     WOPI
Signature verification attempt failed with public key
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             agxqb   Medium     WOPI
Signature verification attempt failed - no public key   e75ead18-af27-4d44-ba50-b38b408011e8
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             ahdzz   Monitorable   WOPI
Proof: All WOPI Signature verification attempts failed   e75ead18-af27-4d44-ba50-b38b408011e8
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             ag7pj   Unexpected   WOPI
(CheckFile) - Invalid Proof Signature for file Letterhead Template.docx url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi
The ULS Logs on my Office Web Apps server gives me this:
Error message from host: Verifying signature failed, host correlation:    d197d187-ef9d-42f6-ae4f-c4b8199c1078
WOPICheckFile,WACSERVER FileNotFound
WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404
Any idea what may have caused this issue all of a sudden?
Thank you.
Yoshi

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
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 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.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

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.

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

I've got a brand new Exchange 2013 CU2 farm set up, 2 CAS servers and 2 mailbox servers in a DAG and I'm trying to add an Office Web Apps 2013 server into the mix. First, can someone give me a reason why we would want or need an Office Web Apps server, if
all that's integrating with it is Exchange? From what I've read, it only offers Office document previews, but it appears to already have that functionality. Does it offer editing capability?
Second, I've followed all the guides I can find on integrating OWA (there has to be a better acronym for this) and Exchange, but I'm still getting errors when I try to preview an attachment.
For Word, it says "Sorry, there was a problem and we can't open this document." For Excel, it gives an ASP-style error that says "Server Error in '/x' Application" behind the words "Excel Web App" and a continuous progress bar.
For Powerpoint, it says "Sorry, we couldn't open this presentation because we ran into a problem."
I've tried building a new OWA server, running 2012 R2 and all the updates, and the only commands I've run on the OWA server are "New-OfficeWebAppsFarm", giving the internal URL, the external URL, enabling editing, and giving the friendly name of
the certificate (which is a valid cert). On the Exchange side, I've run "Set-OrganizationConfig -WACDiscoveryEndpoint 'https://fqdn-of-owa-server'" and "Set-OwaVirtualDirectory -WacViewingOnPublicComputersEnabled $true -WacViewingOnPrivateComputersEnabled
$true -ForceWacViewingFirstOnPublicComputers $true -ForceWacViewingFirstOnPrivateComputers $true" for both CAS servers.
I've also tried it from different browsers, and added the OWA URL to the Trusted Sites in IE10 and IE11, but no dice.
Am I missing something? Even if I get the integration to work, what benefit does it give me?

Hi,
Office Web Apps Server Integration
http://technet.microsoft.com/en-us/library/jj150495(v=exchg.150).aspx
Recreated Office Web Apps farm and WOPI Bindings on SharePoint as follows:
===================
Remove-OfficeWebAppsMachine
New-OfficeWebAppsFarm -InternalUrl "xxxx" –AllowHttp
Set-OfficeWebAppsFarm -EditingEnabled:$true
Get-OfficeWebAppsFarm
Get-OfficeWebAppsHost -> „allowList“ war empty
New-OfficeWebAppsHost –domain „xxxx“ to add the domain in the allowList
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Office Web Apps Farm - undo the AllowHTTP switch

Similar Messages

Maybe you are looking for