Office Web Apps 2013 with SharePoint 2013 Server

Hi All,
I have installed a separate server for Office Web Apps 2013 on Windows Server 2012 VM. I have followed TechNet's article on
Deploying Office Web Apps Server & exactly followed steps.
On SharePoint Server 2013 (Windows Server 2012), I followed TechNet’s article on
Configure Office Web Apps for SharePoint. The Office Web Apps on SharePoint 2013 environment works for
Excel document that shows “View in Browser” but
no Preview.
However, PowerPoint and Word documents doesn’t show “View in Browser”. I thought Internet Explorer 10 has some issue with Office Web Apps and checked on Chrome and results were same.
On SharePoint Server 2013 environment, I have configured 3 services applications, MMS, UPS and Excel Service.
1.) Do I need any other service applications to be enabled for OWA 2013?
I read number of blogs,
Installing Office Web Apps Server for SharePoint 2013 (Steve Mann),
Install Office Web Apps 2013 with SharePoint 2013 (Max Melcher) and Spence Harbar
(Enabling Office Web Apps Preview editing with SharePoint 2013). and all these blogs give more or less same steps that I have followed.
Strange thing is that Excel documents on my SharePoint 2013 sites are working but neither word or PowerPoint documents are not showing option for “View in Browser”.
I am using HTTP and not HTTPS.
2. Can someone please advice how could I solve the Office Web Apps 2010 on Word and PPT?
3. How to can enable preview for Excel, Word and PPT documents.
Thanks you.
Regards,
Aroh
Aroh Shukla

Hi Inderjeet and Olafur,
Thanks for your reply.
@Inderjeet: That site collection feature on SP2010 works on our production environment but on SP2013 site collection there is no OWA feature. Microsoft recommends to have a separate OWA2013 server and what I create
a separate VM for OWA2013 server.
@Olafur: Your suggestion looks spot on. The OWA server does show the discovery:
Our SP2013 development server has limited RAM (4GB) and it think is causing the issue.
Let me check if increasing RAM solves the issue.
Thanks again for your suggestions. (Interjeet and Olafur).
--Aroh
Aroh Shukla

Similar Messages

Failed to Sync OneNote 2013 with Sharepoint 2013 - Saying Required Properties option is selected

Hi All
I am trying to integrating OneNote 2013 with Sharepoint 2013, but whatever i do it came up as:
We can't sync because the Required Properties option is selected on the server. Disable the option, or move the notebook to a new location. (Error code: 0xE0000B9B)
I've followed knowledge based and turn off the Required Properties as i can see off, but error still showing up.
Has anyone encountered this error before?
Thanks a lot for any contribution.

HI G_Virus,
Please check if any field is set as required, then set it to optional for the OneNote content type from the problem library.
And also check Jannifer's reply mentioned that compare this content type fields to the OneNote without issue from other site collection or farm per the following post, see if it helps.
http://office.microsoft.com/en-us/onenote-help/resolve-document-library-errors-when-using-onenote-with-sharepoint-HA102647129.aspx
http://social.technet.microsoft.com/Forums/office/en-US/a0e8cb4e-6daa-4ef8-a856-337da837c5db/sync-error-to-sharepoint-2010-library-with-revisions-checkinout-not-enabled
Thanks
Daniel Yang
TechNet Community Support

Office web Apps preview of SharePoint 2010 source in SharePoint 2013 search results

Hi Team,
We have crawled SharePoint 2010 source in SharePoint 2013 and able to get results successfully. Now our requirement is to show Office Web Apps previes of 2010 documents in 2013 search results.
Any guidance on this please.
Thanks,
Manjeera

Hi,
Take a look at this blog post on how to do this: http://blogs.msdn.com/b/murads/archive/2012/10/11/utilizing-web-apps-2010-to-get-powerpoint-previews-of-sharepoint-2010-content-from-sharepoint-2013-search.aspx
Thanks,
Mikael Svenson
Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
http://techmikael.blogspot.com/
Author of Working with FAST Search Server 2010 for SharePoint

Office Web Apps 2010 on SharePoint 2010 site running in SharePoint 2013?

We're in the process of moving a SharePoint 2010 site over to SharePoint 2013. The SharePoint 2010 site is using classic authentication, and it's not in scope to update this to claims-based authentication.
I'd like to continue running the site in SharePoint 2010 mode without upgrading it to 2013. In this case, can I continue to use Office Web Apps 2010 for this SP2010 site? I've already installed Office Web Apps 2013 on another server but just
read that it needs claims-based authentication.

If you want to use OWA once the site has been moved to 2013 you will need to change the web application to use Claims. OWA in 2013 requires that and will not work in classic mode.

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

Excel 2013 Data From Web not working with SharePoint 2013?

In Excel 2013, on the ribbon select the 'Data' tab and 'From Web' to import data from a web page. Navigate to a SharePoint 2013 site with a table on the home page and you will not see the table import arrow on the table. With SharePoint 2010 you would have.
Any suggestions on a workaround/fix?
One thing to note, in SharePoint 2013 be sure to disable the Minimum Download Strategy feature on the site or you will get script errors in the New Web Query dialog.
Also, I realize this may belong in an Office/Excel forum so I have posted it there also.
Thanks, Fintan

Hi Fintan ,
According to your description, my understanding is that the Excel table import arrow disappears in the SharePoint 2013 page.
For your issue , I can reproduce your scenario in my SharePoint 2013 environment. It should be caused by the Excel Data connection from web page feature cannot identify the page layout which is
used by SharePoint 2013 . For a workaround, you export the HTML table using jQuery:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/30fc097f-256c-48d9-8b6c-cb821a504045/problem-while-exporting-html-table-to-excelcsv-in-sharepoint-2010?forum=sharepointgeneralprevious
http://community.office365.com/en-us/b/office_365_community_blog/archive/2013/07/31/how-to-use-power-query-for-excel-to-query-a-sharepoint-2013-list-grid-user-post.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Firefox 4.0.1 doesn't open web app from withing win 2008 server.

I have an asp.net web application hosted on IIS 6 , windows 2008 server. When i try to browse to this web application from within the server machine Firefox 4.01 throws error saying "Network Error (dns_unresolved_hostname)" . But i could browse to same web application using Firefox 4.0.1 from a remote machine.

The last Apple Supported OS for FCE was 10.6.8, that's three changes back.
Some users have luck with the newer OS systems.
Search this forum for discussions.
Al

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

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.

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

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

Will Office Web Apps Server 2013 work with SharePoint 2013 sites hosted in SP2010 compatibility mode?

We are planning a upgrade of a SP2010 farm to 2013. There has been a bit of customization so we wish to run the old sites on the new SP2013 platform in SP2010 compatibility mode.
So my question is will Office Web Apps Server 2013 work with the old sites hosted in compatibility mode?
I found a similar query from March 2014 found here
http://sharepoint.stackexchange.com/questions/93101/office-web-apps-2010-running-on-sharepoint-2013-for-compatibility-mode-sites/116281#116281
Has there been an update released to resolve this
Cheers D

Hi ,
According to your description, my understanding is that you need to know whether Office Web Apps 2013 is working with SharePoint 2013 sites which is in SharePoint 2010 compatibility mode.
For my test, Office Web Apps 2013 with SharePoint 2013 sites which is in SharePoint 2010 compatibility mode is working fine.
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 with SharePoint 2013 Server

Similar Messages

Maybe you are looking for