I have developed an ASP.NET Web Service in Visual Studio 2013. The target framework is .NET 4.5.
I am attempting to deploy the Web Service in IIS 10 running on a Windows Server 2016. I have registered.NET 4.5 on the IIS using the following command - dism /online /enable-feature /featurename:IIS-ASPNET45.
I have also enabled 32-bit applications in the application pool.
I have also ensured that .NET extensibility for .NET 4.6 and ASP.NET 4.6 are enabled, in the application development features.
I am getting the following error when trying to browse the web service - HTTP Error 403.14 - Forbidden The Web Server is Configured to Not List the Contents of this Directory.
The funny thing is that when I deploy the web service to IIS 8, it runs with no problem at all.
I am at my wits' end. Could someone please tell me where I am going wrong with the IIS 10?
Related
I need to host my Asp.NET Core gRPC Service on IIS so that I can make it publicly available for others in my team so can you please provide a proper document or steps for hosting my gRPC service on IIS.
Hosting .net core application in IIS is not yet supported. For more details please go through link
This document states that ASP.NET Core gRPC can be hosted on IIS, but it carries extra requirements.
IIS requires .NET 5 and Windows 10 Build 20300.1000 or later.
HTTP.sys requires .NET 5 and Windows 10 Build 19529 or later.
So please check if it meets the requirements before trying to publish it on IIS:
Host ASP.NET Core on Windows with IIS.
I have my ASP.NET Core application running on IIS and the Application Pool is currently set to .NET CLR Version 4.0. My application loads up correctly and the my view is displayed. However, when I try to run a POST I get the following error:
502 - Web server received an invalid response while acting as a gateway or proxy server.
I realize that most documentation says to set the .NET CLR Version to No Managed Code for .NET Core, but is it possible to run ASP.NET Core against v4.0? I am targeting .NET Framework 4.5.2 in my .NET Core app.
I am trying to set up Web Deploy on Windows Server 2008 R2, I have installed Web Deploy and Web Management Service.
I know that I'm connecting to the server because I see the following in the log.
2015-06-19 12:13:59 100.72.108.11 HEAD /msdeploy.axd site=IAmAFish 8172 - 86.1.148.102 - 404 7 0 93
However, I'm receiving the standard error about checking that Web Deploy is running.
I suspect permissions are the issue and I'm currently trying to find 'IIS Manager Permssions' in IIS manager, after selecting the site. It's not there. How do I add this feature to IIS manager so that I can manage permissions?
It turns out that the version of Web Deploy installed by Web Platform Installer does not include the full suite of tools and should not be used for this.
Instead, download Web Deploy from:
http://www.iis.net/download/webdeploy
Be sure to restart IIS Manager to see the new icons.
Running a webrole that is using NServiceBus 4 hangs when running in the local emulator. I have duplicated this on several windows 8 machines. Works fine on Windows 7. It appears that the only way to get it to run is to change the azure project (web settings) to "Use IIS Web Server." I am running Windows 8 and Visual Studio 2012 and Azure 2.0 SDK.
Here is how you can duplicate the problem by working with the PubSub sample from here:
http://particular.net/articles/windows-azure-transport
Build the project and run it to verify that it works out of the box
Now change the Web settings by right clicking on the azure project and Selecting the "Use IIS Express" option on the web tab.
Run the project now
The web role will simply hang. Any ideas? Running under IIS Express is preferred for many reasons.
there seem to be some known issues with IISExpress and Azure. Could you have a look at these pages and see if they help
Can't get azure web role to run locally using the emulator
Workaround for IIS Express Crashing When Running Windows Azure Cloud Service Web Role
IIS 7.5 is installed on two servers (both Windows Server 2008 R2) with Web Deploy 2.0 installed (to enable me to Publish from Visual Studio 2010.) Publishing straight from VS requires the Web Management Service be running on the server. I've been publishing to the first server for months, no problem. The second server has just been spun up (not by me) but as far as I can tell has all the same versions of components (OS, IIS, Web Deploy). However, on the second server the Web Management Service isn't installed. There's a key difference:
Web Deploy 2.0 options available on the first server:
Web Deploy 2.0 options available on the second server:
Why is there a difference between the two?
(Follow-up: I tried the Web Deploy 3.0 installer and encountered the exact same dialog as the second server, above, except that it said "3.0" instead of "2.0".)
Verify the proper IIS roles are installed on your new server. In the Server Manager console, under Web Server (IIS), verify the following roles are installed:
Management Tools
IIS Management Console
IIS Management Scripts and Tools
Management Service
Then try re-running your Web Deploy installer. I think you'll find you get the options you desire.