I have Classic ASP web site hosted on IIS 6.0 (It's a production server). It stops serving pages intermittently say for every 1 week or 10 days. after IISRESET again it works fine.
Verified IIS web server logs and there were no request hits found from the logs.
Verfieid HTTPError logs. Nothing found abnormal.
We already configured Application pooling to improve the performance for the website and recycling the worker process every 24 hrs.But, didn't help us much.
Could you please advise me in resolving the issue and what is causing this issue.
Related
I am experiencing next issue:
I have an AspNetCore website that is hosted on Windows Server 2012 IIS 2019.
I am running automated tests(Selenium, Chrome webdriver) for this website from any another server or PC and sometimes(not every time) after about 4 minutes i am getting Connection Timeout Error.
I am getting this error through Chrome Webdriver, Chrome, but website is accessible through any another PC/Server or even IE on the same server.
This continues for 5 to 15 minutes and after it is back again, i can access the website, i can run the tests.
Looks like something is blocking IP/Web browser from IIS.
I am running tests in parallel(4 threads).
I am running the same kind of tests for another website(which is not Core, just regular .Net Framework) and never had such issue with it.
I've checked DNS resolution - everything is fine, am getting the same error even with it hardcoded in hosts
I've disabled server firewall at all - did not work
There is no additional Antivirus protection except Windows Defender
There is no AVG set up on the server
I've tried different Servers, PCs and Chrome versions - still the same error happens from time to time.
Windows Event Log has nothing that can be linked to this issue.
Any help is extremely appreciated.
We have been using servicestack version 3.8.5.0 for a few years.
We noticed an occasional error where one of the web services returns 404. This service is part of an assembly where the other webs services all work.
This service has not been modified for a number of years and if we restart IIS the service works as expected.
Any ideas where to look on what might have caused the 'registration' to fail?
Edit:
Just found that this issue happens consistently on rebooting the server. So if I restarted IIS a number of times and I do not see the issue. However on rebooting our server, the issue appeared.
I'm having a problem with my IIS 7.5. problem that maybe I have caused yesterday after playing with application pools.
The problem is that website become very slow and the only way to fix it is to recycle the application pool.
When i try to access HTML file it's working fast but when i access classic ASP file it takes long time to load "Waiting for"
When i recycle the pool the problem solved for few seconds or minutes and my question is how do i debug it ? how do i know what cause the application pool to stuck ?
you always have the possibility to debug classic asp applications.
set the debug properties in your iis for your web application like so:
server-side Debugging active: true
then you can use the "stop" keyword in your classic asp files to set a "breakpoint". a popup will be raised to ask you how you want to debug your asp file (e.g.visual Studio)
I am trying to turn the logs on for IIS 6, because I want to know if my workers are recycling too fast due to an error. Our application keeps getting a reset connection when running a ton of queries from our app.
How do I get more info on logs and stuff?
Chris - I'm working on a similar problem as I'm writing some code to recycle app pools in both IIS6 and IIS7+. Just came across this article. Hope it helps.
How to Configure Application Pool Recycle Event Logging in IIS 6.0
This command, from that article, worked like a charm:
c:\cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs set w3svc/AppPools/LogEventOnRecycle 255
I hosted my asp.net mvc3 application on amazon ec2 cloud using windows server 2008 R2. The first time page loading is very slow. I decided to enable auto start on IIS 7.5.
I followed Scott's post.
http://weblogs.asp.net/scottgu/archive/2009/09/15/auto-start-asp-net-applications-vs-2010-and-net-4-0-series.aspx
I only have one web application hosted on this server, and this application got its own app pool, not shared with anything else.
this is all I did, add startMode="AlwaysRunning".
here's hte problem. I see performance gets a little bit better, but still about 4-5 seconds.
Is there way to verify if my auto-start setting acutally works?
If you have access to IIS Manager on the box, you can examine "Worker Processes" for the site. Otherwise, look for a process named w3wp.exe. If you only have one site, it should be the only process.
Try stopping the application and confirming the worker process has stopped. Now start the application without issuing a request. If the process is there, auto-start is working.
EDIT: Slides 11 and 12 from http://www.slideshare.net/brianritchie1/iis-alwayson-services may be helpful.