We have a Custom Outlook Addin. Which is frequently giving
"Add-in error: This add-in may not load properly, but you can still try to start it."
After couple of retries it started working and it is happening on every first load when I click the add-in.
What could cause this issue ?
Our manifest file is fine and the site is also working fine in browsers.
Make sure add-in's pages reference the office.js library and include an Office.initialize handler.
Take a look at the Understanding the JavaScript API for Office section for more information.
Related
I've inherited care for a legacy Outlook add in, triggered by an issue reported by an end-user, stating that the add-in isn't activated anymore.
What I know
We have an old custom add-in:
Written in .NET 4 Client Profile
As a VSTO project
Written in VB.NET
It worked fine on Outlook 2010, the user's recently been updated to 2016.
Symptoms
After installation, loading Outlook takes much longer
You have to manually activate the add-in
If you do, the menu/ribbon is loaded correctly
On shutdown / restart of Outlook, the add in is inactivated again
It's config'd to be x86. I've tried switching that to x64, because I'm on a 64 bit OS, but then the addin just didn't load.
What I've looked into
I've googled a bit and found this link: CRM for Outlook Add-In keeps disabling
I think this quote describes what's going on:
Microsoft has some security measures in place to prevent slow add-ins
from running inside Outlook. The issue is however that in many cases
add-ins without fault are mistakenly marked as slow and disabled by
Outlook, and if this is not immediately corrected when it first
happens, Outlook may permanently disable them with no easy way to
re-enable them.
I've researched with the help of an infrastructure/network engineer colleague to see if we can toggle the add-in to always enable, but no luck.
I've investigated eventviewer logs, I found this:
Outlook loaded the following add-in(s):
...
...
Name: AteamAddin
Description: AteamAddin
ProgID: AteamAddin
GUID: {00000000-0000-0000-0000-000000000000}
Load Behavior: 3
HKLM: 0
Location: file:///C:/Development/Deployment/AteamAddin.vsto
Boot Time (Milliseconds): 328
Followed by an entry with only my add-in on activating in Outlook, but with:
Boot Time (Milliseconds): 172
That's much slower than the second slowest, which loads in 47 milliseconds, but honestly, even 328 milliseconds isn't even that bad for a custom addin.
A weird thing is the empty GUID:
GUID: {00000000-0000-0000-0000-000000000000}
But I don't know if it's important. I've tried adding a Guid attribute to my ThisAddIn class, but no effect.
Question
What can I do to have Outlook 2016 accept the custom add-in?
The load time looks good, I don't see anything strange there. Instead, I'd suggest making sure no exceptions are fired at runtime. 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.
Also, I'd recommend making sure all the required prerequisites were included to the add-in package.
The application needs two folders to move mails to, so it checks / creates it on startup of the add-in. It looks like Outlook 2016 is more restrictive in what is allowed. Checking these folders likely takes longer than Outlook allows, so the add-in is deactivated.
I moved the checking and creation of these folders to whenever a user opens any of the forms. That way it's way later in the process and that works without issue.
We have developed outlook Addins and hosted on Apache Server with SSL certicate installed with it. Some days back it was working absolutely fine on both web as well office outlook client, after windows update and client update it returns Empty blank screen?
Till the Outlook Client version 1808 all looks good in client. After the Update to outlook client 1902 Addin Stopped working on outlook client.
The error message in F12 Debugger is thrown is :
Everything was working fine before update,
Note that this addin is build on Angular version 5 frame work using routes.
Update: I was loading office.js locally from the project not from the CDN, Now when I changes the office.js path in index.html to the cdn link "https://appsforoffice.microsoft.com/lib/1/hosted/office.js" Addins started working back.
But I need something not from CDN because one of our customer has on-primises server and not the office365 .So the problem I found is the office.js loading the outlook-win32.02.js but saying permision denied if loaded from the project and not from the CDN link.
Hope to get some suggestions from the outlook web addin Team....
After lots of reasearch I decided to use CDN link "https://appsforoffice.microsoft.com/lib/1/hosted/Office.js", and every thing started work as like before,
Then I decided compare my office.js inside the library with the CDN link javascript then I came to know that office script library is updated and I m having an old package, after reseach I found the github project updated recently , the below link will directly takes to the updated libraby , one can download with your existing one,
"https://github.com/OfficeDev/office-js/tree/release/dist" .
Hope this works for all having this issue.
I would appreciate any help as I have exhausted every solution I found at this point.
The Load Behavior of an Outlook Add-In is listed as "Unloaded" under File > Options > Add-Ins > COM Add-ins. It will load and work as expected if I manually check the add in. However it automatically disables when Outlook is restarted. I cannot find a way to make this stick. The following is what I have tried based on Google searches:
The registry shows that all available LoadBehavior options are set to 3, which indicates that it should load automatically. For good measure I searched for every occurrence of "LoadBehavior" to see if I was missing anything, but they are all set to 3.
The "Resiliency" options in the registry called "CrashingAddinList" and "DisabledItems" are empty, indicating that this add-in is not being forced to disable. Again I searched for every occurrence of this in the registry and they look good.
I added a "DoNotDisableAddinList" entry into the resiliency in the registry and gave it a value of 1. This is supposed to load the add-in no matter what.
I uninstalled the add-in, cleared out any reference to it in the registry, rebooted, and reinstalled. The same issue continues.
If I set the user as an administrator on their desktop, the add-in is loaded automatically in Outlook and works as expected. This is the only time it works, however nobody else has this issue and they are not set as administrators on the desktop.
Any ideas?
Thanks
Ian
Looks like your add-in fires an exception at startup...
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.
Hard disabled add-ins are listed under the DisabledItems windows registry key.
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. See How to: Re-enable a VSTO Add-in that has been disabled for more information.
We have customized ribbon(js scripts) that loads properly in IE and firefox but in google chrome(which is a requirement to use it due to its high response time) it does not load the ribbon at the first instance. However, it loads after several page load refreshes(Ctrl + F5). If anyone come across this issue, provide your inputs. Appreciate your help. Thanks
SharePoint and IIS are always trying to cache resource, to ensure application performace. When you're doing SharePoint Development you've always to ensure that cache is cleared.
Especially when you're working with the SharePoint ribbon it's required to clear the cache before accessing the website after deployment.
When you're using CKS tools for deployment from VS2010 you have to ensure that files are copied to the SharePoint Root. Sometimes I get an exception when they try to overwrite JS files in the SharePoint root, because sharepoint has a handle on them.
When doing SharePoint development I always copy *.resx and *.js by hand.
The issue appears to be with the rendering of the search box control in Google Chrome. Try adding 'Visible="false"' to the 'SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" Version="4"' control on the master page. This corrects the rendering issue for us.
SharePoint is officially not built to work in Google Chrome
I just fixed my webkit (chrome and safari) browser issues such as scrolling and the ribbon loading with this nice script http://goo.gl/1OUlI. Ended up being a timing issue. Hope it helps you out. I see this is a bit old but no best answer.
I finally got my localhost to display the site locally. Everything seems to be working on that end. My next step is to actually be able to step into the code from the VB6 IDE when the web site uses a function from the ActiveX.dll
UPDATE:
I updated the code and removed the issue I was having compiling the code.
Now when I try to debug the site won't open. It just hangs. I'm wondering are there any tutorials that I can read so figure out how to properly get this application setup for debugging?
UPDATE #2
Just to clarify, I got the web site (which references the ActiveX .dlls) locally on IIS 7.5. My hope is that when I open the site (on localhost) I can step through the .dll code at the same time.
That is really what I'm asking.
It's actually quite easy. First of all, do an iisreset. Then load up Visual Basic with your ActiveX DLL. Place your breakpoint, then Run your project.
Then hit your page containing a call to the ActiveX DLL and it should stop on a breakpoint you just set.