Recently I've had a problem where all my projects using ASP.Net Core with Swagger give a 403 error when trying to access them through a browser locally. This happened overnight and seems to effect all Swagger projetcs when run using IIS Express.
I have tried:
Different browsers (Firefox/Chrome/Edge)
Different operating systems
(Windows 10 / 7)
Different versions of Visual studio (2017 and 2017
preview)
Different machines
Going back to an old branch I know was
working
All give the same result. The issue doesn't seem to stop the API from working and when it is deployed to an Azure app service the Swagger UI appears with no issues. Any idea what the problem could be here?
Related
Good Day everyone
We are currently testing our first Blazor Server application that is deployed on our Staging Server (Windows Server 2016 with IIS 8), we have noticed that, when the application is accessed by multiple users and doing some testing process, the application becomes slow, or sometimes when accessing the site again, the browser still loads the application but without rendering the design, we check it using the dev tools in google chrome, and on the network tab, it says "pending" under the time column.
We tried to ping the application, and it returns without too much latency, I don't know if this application side or on the server or the network, we deploy the project similar to our ASP.NET Core MVC projects, we are all testing the applications on our homes, because of the global pandemic.
Is there a different setup for Blazor Server when deploying to IIS?
I hope someone can help us with this.
Thanks, everyone, and regards.
Edit
We found the suspect, It's the Visual Studio JIT Debugger, yes we install VS2019 on our Staging Server, it's weird that we haven't encounter this from our other web application, is it because the project is in Blazor Server? when we check the server the JIT is running, and then the app is working again, I think when the application encounters an error, this shows up on the server side, and when it reach 3 JIT on the process, it will not continue to load the application.
I search for this and the answers is to disable the JIT Debugger, either in VS or in the register, is disabling this is the best solution??
Thanks again everyone.
I have an Asp.Net Core 3.2 Blazor Webassembly application that has been published to a server running Windows Server 2016 with IIS 10.
After publishing to the server I can browse the login page to the site, However, when I attempt to login which calls a service and signs in with Entity Framework Core 3.1.5.
However when I attempt to call a linq query on the DbContext it seems to fail (This is deduced from log files).
Interestingly, if I remote into the server whilst running a login I get a JIT popup with the following error;
In the Windows System Log can see the following error;
A process serving application pool 'myapppool(domain)(4.0)(pool)' suffered a fatal communication error with the Windows Process Activation Service. The process id was '10188'. The data field contains the error number.
It seems to sometime crashes the apppool as well so if I then refresh the page i get 502 error on the site?
Below is a screen shot of the application pool advanced settings;
The server is running Windows 2016 with Plesk Obsidian installed on it (I'm not sure if this can interfere in any way??)
Does anyone know whats going on here please?
I don’t know what’s going on since I can not reproduce your issue. Here is a workaround.
Please ensure that IIS Application pool’s Advanced Settings has set ”Enable 32-Bit Application” to true.
Check below link for troubleshooting the issue.
How to diagnose IIS fatal communication error problem
we have developed an application using ASP.NET/C# MVC 4.0, SQL SERVER 2012 DB, Entity Framework, WCF Service.
application website is hosted on IIS 10 and the operating system used is Windows Server 2016 and this is standalone WEB server dedicated for our project.
application WCF web service is hosted using Windows Service and this is standalone APP server dedicated for our project.
application database is hosted on SQL Farm and this is a common database server, where other projects databases (more than 60) are also hosted.
application is already running absolutely fine in PROD environment from couple of years.
but suddenly from couple of months, we started facing as intermittent issue and i.e. application slow response
There are no errors, but the response time is too long, and sometimes it doesn't respond either, the browser keeps waiting for the web server.
customer has complained that his web application gets slow sometimes.
It happens at random times, the system just gets slow then after few hours (2-3) it gets back on track with normal response times.
this slowness issue is affecting only to one specific MVC View, whereas other MVC views are rendering correctly at the same time when slowness issue occurs.
error handling is already in place in the .net code, but nothing gets logged in error log file.
also DBA has confirmed that there are no issues on the SQL Farm and none of the other projects apart from us has reported slowness issue whose database is also hosted on the SQL Farm.
when tried to reproduce the same issue on UAT with the same PROD database copy & same user, was not able to reproduce it.
UAT environment is exactly similar for WEB & APP server.
only in case of UAT database server, we do not have SQL Farm here. we have standalone database server dedicated for our project.
here tried doing some R&D and verified few things, but still unable to resolve the issue.
so could you please guide me here that what should i do/verify to resolve this issue.
thank you in advance for your inputs.
I'm trying to setup a prototype with an mvc 6 project and application insights. When selecting to monitor an mvc 6 website in IIS 7, it says it is monitoring but no server statistics are being sent to Azure. When I monitor any other sites on that server it works correctly. So my question is, does application insights support .Net 5 and MVC 6 running in IIS?
In the website I have installed Application Insights using the snippet of javascript provided by Microsoft Application Insights. This is working correctly and sending data to Azure.
The website is on a local Windows 2012 server. I have installed the Application Insights Status Monitor on the server and I have it pointed to the mvc 6 website. This part is not working. When I point the Server Tool to a site on the local server running a .Net 4.5 website it does submit the data correctly to Azure.
I did not add the AI part via nuget package because I am not submitting any custom alerts to Applications Insight. Right now I am just looking to get the server statistics. IE Memory, Processor usage, etc.
Asp.net vnext is not currently supported. But there are plans to support it in the near future.
There is ongoing work visible on it in github: https://github.com/Microsoft/ApplicationInsights-aspnetv5
Okay, here goes: Our developers are running VS 2012 on Win 7 boxes. I am running TFS 11 on my Win Server 2008 R2 box with IIS 7.5. It runs fine. My gating unit tests fail however. While I am not completely certain what the issue is, I seem to be unable to get the default Web Site or our application that I have installed under it to run. The default web site won't even return a test.htm file choosing instead to return a 503. To date I have tried...
Setting up WCF with access to the test cert installed on the box
Changing the app pool and giving it access to the dir in question
Burning a small offering to the gods of oblique IIS issues
Various other things I can't recall at the moment
I would take Sean Walsh's advice at the end of this post: http://forums.iis.net/t/1183179.aspx/2/10 but I need SQL reporting services for my TFS to work properly.
Thoughts? Thanks in advance.
Sean Walsh had it nailed. This turned out to be due to the fact that SQL server reporting services were using the port at the behest of TFS. I was able to step around this problem by setting up a dedicated build box on a VM.