My Office Add-In (Word, Excel) is only loaded successfully when started the office desktop client (2013, 2016) as Administrator.
When not started as Admin we get this error:
"ADD-IN ERROR: This Add-In could not be loaded... Close and Click on Reload."
We face this error in the newest versions of Office 2013 and Office 2016.
What we have tried:
Enabled Protected Mode in Internet Explorer
Deleted Wef directory of Office
Updated Office versions
Any ideas why the Add-In could not be started?
The problem is starting as Administrator is no more possible since Visual Studio 16.6.2 - only IIS Express not as Administrator is supported.
Previously we used IIS which only worked when started as Administrator.
In the solution properties of a newly created Office AddIn there are now multiple startup projects:
I tried this in my solution - also switched to IIS Express and used localhost web adress.
We also had to use Action = Start to avoid this error:
This is not a solution - just a work around - starting as Administrator and using IIS does not work anymore :(
see my VS Developer Community post
Related
We have a Office add-in component that is built in VB 6. We register it by running command as OfficeConnector.exe /regserver with admin rights that works most of the time for any MS office versions. In one of the machine with Office 2013 installation, Add-in registration fails with error as "Component not correctly registered". We tried repairing the office installation, still the same error happens. Any suggestion on this ? Thanks in advance.
Everything was working fine. I have windows8.1, VS 2010, VS 2013 installed on the same machine.Ms office 2013 was installed without infopath and InfoPath 2010 was installed already with MS Sharepoint 2010 and it was working fine with code behind. Suddenly mistakingly someone updated to MS Office 2016 and now I have tried installing Ms Infopath 2010 again it installs properly but when i click on code on MS Infopath 2010. it gives error "InfoPath cannot start Microsoft Visual Studio Tools for Applications. InfoPath has encountered the Error. The operation failed.". I have installed msxml6.msi. I have checked everything installed VSTA too. tried every solution but my code behind is not opening VSTA. I installed msxml6.msi too. but one thing I noticed if I run VSTA from my command it opens up but its not opening with infopath. I have lost hope. What could be the reason. Please help. I ll be grateful.
After several failed attempts, I installed visual studio tools for office system 3.0 and luckily it worked. :)
I have written a small officeJS addin for excel which run perfectly on desktop excel client. Also office online gives an option of installing the addin from the ribbon menu. I want to do the same for microsoft sharepoint server 2016 which can be maintained centrally by an administrator. The addins options is available in office online, but not available through sharepoint, PFA image.
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 have created an Web Add-ins project for Word using Visual Studio.
I have Office 2016 Professional Plus installed on my system.
When I try to launch the application using F5. Everything works, but when I click on the button in the ribbon menu to show the task pane. Task pane is shown but with following error message.
ADD-IN ERROR
This add-in could not be started. Close this dialog to ignore the
problem or click "Restart" to try again.
UPDATE:
I have tried to create a new project/solution and without modifying anything. It is giving the same error on running or hitting F5.
UPDATE 2:
I have verified that I have Latest version of Office developer tools installed.
I shared the same application that I created with another colleague here and it did not run on his machine either, but when I tried to create a File->New Project on another machine (it worked there) and tried to run that on my system and it didn't work.
I was facing this issue because of a bad environment setup. After I uninstalled and then reinstalled Visual Studio, everything started working again, as suggested in #JuanBalmori's comment.
I'm having some issues deploying a Visio addin.
Running the VSTO file works on my computer, but whenever I try and move it to any other user's computer it throws an error on deployment.
I thought it might be a setting I'd set in the project properties so I created an entirely new plugin project and set it to display a message box on startup.
The error I'm getting is:
An error occured during customization install.
The expected element "addIn" was not found in the XML.
This is caused by an issue with Clickonce.
I found a workaround by installing the addin using MSI.
This Guide was a lot of help.
Taken from the section about registry settings for the msi installation:
It is important to note the ‘|vstolocal’ value appended to the end of the Manifest value. This informs the VSTO runtime that it is locally installed and to not invoke the ClickOnce installer.
I'm having the same issue with our Word, Excel, Outlook and PowerPoint add-in. The installation of the msi runs perfect.
When starting Word for example, the Add-in itself gets 'installed' and then I receive the error.
I have added |vstolocal to the registry, which is located in the HKCU tree.
The projects is a Visual Studio 2010 project, build on TFS 2008. The installation on an Office 2010 goes well, the error only occurs when Office 2007 is on the machine.
Anything else I'm overseeing?
The solution to my experience with this issue was the one given by Joeri on the 8th July - install Visual Studio 2010 Tools for Office Runtime on the target machine.
This is an issue with the version of Visio your add-in targets versus what is installed on the client machine. AddIn is an element that is new with the 2007 versions of Office. More than likely the client is running Visio 2003.
Some times the Visual Studio 2010 Tools for Office Runtime is installed on the machine but the vsto file fails to find it. In this case try if you can manually execute the installation command line.See example below (replace X with your own drive letter, path, and file name):
"c:\Program Files\Common Files\Microsoft Shared\VSTO\10.0\VSTOInstaller.exe" /Install file:///X:/XXX/XXX.vsto