I have created a web application with ASP.Net and i hosted it on IIS. In this application there are some forms having log running queries which take more than 30 seconds to run and as i run any query of them all the other forms get slow sometimes it shows like computer is hanged.
Related
I'm created an asp.net core web api application.
I want to get current server cpu/ram usage as percent.
This application is will not scale never and this anytime will running on the one Windows server.
How can i get the server cpu/ram usage as percent?
I'm developing an ASP.NET MVC web application with IIS 8.5 and table adapters connected to SQL Server 2014.
Every now and then my SQL queries (event the most simpliest) suddenly slow down from 15ms to 36 seconds. If I run the same query via the SQL Server Managament Studio it's as slow as with the application. But as soon as I close the browser and restart the application everything works again ultra-fast (application and SQL Server Management Studio) for some time (until it suddenly slows down again).
Any hint what could cause this kind of thing?
Occasionally when I reboot one of the servers at a client site the Web Apps running in IIS do not automatically start backup when the server is done rebooting. The IIS service starts up just fine, its set to Auto Start and there are no errors in the event log. Just none of the Web Apps are running, I have to click each one and click start. This only happens occasionally, as they usually start but its completely baffling.
Any thoughts? Its a mix of Classic ASP and ASP.NET applications. There are a total of 4 application pools running between around 8 web applications.
I have seen this happen when apps rely on a resource that is not yet available to the server, such as a network share.
Some people combat this problem by writing a Windows Service who's job is to check for such conditions and start the application.
I have a problem running an MVC application in my production server. My default website is running ASP.NET 2.0 and it's using the DefaultAppPool.
After reading the article Running multiple versions of the Framework in ASP.NET I followed what Scott Forsyth's instruction and created a new application pool. I also created a new website in IIS and created a Virtual Directory for my application. So my new website uses port 81 and the Virtual Directory for my MVC app uses the new application pool.
To me it seems that everything should be separate now. The new MVC app should spin up a new w3wp.exe process that uses ASP.NET 4.0. The other applications running under the default website should create a process that uses ASP.NET 2.0.
Unfortunately this is not the case. I keep on getting the 1062 error:
It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.
I tried restarting my server a number of times. This error doesn't always happen. For example, last week everything worked well for 1 day, then this morning (Monday) I got this error. All of my apps in the Default Website stop working and I see other errors in Event Viewer like EventID: 1309 with error:
Exception information:
Exception type: WebException
Exception message: The operation has timed out
Can anybody help with this? Thanks.
It's possible to run more that one aplication pool in the same WebApplication on IIS 7 or 7.5? I have one web application on asp.net 4.0 that use EF 4.0 and a large set of Entities. Then the First query Its to slow and when the application pool fails, the users need to login again, but the pool was restarted and the first query Its too slow, this cause any can't login for a time (about the time that the old pool is finished and the new pool It's ready).
If I can use multiple applications pools for the same site, on the same port 8080 for example, thats solve my problem. The only way I found was to create a server farm. However, if I understand, each servers would be a virtual or real machine?
You can have multiple applications and associated pools running under one site directory root. In IIS 7 manager, simply right-click on the folder in question and select "Create Application" in the resulting dialog set the new application pool and the physical path. This will mean that you have to segregate your code into separate projects/modules (web applications or web application projects in vs) but they will all share the same site.