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

Similar Messages

  • Open links to documents with Office Web Apps

    Hi,
    I am trying to configure SharePoint 2013 and Office Web Apps Server 2013 in a Multi Tenant environment for a client that has specific requirements when it comes to document handling.
    They have a number of document libraries where the majority of their user base will only be able to view the documents it contains using the Office Web Apps Viewer and not be able to download it or access it using the local client (Their SharePoint Group
    membership has View Only Permission on the Site).  We see exactly this behaviour when the documents are accessed from within the Document Library App or associated Web Part but not if the documents are linked to from elsewhere within the Site, e.g. The
    library in question is being used to store newsletters and they want to be able to insert links to the latest newsletter in an Announcement or Newsfeed item. As it stands these links present the user with an access request page or with Read permissions on
    their SharePoint Group a browser download dialog.
    My initial searches have so far brought up a suggestion to
    doing the reverse in search which might be promising and updating workflows to modify the url provided in an email to the appropriate wopi url which in my mind suggests a user manual.  Something that would work automatically on at least the
    Site, better Site Collection or ideally Site Subscription level is what I am looking for as our clients users are far from technically minded and a lookup table of file extensions and how to construct the url is out of the question.
    Thanks in advance for any help or advice provided.
    Matt

    Hi,
    I am trying to configure SharePoint 2013 and Office Web Apps Server 2013 in a Multi Tenant environment for a client that has specific requirements when it comes to document handling.
    They have a number of document libraries where the majority of their user base will only be able to view the documents it contains using the Office Web Apps Viewer and not be able to download it or access it using the local client (Their SharePoint Group
    membership has View Only Permission on the Site).  We see exactly this behaviour when the documents are accessed from within the Document Library App or associated Web Part but not if the documents are linked to from elsewhere within the Site, e.g. The
    library in question is being used to store newsletters and they want to be able to insert links to the latest newsletter in an Announcement or Newsfeed item. As it stands these links present the user with an access request page or with Read permissions on
    their SharePoint Group a browser download dialog.
    My initial searches have so far brought up a suggestion to
    doing the reverse in search which might be promising and updating workflows to modify the url provided in an email to the appropriate wopi url which in my mind suggests a user manual.  Something that would work automatically on at least the
    Site, better Site Collection or ideally Site Subscription level is what I am looking for as our clients users are far from technically minded and a lookup table of file extensions and how to construct the url is out of the question.
    Thanks in advance for any help or advice provided.
    Matt

  • Got errors when trying to open word document with Office Web App Server and customized WOPI host

    I am configuring the Office Web App Server with our ASP.NET MVC WOPI host based on this example. https://code.msdn.microsoft.com/office/Building-an-Office-Web-f98650d6. While both the OWA server and WOPI server has been set up and I can use Excel and PowerPoint
    app to open and edit xls and ppt file now, there are problems opening word documents no matter I enable or disable the editing function of OWA server.
    When I open a word document while enabling editing I got this error:
    If I disable editing I got this message:
    I have tried several file so I thought it is not the files' problem. Also I didn't find any exception in the log of OWA server. 

    Hi Gary Jiang,
    Thanks for posting in MSDN forum.
    This forum is for developers discussing issues about
    apps for Office.
    Based on the description, it seems that you got an issue when you deploy the code sample. If I understood clearly, I suggest that you contact the author of the code sample from the "Q and A" tab.
    Also if you have the question about WOPI, I suggest that you get more effective response from
    Office
    Protocols forum.
    Regards & Fei
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Exchange 2013 OWA published through TMG: Unable to preview documents with Office Web App server

    We configured our Exchange 2013 servers to use Office Web App for document previews on OWA. Everything works fine internally, and externally also when we access OWA directly. But when from an outside network we open a OWA session through TMG and try to preview
    a document, we get the error "Sorry we cannot open this document, an error occured . . ."
    Did anyone experience such an issue ?
    Thanks,
    Antonio

    Hello,
    Since directing accessing OWA from CAS is fine and the issue only occur when involving TMG, I think the issue is more related to TMG settings. Please find more efficient support
    via our TMG forum:
    http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/threads
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • New Document button to create/open document in Office Web Apps rather than through Template.doc in client's MS Word

    Greetings all,
    We have a particular campus with exceptionally limited access on their machines -- essentially, they can browse the web (access our Intranet) but not write information to drives or update their MS Word to read the new DocX format (or install plugins, etc,
    to do so).
    The new Web Apps seems to provide some potential for alleviating their issue -- but ideally, they would be able to originate (create) new documents right in Sharepoint by clicking on New -> Document and having the new document open in Office Web Apps
    rather than downloading / creating through Template.Doc (standard method in Sharepoint).
    Any ideas about how to make this kind of functionality happen?
    THanks!
    ---Dave

    When you mention "web apps" I assume you're referring to the new "Office web apps" in SharePoint 2010, so I'm not sure why this question is in a pre-sharepoint 2010 forum...  My answer entails how to go about doing this in 2010 only.
    In the document library's settings, go to advanced settings, and choose for the files to be forced to be opened in the browser, instead of the client software. 
    By default, you're only going to have a new word document for your "new" button.  You'll need to create content types for all the other document types you want them to be able to create.  So create a blank spreadsheet, and save it on your desktop,
    and create a blank powerpoint too. 
    Then create new content types at the top level of the site collection.  One called Excel Template, and one called PowerPoint template.  For each content type, click on the advanced settings and upload that blank file that you created. 
    In your document library, go to the library's advanced settings and change "allow mgmt of content types" to YES.  Then, in the content types section add those 2 new content types you created. 
    Now, when people click the "new" drop-down, they will have choices of a word document, excel and powerpoint, and they will open in the browser.
    Laura Rogers, MCSE, MCTS
    SharePoint911: SharePoint Consulting
    Blog: http://www.sharepoint911.com/blogs/laura
    Twitter: WonderLaura
    Beginning SharePoint 2010: Building Business Solutions with SharePoint

  • Office Web Apps Server 2013 - Word Web App - Problem with Tab space

    Hello We have Office Web Apps Server 2013 running with SharePoint 2013.  Users Editing a Word document with Office Web Apps, can't use "Tabs", any Word document with Tabs; the tabs are replaced with a single space.
    Has anyone noticed this?  Is this a bug?
    -thanks
    thomas
    -Tom

    Yes, currently the Word Web App does not support
    Tab Keyboard shortcut for editing document content .
    For more information, you can have a look at
    the article:
    http://office.microsoft.com/en-us/office-online-help/keyboard-shortcuts-in-word-online-HA010378332.aspx?CTT=5&origin=HA010380212
    http://social.technet.microsoft.com/Forums/en-US/3f5978d3-67a1-4c8c-981f-32493d72610b/office-web-apps-server-2013-word-web-app-problem-with-tab-space?forum=sharepointgeneral

  • 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

  • SharePoint 2013 Anonymous (public) site and Office Web Apps Server 2013 issue with download.aspx

    Our organization has a public facing anonymous site in SharePoint 2013 which allows access to documents (docx) in a library.  ViewFormsLockdown is activated as we present the documents via CQWP / custom template.  We are combating the usual
    issue of multiple login prompts when using Internet Explorer when a user accesses said document.  We also have tried  using the Word Viewer (view only mode) from Office Web Apps Server 2013 which works well, but ...
    the problem stems from the fact that users can go the file menu from the word view and choose to download the document (which is what we want),  unfortunately it looks like the link redirects via /_layouts/15/download.aspx which also presents a login
    prompt. Much has been written out there about doing direct links for documents via /_layouts/download.aspx to address multiple login prompts when the document is opening in word (from IE).
    I've tried nearly every combination of recommendations (disabling client integration, browser file handling (permissive/strict), ViewFormsLockdown feature, web.config modifications with options and propfind verbs and more) all to varying levels of success,
    but never totally getting rid of the prompt.  It has been stated that because the downloads.aspx inherits from Microsoft.SharePoint.ApplicationPages.Download this will not allow anonymous access.  We really want to use the word view from the Office
    web app and have the file download functionality work from the menu there ... can anyone suggest an alternate fix?  I might be wishing but will appreciate any guidance offered ...
    cheers,
    Dean
    some reference links (but not all) for various things we've tried:
    http://mohitvash.wordpress.com/2013/06/18/sharepoint-download-a-file-programatically/
    http://blog.sharedove.com/adisjugo/index.php/2012/09/29/open-sharepoint-files-in-edit-mode-from-client-applications-and-not-read-only/
    http://stackoverflow.com/questions/375390/office-documents-prompt-for-login-in-anonymous-sharepoint-site
    http://yalla.itgroove.net/tag/anonymous-access/
    Glifnard

    I'm glad to here that the problem has been fixed. Thank you for sharing your experience here, it will be helpful to other community members who have similar questions.
    Cheers,
    Steve Fan
    TechNet Community Support

  • 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 App Server 2013: cannot edit word document with own WOPI Server

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

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

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

  • Sorry, something went wrong - Open Office File from Search Results Page with Office Web Apps

    Hi,
    I'm getting "Sorry, something went wrong" error when I'm trying to open any office document from inside Search Results Page with Office Web Apps, the same error is appearing in the document preview as well.
    The error in SharePoint logs says that the file cannot be found.
    Please note that this error is coming only when the "Filename" of the document is not written in English (in my case its written with Arabic characters).
    If I try to open it from the document library, its opening properly with no errors.
    The only difference between two URLs (document URL in Search Results and in Document Library) is the value for "sourcedoc" attribute;
    In the case of Search Results page, the filename in "sourcedoc" attribute is kept as is with Arabic characters.
    While in the Document Library, the filename in "sourcedoc" attribute is converted into different characters (something like: "B9%D9%85%D9%8").
    Anybody have an idea on how to overcome this issue, implement a workaround or modify the "sourcedoc" behavior?
    Thanks in Advance.
    Hamza AlSughier

    Dear Wendy,
    Thanks for your efforts, I already tried your last suggestion before, but this didn't solve my problem.
    Actually my end users are accessing this portal using ADFS and HTTPS.
    Finally I got this solved, I have done below to get my overall solution working perfectly:
    - First I have configured Windows Authentication and ADFS Authentication on the same zone which is the default zone.
    - The issue when opening office documents with Arabic file name has disappeared as a result of first change.
    - Then I have faced an issue where we are not able to crawl content under Default zone, however we have to do so, after too many efforts, I found that its related to the Load-balancer/proxy, I have made the crawler server
    to crawl himself (http://CrawlServerName:PortNumber).
    - Also a change on Alternate Access Mapping was needed, I have set one of the extended zones (which is running Windows Authentication only) as Internal URL for the Default Zone, and this is was the URL I used for Crawling.
    I have configured Server Name Mappings to make sure we got proper URLs in Search Results.
    - Then we faced another issue, which is Authentication selection on login page (How to bypass this page, and authenticate using ADFS auto), I used this solution (Set Custom Sign In Page):
    http://0ut0ftheb0x.wordpress.com/2014/01/04/skip-the-authentication-selection-page-at-_logindefault-aspx-in-a-mixed-authentication-environment/.
    - I faced one more issue as a result of above workaround; Sign Out functionality wasn't working well; users get logged in automatically whenever I click on Sign Out. I solved this by modifying the "Sign Out" Control under _layouts;
    I made it to redirect users to ADFS Sign Out Page instead of SharePoint Sign Out Page (I know its not recommended, but I don't have any other option).
    Hamza AlSughier

  • Installing Office Web Apps Server 2013 fails with app-crash during install.

    Hi Folks,
    I am trying to install Office Web Apps Server 2013 with SP1 on Server 2012 R2.  The installation gets half way through then crashes (it just says a problem has occurred).
    The Event log only contains the message:-
     MsiExec.exe version .5.09....
    Faulting module name: Kernelbase.dll
    Exception Code 0x306d7363, Faulting process id: 0x774.
    Does anyone know how to install this product on Server 2012 R2?

    Hi,
    I’m afraid that this case is off-topic in this forum, About installation of Office Web Apps Server 2013, I suggest you posting your case to
    SharePoint 2013 - Setup, Upgrade, Administration and Operations .
    Regards,
    Marvin
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Printing Word documents to PDF from Office Web Apps Server 2013 yields inaccessible PDF files

    I have Office Web Apps Server 2013 SP1 with March 2015 CU applied. The version shows up as "15.0.4569.1506" using Todd Klindt's
    method. When anonymous users view the Word documents online through the Office Web Apps, they have an option to print them to PDF. The PDF file that gets generated as a result isn't accessible
    (i.e. it isn't WCAG-compliant). using Adobe Acrobat Pro to check it I can see that it is missing tags, for example. The source Word document was made fully accessible from the point of view of Microsoft Office accessibility tools.
    When viewing the same document in Word Online in Office 365, I get an extra option  "Download as PDF". The PDF document produced is accessible. If I save a Word 2013 document as a PDF from within the Word editor, it also generates accessible
    PDF.
    I was wondering if the reason for the accessibility problem that I have misconfigured my on-premises Office Web Apps,  or perhaps the accessibility compliance isn't built in yet. If the latter is true, I was wondering if someone could indicate whether
    or not this is on the list of upcoming CUs.
    thanks in advance. 

    Just check my WAC install, no this is likely an Office online only feature, at least at this point in time.
    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.

  • Is there any solution for convert document spreadsheet presentation to images with Office Web Apps?

    Hi there!
    Is there any solutions for convert document spreadsheet presentation to images with Office Web Apps?

    Hi,
    As far as I know, there is no build-in feature that convert Office file to image format in Office web app yet.
    I'll collect the information, and submit it with internal ways. Then, we could also submit the feedback here:
    http://office.microsoft.com/suggestions.aspx
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

Maybe you are looking for