I have create Excel 2003 addin and installer according with manual http://blogs.msdn.com/b/cristib/archive/2010/11/01/deploying-a-vsto-word-2007-add-in-to-all-users-visual-studio-2008-sp1.aspx
At that time I try to install addin on another machine. Installation pass success, but addin does not work. Excel does not shows any errors, but plugin is not loaded correctly and does not work.
Does it exists any way to diagnose problems with addin?
Duplicate question.
How to troubleshoot a VSTO addin that does not load?
More info can be found here: http://msdn.microsoft.com/en-us/library/ms269003.aspx
Related
I am using visual studio 2013 with Team foundation Server add-in. Opening up a TFS task/bug item, there is a outlook icon button, which allow me to open up outlook new email with the TFS item title.
my visual studio runs in administrator mode.
I have two office versions installed (office 2013 and office 2016.)
Each time when I switch office versions, I will do a repair for the office version. and most time I was using office 2013 and everything works fine including open outlook through TFS add-on.
today, suddenly I couldn't open outlook through the TFS add-on, the error is
Unable to cast COM object of type 'Microsoft.Office.Interop.Outlook.ApplicationClass' to interface type 'Microsoft.Office.Interop.Outlook._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063001-0000-0000-C000-000000000046}' failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)).
I repaired office 2013, but didn't work.
some one knows other possibilities of the issue?
thanks.
The root issue is that the Version reference for the TypeLib created by the Outlook installation is pointing to a incorrect value.
The root issue is that their is a problem with the Outlook
installation Common Object Model (COM) interface where the version
referencefor the TypeLib entry set by the Outlook installation is
pointing to a incorrect value/version or that version does not point
to a correct location. If you continue to have issues
then you may beed to reinstall Microsoft Outlook. Repairing the
Outlook installation does not fix this issue so a reinstall is
suggested.
Just following the steps mentioned in below article to fix that: https://www.fieldstonsoftware.com/support/support_gsyncit_8002801D.shtml
Just verify that with Regedit.exe, check below keys:
HKEY_CLASSES_ROOT\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib
HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}
Verify if the type library (GUID should be {00062FFF-0000-0000-C000-000000000046}) is indeed properly registered, using the correct type library version number.
Andy's post is right. you can follow the instructions to find out the issue.
Office 2016 registry key is 9.6, on my machine, even I uninstalled office 2016, the registry key 9.6 still exists at
Computer\HKEY_CLASSES_ROOT\TypeLib{00062FFF-0000-0000-C000-000000000046}
After deleting it, TFS office add-on works fine now. I think the add-on is trying to use the latest version and it causes the issue.
I have tried to create a package for a VSTO addin using windows installer in Visual Studio 2013 but having no success. By that I mean I can create a exe and msi by using the Visual Studio Installer Setup Wizard and selecting everything as default, which seems to all run ok when installed but I don't get my addin appear anywhere in Word (I have looked in File-Options-Addins- com addins/dissabled addins).
I have spent quite a lot of time googling to find some instructions but with no success. Can anyone please help me by either writting some instuctions on here or pointing me to a link where someone has already done it?
Can I point out, I know how to create a package using Installsheild instead but I was having a few issues with that, so wanted to try this instead. So please don't suggest that as an approach, or wix.
You don't mention which version of Word you're using. Traditionally, this has been a nightmare - but I would guess that the most horrible things has been fixed in more recent versions of Office. In particular I'm thinking of the "KB908002" which had to be applied during setup (don't know if that is the case still).
One thing that may be forgotten is that you are required to install the "Microsoft Primary Interop Assemblies" (PIA) on the target machine, and that you have to apply the correct PIA depending on which version of Office you have on the target machine.
Anyway, this article http://blogs.msdn.com/b/vsod/archive/2008/04/22/troubleshooting-com-add-in-load-failures.aspx will give you quite a few ideas. Specifically, enabling the Fusion logging which has help me way back.
Good luck!
I have c# outlook addin created in visual studio 2013.
It has windows forms also.
I am getting mad on generating msi file, any easier solution/steps for me, please ?
Mainly tell me, after completing the process, where do I find the final MSI file (like bin/release folder) ?
I installed this - https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d
as well as installshield limited edition installer.
I was able to build it and ran the installation file(.exe) from disks folder and it is installing but not showing anything in the outlook.
Take a look at the Deploying an Office Solution section in MSDN. It describes two possible options for deploying your Office solution in depth:
Deploying an Office Solution by Using Windows Installer
Deploying an Office Solution by Using ClickOnce
It is up to you which way is to choose.
I was able to build it and ran the installation file(.exe) from disks folder and it is installing but not showing anything in the outlook.
There are multiple reasons why you don't see your add-in in Office applications.
First of all, make sure that you did all the steps described in the previously mentioned articles. Then I'd suggest checking the required windows registry keys for COM add-ins, see Registry Entries for Application-Level Add-Ins for more information.
Microsoft Office applications can disable add-ins that behave unexpectedly. If an application does not load your add-in, the application might have hard disabled or soft disabled your add-in.
Hard disabling can occur when an add-in causes the application to close unexpectedly. It might also occur on your development computer if you stop the debugger while the Startup event handler in your add-in is executing.
Soft disabling can occur when an add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable an add-in if it throws an unhandled exception while the Startup event handler is executing.
You can read more about that in the How to: Re-enable an Add-in That Has Been Disabled article in MSDN.
Finally, you may also check out the Trust Center settings in Outlook. The Macro Security settings can be applied to add-ins as well. May be it is required to sign the add-in with a digial signature and etc.
I have a VSTO 2010 Office 2007 Outlook Add-In deployed from Click-Once. It works on my dev machine and on a standard user machine and fails on another. On the first time it was installed but the add-in didn't appear in Outlook. Then I removed that Add-In in the control panel and deleted the "outcmd.dat" file. When I'm trying to install a new plugin, it shows an error message:
"Microsoft.VisualStudio.Tools.Applications.Deployment.AddInAlreadyInstalledException: The customization cannot be installed because another version is currently installed and cannot be upgraded from this location. To install this version of the customization, first use Add or Remove Programs to uninstall this program: WG plugin. Then install the new customization from the following location: file:///C:/WG25.10.2012/WG plugin-php.vsto
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.VerifySolutionCodebaseIsUnchanged(Uri uri, String subscriptionId, Boolean previouslyInstalled)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn() "
Does anyone have any idea what might be causing this?
try this link , you have a command to run in this page,just run it the problem will be fixed. command: "rundll32 dfshim CleanOnlineAppCache"
or try this link
How do I completely uninstall a ClickOnce application from my computer?
I had previously installed the VS11 beta, and had some issues with my Visual Studio 2010 instance, which you can see here how they were resolved: Excel AddIn Click Once deployment issue.
Now I have a code base which compiles/builds a vsto, which installs fine and runs fine in Excel 2010. However, when I remove the installed version from Excel, and try to run it directly through Visual Studio 2010, the AddIn does not get loaded into Excel when running in debug configuration mode, in release configuration mode it works fine. Any ideas on why this might be occurring? I've tried re-enabling it through Com AddIns, and a few other things with no luck.
I've found the issue which was not letting me run my project in 'Debug' configuration mode, though it worked in 'Release' mode. At some point, the AddIn, got hard-disabled (not sure if that's the term to use). At that point, trying to re-enable from within Excel doesn't do anything. Within the registry, there is a folder where disabled AddIns are flagged. I deleted all of the keys from this folder except for "(Default)" and now my AddIn works when launching from Visual Studio 2010 in 'Debug' mode.
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Excel\Resiliency\DisabledItems
When you run through Visual Studio 2010 does it hits the breakpoint in the addin_startup event.
If not try to debug this way
Hope this helps you
You can reenable a hard-disabled Add-In with Excel
http://msdn.microsoft.com/en-us/library/ms268871(v=vs.80).aspx
I had the same problem with a Word VSTO, but there was no Resiliency\DisabledItems folder in my registry, so I think it was never hard disabled (as in #mservidio's solution). What worked for me was to edit the Manifest path in HKEY_USERS\<user key>\Software\Microsoft\Office\Word\Addins\<Add-In name> to reflect the 'Debug' path rather than the 'Release' path.
To find the right folder it might be easiest just searching for the Add-In name and checking that any Manifest keys refer to the Debug path.
I had the same problem in Excel.
The following worked for me:
Go to the following key....
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\AddInLoadTimes
see if your plug-in is listed. if so, delete it.
now run your app from Visual studio again.
This worked for me, hope it can help someone else.
I also had the same problem, what I didn't understand was :
Why I re-install Office 2016, I don't change my code neither VS setting but I get a cant load error message ?
After many many hours, repairing Office and VS and getting the same error message, I observed that the Addin was starting well in Release config, I started checking the difference between the both config in my code.
I found that debug config was targeting to x86 proc bug release to any cpu
So Office x64 didn't load x86 dlls (in my case)