I need to have all the documents in Sharepoint opens in client applications. I set the appropriate setting in the admin page, but it doesn't work for all users. Also I tried to set this in library settings, result was similar.
I think the reason may be on a client side, but I haven't found it. All users with this trouble have IE7 and MS Office 2003.
Does anybody know, how i could handle this?
I would think that the server is checking if the user has Office installed locally. This is achieved by trying to activate an object from the ActiveX control installed by Office locally. You can find this DLL under c:\program files\microsoft office\office12[14]\OWSSUPP.dll. If this dll fails to load, for instance, missing or not registered probably, SharePoint assumes that no local client software is installed. You can register the DLL or run repair on the Office installation, that should fix the problem
Related
I want to create an Office Add-In with some HTML + JavaScript for sell in Office Store. And this add-in no need using any server side facilities.
But if I understood https://dev.office.com/getting-started/addins the source files of Add-in must hosted on some Web server.
So main question: can I somehow pack all sources and all resources of Add-in to the output DLL file and push to Office Store only the Manifest and DLL files without any web servers?
I need this for allow users from Office Store, install this Add-in to his Office and let work with it even offline (without internet connection).
Also such configuration a little complicate for reverse Add-in, if someone decide steal my sources and create duplicate of Add-in.
No, it is not possible because office add-in have to be located somewhere. When the user "installs" a web based office addin, in reality he just subscribes to a server where the addin is hosted. Microsoft doesn't host the dlls, (i.e they don't provide a server to run your dll), they just establish a link between the final user and your server via the office store and provide an API to ease interaction.
If you want to build an add-in that can be completely offline, you should look VSTO addins, XLA addin , XLL addins or COM addins. However none of these addins can be published on the office store.
It has been possible to use appcache to make offline webapp add-ins for office 2013 (https://code.msdn.microsoft.com/office/Apps-for-Office-Enable-bdcb7a2f).
Its unclear whether this works with newer versions of Office.
This is definitely not possible via the Office Store.
I am using VS 2015 to create a console application that has a reference to Microsoft.Office.Interop.Excel. When I deploy it on a server (Windows Server 2012) I get the following error:
Retrieving the COM class factory for component with CLSID {0004567-3456-
0000-C002-000434000046} failed due to the following error: 80040154
I read some old postings that suggest I must have Office 2010 installed on the server. However, this is not possible. Is there any way to embed Excel assemblies in my application?
Or is there any different approach to resolve this issue? What I need to do is just extract an Excel file sheet names as a list....
Please remember that you need to have the host application installed on the target machine. When and where do you run the console application on the server?
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution. Read more about that in the Considerations for server-side Automation of Office article.
You may consider using the Open XML SDK if you deal with open XML documents only. See Welcome to the Open XML SDK 2.5 for Office for more information. Or use any third-party components designed for the server-side execution.
I have created a vsto addin in VS2012. I have added an installation project to the solution using Installsheild LE. After installing the exe that I get, I get the expected item added to my add/remove programs. However when I open Word, I get prompted with a Microsoft Office Customization Installer prompt which says the publisher is unknown. I click OK to this and it adds my addin as expected, which all works fine but I also get a second item appear in my add/remove programs.
Can anyone tell me why I am getting the second item in add/remove programs and offer any advice about what I should do to avoid this?
You have to add "|vstolocal" to the addin registry value that points to your addin file. This tells ClickOnce to run it directly and not install it per-user.
You also want to digitally sign the addin using a certificate issued by someone in the users trusted root. This could be VeriSign or others. If you create your own certificate you have to use custom actions to install the root certificate in the certificate store and to register the publisher cert as a trusted publisher.
I've created about a dozen of these installers over the last 8 years and it's tricky at first but gets easier over time. Several of my customers are using InstallShield LE to get the prereqs installed but then I factor all the components out into a WiX merge module where I can use things like the Util extension to install certificates.
It looks like you use ClickOnce and MSI installers to deploy the add-in. You need to remove any of them. Both kind of installers are described in the following articles in MSDN:
Deploying an Office Solution by Using ClickOnce
Deploying an Office Solution by Using Windows Installer
Is that your dev machine and got Visual Studio in it? I have seen this happened with Windows 7 during development the addin is added in to add/remove programs. This has gone later when I updated my Windows 7 machine. Some updates from Microsoft has removed this later.
Sorry, my English is bad, but i will try to explain what i mean.
I made EventReceiver on Developer PC on VisualStudio 2012 and it's work on my developer's SharePoint2013 Server.
I made WSP packgage, deployed it to Client's SharePoint 2013 Server, activated feature and get an Error.
Could not load type 'Microsoft.SharePoint.Administration.SPDiagnosticsService' from assembly 'Microsoft.SharePoint, Version=15.900.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
How i understood it's SharePoint.Dll version is another, but i can't find this version and don't know where it's on clients server.
I have the same Error. I copied dll files and had the same Error. Installed Visual Studio on clinet Server and it didn't help. I think it's server configuration bad.
To load SPDiagnosticsService, you need to ensure that your solution is deployed to the Farm.
To do check the settings, view the project properties, make sure Sandboxed Solution is set to False
I have already enabled webclient service but i think I m missing something tht has to be done...
The client needs to run IE 32-bit and have a single recent Office 32-bit installed.
Mixed Office enviroments often seems to break the explorer view.
BTW should probably be asked on serveroverflow