I created an Outlook add-in using Office developer tools for Visual Studio 2015.
The project is correctly generated, and I deployed it to an azure app service.
When I try to add the add the manifest to my Office 365 dev subscription, I get the following error : "Something went wrong, and we couldn't install your add-in. Please try again later"
This manifest is the exact manifest generated by VS, the only modification was to replace the place holder for the Web URL by the one of the Azure app service.
Has anyone encountered this issue before ?
Thanks.
Can you upload or copy/paste the manifest you are trying?
If you are installing via URL. This is also a common error that is given when OWA cannot download the Manifest from the URL. There could be permissions/something wrong with the URL.
Otherwise, you may also get more detailed information on why the install is failing if you install from the Manage App page instead of the In Client Store Page. (Detailed errors on the In Client Store Page will be added soon)
Related
I have developed ASP.NET project in Visual Studio 2019. When I try to run the project with IIS Express, the webpage says “This site can't be reached” and "The connection was reset".
In taskbar I can see that IIS Express is working and I'm able to debug and step though my code till the very end successfully so I know the service is executing fine without any errors.
Site can`t be reached
I created a new project, just to ensure that there weren't any errors within my config or build files. When I run the new project, I get the same result.
I tried with other browsers as well, but still the same error.
I repaired the Visual Studio using the Visual Studio Installer, and reset everything to default, and had no success with that.
I tried to delete hidden vs. folder and had no success.
Any advice on how to resolve this would be greatly appreciated.
Thanks!
I fixed the issue by deleting Kaspersky Antivirus.
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 need to add a web reference in Visual Studio 2012 (because service reference generates a blank reference CS and I have given up after hours of googling).
When I go to add the web reference (add service reference → advanced → add web reference) and enter the WSDL URL I get the IE Notification Bar in the dialog with the message:
To help protect your security, your web browser has blocked this site from downloading files to your computer. The option to "Download file" does not work.
I've changed IE security settings to minimum and added the domain to the list of trusted sites but did not have any effect. I also uninstalled IE10 completely and still get the notification bar. I am using Windows 8.
Anyone shed any light on this or had any success adding a web reference in VS 2012?
If you can download the WSDL with your browser, download it and save it to a file. You can then reference it from Visual Studio by pointing it to that file. Or you can use svcutil.exe or wsdl.exe to generate a proxy from the commandline.
I'm stumped. There are several threads out there that reference a similar problem, but not the same one. I'm trying to get a simple WCF service up and running in Azure, but my problem is happening before I even deploy. I'm following this article:
https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-create-deploy/
Which says to create your project, build the "Hello World" service interface and class, and then start your project locally. I get a 403 error when I try to start my project.
The only step I'm not following exactly is that I don't have a "Start Without Debugging" option (I'm using Visual Studio Express Web Developer), so I just push "Start Debugging."
Why would I get a 403 error on my own machine? I am running Visual Studio as Administrator.
On the WebRole project right click on your .svc (Service1.svc) and choose "Set As Start Page" And then run the project. Make sure to do this on the WebRole project not the Azure Cloude Project.
Is the Azure project the default project or is the WCF Web Role? If it's the role itself, that may be your issue - it's trying to access the root of virtual directory containing the web service versus running the cloud app in the local emulator. If you browse to http://127.0.0.1:81/Service1.svc in a new browser window do you still get the 403?
It seems VS has lost the its project settings. Bring up "Properties" page on the web service in VS. Go to the "Debug" tab. Under Servers/Virtual Path: my configuration was set to just "/". Put the name of your server back in there "/Service1.svc" and it should work from the debugger now. This fixed the problem for me.
The problem went away when I upgraded to VS 2010 Pro. I never fixed it on Express, but after upgrading the problem was gone ... I had the "Start without Debugging" option in the Pro edition, so I suspect that the problem may have been specific to Express.
I've just got to the bottom of this, and couldn't find the problem documented anywhere, so thought I would post the question (and answer) for future reference:
I've just installed CruiseControl.NET on a (virtual) Windows Server 2003 and I can't access the Dashboard. CruiseControl (ccnet.exe) runs fine, and IIS6 is up and running, and the the CruiseControl installation installed the Dashboard app under Default Web Sites as "ccnet". It's pointing to the dashboard folder, and the dashboard files are visible in IIIS Manager, but when I try to access http://localhost/ccnet I get a 404: Page Not Found error. I get this whether I use IE or Chrome, or try to Browse the site from IIS Manager.
What's wrong?
ASP.NET was Prohibited, and needed to be Allowed - in IIS Manager, click on Web Service Extensions under the server, select ASP.NET and click Allow.