We have encountered a very curious issue where Outlook web add-ins randomly disappear from the ribbon. The issue seems to be only reproducible in Office365 MSO 16.0.10827.20118 (32 bit).
Related
I've developed a VSTO Add-In for MS Word. When I'm installing the Add-In into client's machines, every time I've to enable the Add-In Manually.
I've signed my add-in using a Certificate.
Can anybody help me why the add-in is getting disabled again and again.
Any help is highly appreciated.
Right after installing the add-in I'd suggest checking the LoadBehavior key value (before MS Word is started). By default, this entry is set to 3, which specifies that the VSTO Add-in is loaded at startup. Read more about such keys in the Registry entries for VSTO Add-ins article.
Microsoft Office applications can disable VSTO Add-ins that behave unexpectedly. If an application does not load your VSTO Add-in, the application might have hard disabled or soft disabled your VSTO Add-in.
Hard disabling can occur when a VSTO 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 VSTO Add-in is executing.
Soft disabling can occur when a VSTO Add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable a VSTO Add-in if it throws an unhandled exception while the Startup event handler is executing.
When you re-enable a soft-disabled VSTO Add-in, the application immediately attempts to load the VSTO Add-in. If the problem that initially caused the application to soft disable the VSTO Add-in has not been fixed, the application will soft disable the VSTO Add-in again. Read more about that in the How to: Re-enable a VSTO Add-in that has been disabled article.
I figured out the issue.
MS Office disables the Add-ins automatically, if it crashes. In my case the exception was thrown from the starting point i.e.
ThisAddIn_Startup
Office was not able to instantiate the the add-in, because there was no document open and was causing this exception.
This was the exception: This command is not available because no document is open.
To fix this error, I wrote following lines which opens a blank MS Word Document, if any document is not open:
if (Application.Documents.Count == 0)
this.Application.Documents.Add();
I have a published/certified MS Outlook Add-In on the Microsoft Store:
https://appsource.microsoft.com/en-us/product/office/WA104381281?src=office&tab=Overview
It shows Product Supported: OfficeProductForAndroid and OfficeProductForIOS. However, the Add-In only appears on IOS devices (as well as Desktop, OWA, etc).
How can I get support to know why the Add-in does not appear on Android devices?
PS - it does work by adding our XML staging manifest directly. And other public store Add-Ins are working.
In mobile(iOS and Android) add-in need to be whitelisted to show on Add-in Management Screen if it is not installed manually or not installed at all.
Whitelisting of Add-in is done by our team on request. I think franConnect has been whitelisted. Soon it will start coming on Addin Management Screen.
I developed an add-in with a MessageComposeCommandSurface extension point.
It appears, is activated and works on outlook.office.com but with windows desktop client, Outlook 2016 (version 16.0.8625.2121), the button appears in compose mode but stays gray and it is not clickable.
I tested the command-demo-addin mentioned in Microsoft Docs and published on Github with the same result. Similarly, as shown on screenshot, it is impossible to click and launch the add-in which seems unactivated.
The COMPOSE buttons are disabled in the following instances:
1) The Item is in a public folder.
2) The Item is in Junk, Outbox (not drafts), or Sync Issues.
3) The item is "secure". DRM, or S-MIME encrypted. (older versions of Outlook also do not support S-MIME signed)
4) Outlook is offline.
In the situation where Read Mode add-ins are working, but Compose does NOT it is almost always #3. Usually the user will have on the option to always DRM / S-MIME their outgoing messages.
Update with image of security settings:
If Com Add-ins load a Custom Form this can also affect add-ins:
Checking Com Add-ins:
Note that outlook actually ships with some add-ins and a lot of com-addins work fine with Web Add-ins. It's only when Com Add-ins override the default new mail form (or other forms) that they can interfere with Web Add-ins.
Some COM add-ins will NOT use Custom Form, but will access the parent folder (item.Parent) and there is currently a bug that disable's Web Add-ins when a COM Add-in or VBA script does this.
File->Options->Add-Ins-> "Go" (next to manage add-ins)
If you have an antivirus instaled like avast, try to disable the addin of this and then try to open your compose mail window.
I have a word com add-in that has been working fine previously but due to some reasons, I reinstalled my Windows-OS, MS-office and add-in software right after that It is showing in inactive add-in category. but the load behavior is "load at startup".
unable to find the exact reason. please help me and tell me how to debug this and know the root cause of this
There are multiple reasons why add-ins are disabled by host applications...
First of all, I'd recommend checking all the required prerequsites on the target machine. Make sure that al of them were installed correctly before running the host application with your add-in registered.
Microsoft Office applications can disable VSTO Add-ins that behave unexpectedly. If an application does not load your VSTO Add-in, the application might have hard disabled or soft disabled your VSTO Add-in.
Hard disabling can occur when an VSTO 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 VSTO Add-in is executing.
Soft disabling can occur when a VSTO Add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable a VSTO Add-in if it throws an unhandled exception while the Startup event handler is executing.
When you re-enable a soft-disabled VSTO Add-in, the application immediately attempts to load the VSTO Add-in. If the problem that initially caused the application to soft disable the VSTO Add-in has not been fixed, the application will soft disable the VSTO Add-in again. Read more about that in the How to: Re-enable a VSTO Add-in That Has Been Disabled article.
You may also find the following articles helpful:
Troubleshooting COM Add-In load failures
Troubleshooting Run Time Errors in Office Solutions
I have developed an Excel Addin using VSTO 4.0.
There is a Custom taskpane that contains various controls to perform functions.
the Custom Taskpane works fine with office 2010 and is displayed on left.
but When i install the addin for office 2013 on Windows 8.1 it does not apear at all?
Below is the code snippet im using to display the taskpane;
var taskPaneProcessMapView = new TaskPanes.taskpaneProcessMap().GetInstance();
this.TaskPaneProcessMap = Globals.ThinkReliabilityAddIn.CustomTaskPanes.Add(taskPaneProcessMapView, "Process Map");
this.TaskPaneProcessMap.Visible = false;
this.TaskPaneProcessMap.Visible = false;
May be you need to set the Visible property to true?
Anyway, is your add-in enabled? Did you have a chance to check out the COM add-ins list in Excel? Is it listed in the Inactive add-ins list?
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.
When you re-enable a soft-disabled add-in, the application immediately attempts to load the add-in. If the problem that initially caused the application to soft disable the add-in has not been fixed, the application will soft disable the add-in again. See How to: Re-enable an Add-in That Has Been Disabled for more information.