Forum Moderators: open

Message Too Old, No Replies

IIS Falling Over Itself

Solutions to a bad IIS app

         

cossick

8:40 am on Aug 28, 2006 (gmt 0)

10+ Year Member



Hello everybody,

My first post and it happens to be a doozy of a question! I'm running a dedicated webserver here with a copy of IIS 6.0 on Windows Server 2003.

It's a beast of a server 2GB of RAM, 2xIntel Xeon 3.06GHz processors, so it's not short of being able to deal with requests. It's running off a dedicated 2MB upload DIA/DIS line supplied by my ISP, so bandwidth isn't an issue either.

Though the problem is, IIS keeps failing at random times. Sometimes it'll be up for days on end, and sometimes every 20 minutes it fails. I'm using bog standard ASP and there's no CGI or .NET technologies involved on this.

I've applied latest patches and I run anti-virus software during the night. The screensaver has been disabled and there's no power settings which would affect the computer.

But like I say, IIS just drops out whenever it feels like it. There's no log of it in the Application logs and now I'm at my wits end.

Can anyone help me?

(EDIT) I've had a look at the application logs in more detail and there was one flag for w3wp.exe which I know is an IIS process.

Reporting queued error: faulting application w3wp.exe, version 6.0.3790.1830, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x000224b2.

For more information, see Help and Support Center at [go.microsoft.com...]

Bluesplinter

12:04 pm on Aug 28, 2006 (gmt 0)

10+ Year Member



Check the event viewer. There will be a little yellow (warning) or red (error) icon next to any events you need to check closely, and the description will say something like this:
A process serving application pool 'MadeUpName' terminated unexpectedly. The process id was '3152'. The process exit code was '0xc0000005'.

However, if you look above the description, you'll see an EventID, such as 1009, for instance, and the Source, W3SVC in this example, and those two items usually will help you track down what's taking place. Most of the time a Google search for either the EventID or the actual text of the description (or both) will bring up folks who've had the same problem, and how they solved it.

At least, that's how I've always been able to track down those warnings/errors. Sorry I couldn't help more specifically.

vite_rts

12:19 pm on Aug 28, 2006 (gmt 0)

10+ Year Member



if you're running sharepoint services , look at this ms article

[support.microsoft.com...]

oxbaker

7:22 pm on Aug 28, 2006 (gmt 0)

10+ Year Member



try reinstalling asp.net, sounds like a .dll is missing from your libraries, running aspnet_regiis should fix it.

mcm

cossick

8:10 am on Aug 29, 2006 (gmt 0)

10+ Year Member



Why would reinstalling ASP.NET solve stability issues when I'm not using any .NET technologies in the first place?

Easy_Coder

10:18 am on Aug 29, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



It sounds like your having trouble with --> ntdll.dll and not really IIS. This is a low level windows object. Sysinternals has a good writeup on this object I'll sticky you the url.

Have you tried running process monitor to see what's going on right up to the point where iis ganks?

aspdaddy

7:22 pm on Aug 29, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



>faulting application w3wp.exe

sounds like a badly configured IIS. Try setting the pool recycling a little lower. Also if you have several sites on the same box, run each process its its own pool to identify the problem site.

It looks like you are using un-allocated memory and getting an exception, this is quite normal in Windows you just need to manage it by configuring pools.