Tag Info

Hot answers tagged

6

I found the best programmatic solution: The SPUtility.MapToServerFileRedirect function. In the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML directory are a bunch of ServerFiles XML files that tell SharePoint how to redirect certain types of files, etc. Office Web Apps uses this to redirect links to Office files to ...


5

Co-authoring will be revolutionary I reckon, it's in my 'top 5 drivers for clients to upgrade to 2010'. In answer to your questions: SharePoint Foundation is fine. Yes web and rich client (i.e. Word 2010) both support co-authoring, the experience is basically the same from what I've seen. Probably, but remember that whoever hosts the functionality also ...


4

Here's one way I've been able to "convert" a DOC to DOCX, although it's all manual, is to Open the doclib in Explorer view/open in Explorer Open the file in question (check-out if needed) "Convert the file" Save the file locally Rename the file extension in Explorer view (if you have it opened in Word, SP will complain that the file is locked) Upload the ...


4

It's actually possible to rename/move a file, but you must do it programmatically using client object model or server object model - File.MoveTo Here is an ugly example (didn't test it, might be some typo): using Microsoft.SharePoint.Client; .... using(var ctx = new ClientContext("http://yoursharepoint/web_containing_library/")) { var lib = ...


3

The easiest way I have found is to use the [SPWebApplication.GrantAccessToProcessIdentity][1] method. It grants the specified user account access to the process identity and provides full control of the SharePoint Web Application. Office Web Apps can use this to access the content databases as the SharePoint Web Application's process identity, which already ...


3

If you run your farm on least privilege settings, you can get the above error. Be aware of the security demand for the Word Viewing Service are quite high: When you create a new application pool, you can specify a security account that is used by the application pool to be either a predefined Network Service account or a managed account. The account ...


3

I created a blog post about this today: Create a new document using Office Web Apps. ID is the URL to the document template that is associated with the content type. Ex.: http:// www.yourdomain.com/TeamSite/template.docx` SaveLocation is the location to the document library where the document needs to be saved. Ex: &SaveLocation=http:// ...


3

You need to enable the "SharePoint Server Enterprise Site Collection features" Site Collection feature. And Office Web Apps is not Excel Services. In Office Web Apps (is OWA the correct acroynom?) you have the Excel editor/browser which is not the same as Excel Services.


3

As a very general rule, and I hope I am not doing it an injustice, the Office Web Apps are great for viewing documents, but the editing experience will fall well short of the full client experience. If your end users are editing documents I would recommend going with the full Office client. If they are just viewing, OWA is probably good enough. If your ...


3

You do not have access to the DIP in Office Web Apps. Since you're using the web UI already it's easy to go the the item in the library and change it's properties there. If you need more advanced DIP's (for instance built with InfoPath) then you need to modify the edit, new and view forms of the page to get the "same" experience as in the full fledged Office ...


3

The AutoSPInstaller (http://autospinstaller.codeplex.com/) was actually creating self-signed certificates on the server that the WAC did not trust. So we had to manually create the certs and a CA so that the trust would work properly. This corrected our issue.


3

We raised the issue with Microsoft Support and apparently it's a bug. Will know more soon. In the meantime, the fix is to disable PDF's from being rendered in OWA: Get-SPWOPIBinding –Application "WordPDF" | Remove-SPWOPIBinding -Confirm:$false Control whether PDFs open in Word Web App or the default PDF reader ...


3

Office Web Apps Licensing has recently changed (11-24-2014) in regard to SharePoint 2013, when SP2103 was first released, there was no license needed for "Read only" access, and Office client license needed for "edit" (on your honor enforcement). This has been changed (and the download location changed). You now need an Enterprise Agreement to install it ...


3

Here's some links that might help you understand better and get started: https://msdn.microsoft.com/en-us/library/office/fp142381.aspx and https://msdn.microsoft.com/EN-US/library/office/fp179923.aspx And to better answer the question, provider hosted apps are applications that run in a server that is external to SharePoint's. It has its own infrastructure ...


2

I don't see how this would be possible as changing the file type from DOC to DOCX would create a new item...i.e. you can't change the name of a SPFile object. Your best bet is to probably write some code or a script to convert the docs as you migrate them to a new library along with their metadata and then retire the original doclib.


2

I would suggest you to build a custom tool e.g. command line, webpart, central admin custom action or something else to trigger the conversion process. The code should do the following: Find all SPListItems with targeted *.doc files Convert the DOC file to DOCX with word automation services Check if check-out is required/possible (the item could already be ...


2

You first have to add your site collection url to the list of trusted excel services locations. After that you should have the option to open in web in any document libraries in that site collection.


2

Unfortunately, you will have to install Office Web Apps on your farm.


2

As per your requirement you should go with the Office Web Apps. I will also works fine with Sharepoint 2010 Foundation and you can also download it from volume licensing program of Microsoft. Here is an post that shows system requirements of Web Apps. http://technet.microsoft.com/en-us/library/ff431682.aspx And these are the steps to install and configure ...


2

When slip streaming, ALL (SP, CU) your updates go into the updates folder in the installation source of your application. The language packs go into the language updates folder. When you install from the source, everything in the updates folder gets processed. Here is post by Ron Grzywacz on MSDN regarding this topic Service packs and LP slip-streaming. ...


2

No, there is no configuration option to make this happen. In addition, the Office Web Apps use their own master pages, so editing the master page of your SharePoint site wouldn't even give you the option to do it on the client side.


2

You'll need to use the Open XML SDK 2.0 from Microsoft to programatically create your Word document. Follow this link for more information: http://msdn.microsoft.com/en-us/library/office/bb448854.aspx You'll need to let us know how you want to initiate the creation of the Word document so we can recommend where to start from a Sharepoint point of view.


2

You can achieve your goal using Office XML SDK to generating document programmatically. here is a link to download : http://www.microsoft.com/en-us/download/details.aspx?id=5124


2

Finally figured this out and the answer is not directly related to the install of Office Web Apps or the cache list issues as I first thought. Word docs were actually not being opened because a setting in Central Admin needed to be changed. By default, the setting Central Administration->Application Management->Manage Web Applications->General ...


2

Yes and No. If a user can read a document they can download and edit it if they so desire. They just can't edit the document as it exists in your list. This would include the Read and Restricted Read permissions (http://technet.microsoft.com/en-us/library/cc721640(v=office.14).aspx). You can, through Information Rights Management ...


2

This bug was fixed in the October 2013 CU: http://support.microsoft.com/kb/2825665


2

i am assuming you have SharePoint 2013, You need the Office web Apps installed and configure in order to open the word/office documents in Browser. Once installed, office documents will be opened in web apps by default - you can change it by activating site collection feature called "Open Documents in Client Applications by Default". After this setup, users ...


2

OK, upgrading my OWApps to the latest December CU seems to have fixed my problems with IE11. I also noticed a substantial boost in the speed of loading documents into the browser. The install is super easy(even more if you have snapshots to fallback onto): Instructions(don't download that CU, get the newer one below): ...


2

Looks like you dont have the Office Web App installed. In order to enable the functionality you must have a separate farm. On this second farm you will need Office Web Apps working properly. These requirements are important to us for a few reasons. The first is the extra server that is required will most likely drive the cost. The second is that Office ...



Only top voted, non community-wiki answers of a minimum length are eligible