I have two applications hosted at IIS 7.5 on Windows 2008 Server R2. One application is hosting at .net framework 4.0 and other on framework 2.0. Both have Integrated and Classic values for Managed Pipeline Mode property of Application Pool.
Issue is, at client machine only one application is login at a time, if I login to 1st application 2nd gone to session timeout and vice verse.
Please help and suggest which configuration is require at IIS end.
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.
After a company forced Windows 10 update today, the Application Pool required by a local web application keeps stopping/crashing displaying the message
Service Unavailable
HTTP Error 503. The service is unavailable.
I have checked the the below similar posts and followed the solutions provided with no luck.
#1 - https://stackoverflow.com/questions/47338226/iis-10-0-apppool-crashing-causing-503-error
For hosting .Net Core applications in IIS, .Net CLR Version of
application pool should be No Managed Code as shown in below
screenshot.
#2 - https://stackoverflow.com/questions/50244861/iis-10-app-pool-keeps-stopping-due-to-aspnetcore-dll-failed-to-load
Go to the drive your IIS is installed on, eg. C:\inetpub\temp\appPools\
Delete the directory (or virtual directory) with the same name as your app pool.
Recycle/Start your app pool again.
I have also followed the Microsoft instructions. Made sure to first follow the steps in "Turn Windows features on/off) and then installing the ASP.NET Core hosting bundle as instructed.
#3 - https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.1&tabs=aspnetcore2x
I'm not having any luck.
Here's my setup App Pool
Here's my setup Site
I've done everything I know. Does anyone have this same experience and can share a solution?
As always, a big thank you to the experts out there!
UPDATE:
I created a new AppPool with Identity "ApplicationPoolIdentity" setting. The page will run however I need to connect to a SQL Server instance with my own credentials because we use Windows authentication on most of the pages. When I create a new AppPool with my credentials it will not stay running.
When I Add new web site in IIS and open in browser it shows me the list of directory instead of web page in windows server 2008 R2. I am unable to run application (MVC Asp.net Application). Please help me where I am wrong Or guide me with the steps that I need to perform.
We have a WCF Service that we either have to host in a Windows Service or IIS. This is a commercial application that will be installed on consumer pc's running for example Win7 Home.
In my opinion IIS on Win7 is by Microsoft only meant for development and/or testing. Activating IIS on a consumer pc shouldn't be a real option.
So my question is: Is it a real option to host a WCF service in IIS in a commercial application on a simple consumer pc?
I have InstallShield (IS) Basic MSI project, that creates Application Pool and installs web application on IIS under existing website.
On IIS default website is stopped and different website named WebApps using port 80 is running it uses AppPool1. Under WebApps we have several applications that use different App Pool for themselves for example AppPool2, AppPool3. When I install new application under WebApps and set its App Pool to newly created AppPool4 some applications App Pool changes to ASP.NET v4.0 AppPool1.
You can see my Application Pool and Web App settings below from IS.
Does anyone know why this could be happening?
Issue was with Web App .NET Framework version was set to v4.0 and this would cause all the Web Apps under Website to be set to use .NET Framework v4.0