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.
Related
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.
We just upgraded our MS Access to 2013 and I'd like to know why I am encountering an error message when trying to create a blank custom web app in access 2013.
ERROR:
"an error occured in the client while attempting to communicate with the server"
I find it very weird as I have tried to export a table on my Access desktop Db and it successfully created a list in sharepoint using the same sharepoint path.
I provided the same sharepoint path when creating the new custom web app, anyone encounters the same issue? Our sharepoint is 2010.
It sounds like you are using an on premise SharePoint setup within your organization, correct? And your SharePoint Server is SharePoint 2010, correct? If that is indeed correct, you can't create or edit Access 2013 web apps on that server. In order to create and edit Access 2013 style web apps, you need several elements: Access 2013, a SharePoint Server running SharePoint 2013 (not 2010), the appropriate licenses for Access Services (the 2013 service that can come bundled with SharePoint 2013), and SQL Server 2012 or higher.
If you are using Office 365 to host your Access web apps, most of the existing plans include Access Services where you can create and edit Access web apps.
I have been working with SharePoint online for sometime.I have been given the task to build an app to create subsites in SharePoint 2013 online website. I prefer working with C# code. I am looking into SCOM to built the App.I want to know if this can be done or does online version only supports JavaScript COM development.
I have gone through multiple materials from Microsoft but no were its clear about autohosted app running on SharPoint online.
I have created a SharePoint App project and set it to autohost. But it throws token not found error while trying to run it against sharepoint online. Looking for advice.
Edit - I need to know if SCOM can be used to develop apps for SharePoint online site
Thanks.
Sounds like you're just starting off with SharePoint apps. SP apps use CSOM (client side object model). I personally prefer JavaScript (JSOM) MSDN JSOM Basic Tasks
If you want to develop against an online environment, then select SharePoint hosted not autohosted. If you are using the app internally then continue, if you are hoping to publish it to the app store then you can report back that this requires full control permission which you are not allowed to request in an app published to the SharePoint store.
When I first started developing SharePoint 2013 online applications I found this article on codeproject a great help.
It might be usefull for you as well: http://www.codeproject.com/Articles/690015/SharePoint-2013-Online-App-Development-Part-1.
Alternatively you could give the official Microsoft Office 365 training kit a look. It's basically the same as SharePoint 2013 online.
http://www.microsoft.com/en-us/download/details.aspx?id=14889
I have alfresco running from a server
http://10.0.10.199:8080
and sharepoint running from port 80 i.e
http://sharepoint
I want to synchronize everything that is on Alfresco site,
http://10.0.10.199:8080/share/page/site/cnhg/
to a sharepoint site
http://sharepoint.site.org/cnhg
without having to recreate the entire site on sharepoint. I have already configured sharepoint module for Alfresco to allow online Editing using Sharepoint configuration. My alfresco version is 4.2
I think you may be misunderstanding the SharePoint protocol support that ships with Alfresco. The functionality allows you to use Microsoft Office applications to retrieve and store files in Alfresco via the SharePoint protocol. This uses Microsoft's built-in SharePoint integration but with Alfresco on the back-end instead of SharePoint.
There is currently nothing out-of-the-box that will do a sync between a SharePoint back-end and an Alfresco back-end.
There are third-party products and other open source projects that will do that sort of synchronization but nothing in the core product at the current time.
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%.