I've installed Microsoft office web apps offline in the VM and also Installed SharePoint 2016 in another VM machine. Both VMs are connected to the domain.
Besides, I've successfully connected SharePoint to the office farm. But when I try to open docx files or any other office app on the web browser I get the below error :
Failed to launch 'ms-word:ofv%7Cu%7Chttp://....' because the scheme
does not have a registered handler.
Based on the error that you have screenshoted, the Application falied to launch the MS Word Desktop Client because the scheme "ms-word" does not have a handler registered, which in simple terms means that there isn't any associated app to execute when the beforementioned scheme is used and in order to have the scheme registered with an application, you would have to install Microsoft Office on the machine that you are using to view the SharePoint Site.
Here is the link to the documentation where is states that the scheme handlers are registered upon the installation of Microsoft Office.
The following is the list of scheme names implemented in Microsoft Office applications. When Microsoft Office is installed, each scheme name is registered with Windows to be handled by the Office product of the same name. Note that "ms-spd" is an abbreviation for SharePoint Designer.
ms-word:
But in order to use the Web counterparts of the Office apps, like Word or Excel in the browser, there is a different procedure where it is required of you to Install a Office Online Server and enable communication with SharePoint Server.
As it is written in the overview of the product...
Office Online Server delivers browser-based versions of Word, PowerPoint, Excel, and OneNote. A single Office Online Server farm can support users who access Office files through SharePoint Server, Exchange Server, shared folders, and web sites.
Since it's a lengthy procedure and there are different prerequisites in term of licensing and other matters, you can check out this link (Configure Office Online Server for SharePoint Server) on the topic and decide which features you are looking for.
Related
I started recently to build a office add-in (the web-based ones, not VSTO) and I would like in addition to have it in the office store (the preferred method of distribution) to also distribute the manifest through a setup file. Is this possible?
I searched around the web but the only things that come up are for VSTO add ons.
Web add-ins are not designed for distributing via standalone installers like MSI. You/administrator can sideload them for the organization unit (OU) or just install them from the store. See Centralized Deployment via the Office 365 admin center for more information.
How are the desktop versions of Microsoft Office 2016 products able to retrieve documents from and save documents back to One Drive when they (the desktop versions of Office 2016) are not WOPI (Web Application Open Platform Interface) clients?
I suspect that the desktop Office and One Drive integration looks more like an OAuth 2.0 implementation rather than a WOPI one.
I'd love to hear how that works, and especially would love to have it be confirmed whether or not the desktop versions of Office are WOPI clients (looks like they aren't because WOPI is for Web based applications).
Also, does Microsoft have any future plans to have desktop versions integrate with custom, third-party cloud storage providers? In other words, to make something like WOPI but for desktop clients like Office 2016? DOPI (Desktop ...) perhaps? :-)
Desktop versions of Office are not WOPI clients.
Office <-> Sharepoint is WebDAV
Office <-> OneDrive is not a real integration. It just uses OneDrive's file based synchronization.
More detailed observations can be found in my other answer here
Not sure about the future plans of Microsoft but you can certainly create integrations with desktop versions of Office by implementing the WebDAV protocol. There are many examples and paid SDKs on the internet that'll save you from writing boilerplate code.
I have written a small officeJS addin for excel which run perfectly on desktop excel client. Also office online from onedrive gives an option of installing the addin from the ribbon menu. I want to use this officeJS addin to run on either of the following configuration:
On premise office online server configured with on premise
sharepoint server.
On premise office online server with my own
implementation of wopi host.
How to deploy an officeJS addin on office online on premise server which is preferably managed centrally by the administrator.
Also why is the add-ins option is not available on the office online configured with sharepoint, pfa image:
office online onedrive v/s office online onprem with sharepoint
Thank You
The Office Online Server currently doesn't enable Office store by default. As part of the configuration, you'd have to enable it. I'm not 100% sure about the exact setting. It may be this: set the AllowExternalMarketplace flag to true.
More here
Try this. On a server in the farm, open the SharePoint Management Shell (PowerShell). Run this command:
Set-OfficeWebAppsFarm - OfficeAddinEnabled:$true
You probably have to be logged in as a farm administrator.
There is some documentation here: Set-OfficeWebAppsFarm
I've noticed Microsoft has released a new version of Office Web Apps Server 2013, which is a standalone product now.
I'm looking for an engine that I can convert Word/Excel and PowerPoint documents into web-friendly versions (HTML5) for an application I've built that uploads these documents to S3 and I thought Office Web Apps Server 2013 standalone would work.
I don't want to use Google Docs, but rather use a solution that I'm hosting myself.
Reading the Office Web Apps Server documentation, it doesn't specify whether or not I need to have a SharePoint server license. I've tried deploying Office Web Apps Server on a Windows 2012 server on Microsoft Azure, and while the software installs, it is unable to render any documents that I'm pointing to it from an external URL (a publicly accessible S3 bucket).
Does anyone know the particular requirements of Office Web Apps Server 2013 to work properly? The website does state that it can be used to view documents from an external URL which is how I'm trying to use it. But since its a new product, there isn't that much information I was able to find on it other than Microsoft's deployment instructions.
I know that using SharePoint internally is free, but what if I create an application that will provide some of the data stored in SharePoint externally? Is it legal way to do things or do I have to pay for full SP licence to do that?
The cheapest option in your case may be to install WSS + Sql Server 2008 Express on Windows Server Web Edition (~£400) to avoid paying for CALs or External Connector.
Only Windows Sharepoint Services (WSS 3.0) is free and included in Windows 2003 and 2008 and thus being licensed along with it. If users need to authenticate on the site (i.e. using forms auth), then you either need a Windows CAL for each user or an External Connector License. If you do not have user accounts ("Anonymous access"), then you should not need any additional licensing.
On the other hand, Microsoft Office SharePoint Server 2007 (MOSS 2007) is a commercial product that requires licenses for any use, internal or external.
IANAL, so check with MS Licensing for this.
Using SharePoint internally is not free. You need server licenses for each server copy you have and client access lincenses (CALs) for every client that uses it - internally. There is a separate model for licensing SharePoint hosted and published externally.
You should talk to your microsoft licensing provider about this, it's not really a programming question, it's a licensing question.
There is a licensing fee for providing SharePoint connected to the intrenet. the situation where you have your own application reading data from SharePoint (e.g. webservices/rss) and exposing that to the internet is quite different and not likely to be considered for licensing.
Given that you are only exposing part of the data and none of the interface, you should be okay. If you are using CALs to access SharePoint, I believe the user running the application you access SharePoint with would use up one of those CALs.
You would really need to check with your SharePoint licensing guys to be 100%.