Reputation: 5834
I have an issue trying to load and debug any kind of Outlook web add-in. I can reproduce with my own add-in (which is deployed to the Office store and used to work in debug mode perfectly!) as well as with the default add-in template in Visual Studio 2017. I create a default "OutlookWebAddin1" project, change nothing, hit F5 to deploy and run/debug, enter my credentials, and load the add-in in the Outlook client or browser (Chrome, IE and Edge) - all exhibit the error:
"Add-in Error: Something went wrong and we couldn't start this add-in.
Please try again later or contact your system administrator."
The F12 console in Chrome (to pick one of the three browsers I tested with), shows these errors:
GET https://localhost:44398/MessageRead.html?et=&_host_Info=
Outlook|Web|16.01|en-CA|11aa92ad-a510-ddb9-c441-529b1b374f16|
net::ERR_INSECURE_RESPONSE
GET https://localhost:44398/Images/icon64.png net::ERR_INSECURE_RESPONSE
Executing action: GetTaskStatusAction
GET https://outlook.office365.com/ows/outlookusersettings/api/v1/frepanel
/frepaneltaskstatus 401 (Unauthorized)
Here's a prettier look at the error:
https://www.screencast.com/t/elcbcUkdlkO
Upvotes: 0
Views: 1918
Reputation: 5834
The cause is apparently a problem with the localhost certificate. The fix is to use the Certificates Snap-In in MS Management Console and copy the localhost certificate from "Personal-> Certificates" to "Trusted Root Certification Authorities -> Certificates". How this problem occurred on two very different PCs with different versions of Visual Studio is a mystery, but this does work.
Upvotes: 1