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.
Related
I wrote an Outlook plug-in to help me manage the spam I receive through my mail server.
It was written for Outlook 2016 using Visual Studio 2019. My old laptop took a nosedive and crashed, refusing to power on afterward.
On the new laptop, I've upgraded to Visual Studio 2022 and Outlook 2021.
Now I'm getting a weird compiler error.
Error CS0115 'AddIn.CreateRibbonExtensibilityObject()': no suitable method found to override
Here's the referenced code:
protected override IRibbonExtensibility CreateRibbonExtensibilityObject()
{
return new ContextMenus();
}
The Microsoft.VisualStudio.Tools.Applications.Runtime is version 10.0.0.0.
I'm wondering if there's something I forgot to install, perhaps?
To understand whether you have got everything required for Office add-ins development with VS2022 you can try creating a new add-in project. If it does work correctly then you have got everything set up on your side. Now you can compare the newly created add-in project with a migrated one to find what is wrong with your migrated solution.
Anyway, you may find similar threads over the internet:
Microsoft add-in code build error --ThisAddIn.RequestComAddInAutomationService()': no suitable method found to override.
Error in once functioning C# project - no suitable method found to override
We've created an Outlook add-in which integrates our custom CRM with Outlook. A command button is added to messages in read and compose mode. A function file is called on the button click.
The add-in manifest passes validation and installs properly on all machines. However on Outlook 2016 desktop (only) we are seeing an error on some machines. The exact error message says: “We’re sorry, we couldn’t access [NCS Outlook Add-in]. Make sure you have a network connection. If the problem continues, please try again later.” ([NCS Outlook Add-In] is the name of our add-in.)
Note that this message appears IMMEDIATELY after clicking the add-in command button. It does not first say “[NCS Outlook Add-in] is working on your request” like it add-ins do when an error has occurred.
We have tried Outlook logging and haven't found anything useful in the logs. We've checked settings and disabled other add-ins. We have also tested across machines with user accounts. The same user will have the error on one machine and not the other. In short, it seems that the error is machine specific and not profile related.
Version of Office 365 installed: 1705 (Build 8201.2209).
We experienced this exact behavior in Outlook 2016, the solution was to enable protected mode for the restricted and internet zones.
The easiest way to change this is in IE.
In Internet Explorer, click the Tools button, and then click Internet Options.
Click the Security tab, and then select the Restricted Sites Zone.
Select the Enable Protected Mode check box, and then click OK.
Restart Internet Explorer.
Here is a little more information:
https://support.microsoft.com/en-us/help/2761180/apps-for-office-don-t-start-if-you-disable-protected-mode-for-the-rest
Try this:
1) Close Outlook
2) Rename the folder C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook
to C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook.OLD
(Where %USERNAME% is current User Name.)
3) Start Outlook, Setup User Profile
4) Add/Test Add-In.
If that works, then something broken on old Outlook profile. But if same problem: Exit Outlook, delete the Outlook folder and rename Outlook.OLD back to Outlook.
I ran into this exact same problem after uninstalling Visual Studio 2015 on my development machine. (I had been using Visual Studio 2017 for Outlook add-in development.)
The problem went away as soon as I reinstalled Visual Studio 2017. The Outlook 2016 installation had nothing to do with the problem, I never changed Outlook or its profile at all.
This would indicate that the problem is somehow related to the SDK tooling on the machine...perhaps something to do with the .Net framework?
If I ran into this problem on a customer machine I would try reinstalling or repairing the .Net framework, or perhaps reinstalling Outlook (assuming it contains some add-in tooling that is broken.)
Just passing this on in case it helps anyone else.
I've been developing an Outlook Add-in, been working and installing fine.
Then I tried to installed a really old version of the same add-in (trying to verify some old behaviour, the old plugin was for Outlook 2010), and it somehow messed up the install/uninstall process. Ever since then Office Outlook 2016/365 is not able to register/view the Add-in anymore.
I've tried the following:
Uninstall and Reinstall Outlook
Removes all the registry entries related to the Add-in (I literally search with the Add-in's keyword and removed hundreds of left over entries which I wasn't even aware of)
Deleted c:\Users\user\AppData\Local\Microsoft\Office
Deleted c:\Users\user\AppData\Roaming\Microsoft\Office
Deleted c:\Users\user\AppData\Roaming\MyAddIn
Ran CCleaner
Ran RegDllView to scan all the registered DLLs, and it says C:\WINDOWS\system32\mscoree.dll is "missing"? But is there...
Tried to uninstall and reinstall Add-in Express before recompile the whole project.
If i try to manually add the Add-in in Microsoft Outlook, Options > Add-ins > Manage > Add, if i point it to MyAddIn.dll it would say that it is not a valid COM Add-in (but nothing was changed in the project on how the dll was built). If i point it to adxloader.dll and hit OK, it won't complaint but nothing shows under Add-in either.
My next option is to completely reinstall Windows, this is driving me insane. Can anyone who have experienced this insanity give me some pointers?
Operating System: Windows 10
Office: Office 365 Outlook
This is a very strange situation that I am in; scratching my head for answers.
I have developed an outlook addin that works perfectly on my dev machine and on about 90 % of the clients machines.
The load behavior of the addin is 3.
On 10% of the users, outlook starts up without loading the addin despite the load behaviour being 3. The user can manually make the addin active by going to the addin manager on outlook but after a restart this addin reverts back to being inactive bbut load behavior never changes from 3.
I used Install Shield LE to package this addin. I don't even know where to debug anymore, I tried changing different load behaviour values but still the same outcome. The addin just won't load on startup with this set of users.
The company uses ZenWorks to automatically install the addin on all the PCs from the MSI i generate using install shield.
One weird thing is, If i go to the installation directory of the addin and install the addin using the .vsto deployment file, it works and gets loaded on outlook (but thats makes it two addins installed).
I also checked the Resiliency section on the registry and the addin isn't there.
I have faced this issue. To solve this, you need to manually delete the registry entries from the following path.
Open registry editor and go to HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\<Your add-in> and change the LoadBehavior to 3.
If the above registry entry is not found, then look for HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\Outlook\Addins\<Your add-in> and change the LoadBehavior to 3.
Go to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Resiliency – remove the REG_BINARY keys found in DisabledItems and CrashingAddinList
where 15.0 is for outlook 2013.
If you are using 2010 outlook, replace 15.0 by 14.0 and for Outlook 2016 replace 15.0 by 16.0
Hope this helps.
It's very annoying problem, I tried to search everywhere for a solution, but nothing!
Anyway, I have installed the CRM 2011 SDK addin for visual studio 2010 (ultimate) and I am trying to create a XAML Workflow Activity
I have added the CRM Workflow items to the toolbox using these instructions: Add Microsoft Dynamics CRM Workflow Activities to the Toolbox
When I try and drop a Workflow on the design surface it say in red box text "Could not generate view for Workflow"
Hovering over the text reveals a System.IOException that says "Cannot locate resource workflowdesigner.xaml"
I read on another post to dump all the SDK bin folder files into the PublicAssemblies of the VS, but that didn't work for me! Tried that on a Windows 8, Windows Server 2008... Still nothing!!!
How do I fix that?
That is a known bug. I contacted Microsoft and they confirmed it. I was told to look for a fix in UR 17. UR 16 was released in January so it should be out "soon".
Update Rollup history: http://support.microsoft.com/kb/2555051/en-us
(I realize this is a late reply, but it was a recent issue for me.)