we configured outlook 2016 with Dynamics 365 with help of Dynamics 365 for Outlook add ins. The contacts are Syncing fine but every time when I open the outlook 2016 in my machine, its asking us to add the Dynamics 365 for Outlook add ins to Enable. Please suggest us how the Add ins should stay connected or Enabled longer instead of adding the add Ins every time.
Thank you. Suggestions are appreciated.
Looks like the add-in was installed/registered twice. You need to remove the second instance from Outlook.
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 VSTO 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 VSTO Add-in is executing.
Soft disabling can occur when a Add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable a 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. Read more about that in the How to: Re-enable a VSTO Add-in That Has Been Disabled article.
Related
I have created a Outlook 2010/2016 addin (VSTO?) with VS2015. I deploy this addin using click-once.
The update settings in the addin are set to every time the customization (addin) runs.
I can install the addin with one click (so far so good) and it remains working if a stop and start Outlook. No issues.....
But when I make a change to my AddIn, publish it and restart Outlook again. The addin is not loaded anymore. It is just not enabled in Outlook. Even enabling it again will not work. I need to uninstall and reinstall the addin to get the newest version available.
I cannot figure out why it is not working as there are no error messages.
Any clue anyone?
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.
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'm coming back to an Outlook Add-In I wrote last year - the Add-In installs and runs just fine (apart from a code issue I'm trying fix) but when I uninstall it (because I must) and try to run the code in Debug mode it launches Outlook just fine, but then nothing else - a breakpoint in InternalStartup() never gets hit, nor does one in ThisAddIn_Startup().
The List of Add-ins does not show my Add-in when I'm trying to debug, but it doesn't throw any sort of error or window. Just... nothing happens. The list of disabled Add-ins doesn't list my Add-in either.
I was finally able to find the answer on Dan Crevier's Blog post: Debugging Outlook Add-ins Doesn't Work if You Have Disabled Add-ins:
[...] if you have any disabled Outlook add-ins, VS will not stop at any breakpoints in other add-ins. The fix is to reenable all add-ins.
This kinda hoses me because my Outlook has an Add-in disabled by a corporate policy, but maybe it will help someone else.
We have developed a custom outlook addin which has a log file for logging. For installation, we are using .msi installer created using installshield. Installation is successful and functionalities are good except logging. There is only one entry in the log file after installation, rest of the actions are not logging as expected. But the same is fine, if we install the addin using .exe installer created using 'publish' option in VisualStudio 2010. As .msi is the expected installer, any help in fixing this issue is appreciated.
Saravanan,
Make sure that you did all the steps described in the Deploying an Office Solution by Using Windows Installer article.
Is your add-in loaded by Outlook? Did you have a chance to check out the Disabled Items list?
The fact is that Outlook 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.
Also Outlook 2013 monitors add-in performance metrics such as add-in startup, shutdown, folder switch, item open, and invoke frequency. Outlook records the elapsed time in milliseconds for each performance monitoring metric.
For example, the startup metric measures the time required by each connected add-in during Outlook startup. Outlook then computes the median startup time over 5 successive iterations. If the median startup time exceeds 1000 milliseconds (1 second), then Outlook disables the add-in and displays a notification to the user that an add-in has been disabled. The user has the option of always enabling the add-in, in which case Outlook will not disable the add-in even if the add-in exceeds the 1000 millisecond performance threshold.
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.