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
Related
I have a problem regarding White Screen Of Death (WSOD) at my site.
I will try to explain what I have tried until now.
I know it is not a triviel error to debug, but maybe some of you have tried something similar.
Here is the setup: One Windows Server 2019 v1809 with one IIS: 10.0.17763.1.
Multiple websites with associated application pools.
It's a MVC solution, and we are using .net 4.7.2.
What I have tried:
Recycled application pools every night
Restarted the server every night
Issued a IISReset every night
Deleted temporary files in C:\Windows\Microsoft.NET\
Looked at the IIS logs
Looked at the application log, our own log
Looked at the Windows log
Searched the Internet for similar problems
Made sure there always were some traffic at the website
Made sure no errors were shown when pressing F12 in the browser, the site always returs code 200
The WSOD comes at varies times, and not all the sites are affected at the same time.
A manuel recycle of the website always helps.
My question is, have any of you encounted similar problems?
And how did you solve it?
If you need more information please ask, and I will try to provide it.
/Regards Søren
This kind of problem is very unusual in IIS, because there is almost no record and useful information in the log file.
You can try to use this plan to repair IIS.
Unregister all the versions of ASP.NET with command "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ua". and the framework 64 also versions. 3.0 and 3.5... etc
Delete ASPNET account from "Local Users and Group – Users".
reregister ASP.NET with IIS using "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –i". and framework64... net 3, 3.5 etc
Give permissions to the ASPNET account using "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ga machinename\ASPNET". for framework 32 and 64 and versions.
Reset IIS .
Recently we are facing "Service Unavailable" while opening our web reports url in internet explorer.
Restarting the IIS service resolves the issue but didn't found any logs/errors in event viewer to track what is causing IIS to fail.
Is there any other way to troubleshoot this?
Many thanks...
To actually help you out SO need more information but following is more common cause.
There is no enough memory for application to run when it try to start. If there are multiple application in your IIS then it cause such issue as other application took priority so memory consume by them.
Your application has some un-handle exception that cause your application to shutdown and sometime it cause worker process to stop.
If your application is .NET based ( This is not the case with you because after IIS restart it runs successfully ) then .NET Runtime Version conflict also create such problem.
We have SharePoint 2013 Service Pack1 May 2015 CU.
Of lately we see lots of POST requests to SharePoint for end point " _vti_bin/sharedaccess.asmx" .
These requests just wait in IIS pipeline for as long as 3+ hours and after.
Once IIS can't take more requests, SharePoint Throttles and no one can access anything.
Any idea why this web service is hanging? What can be done to fix this?
turns out this was a problem with Distributed Cache. The App Fabric service on the WFE stopped. Upon restarting the service and doing an issreset , everything seems ok.
NOTE:
In case App fabrci keeps stopping you might have to remove the cache host and add it again
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.
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.