Losing IIS at Random Times (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

ScribeVision -> Losing IIS at Random Times (2/23/2005 8:58:24)

Pulling my hair out!

I'm currently deployed with my National Guard unit in Iraq. I created a web site that we used for years in one form or another for training purposes. It's run fine on W2K servers. Now that were over here and running on a brand new server with Server 2003, I'm encountering problems. The main problem is that 2-3 times a day, at varying times, the web site just kinda shuts down. There's no error message, just the screens blank out. The site logo image usually stays visible, but all the asp pages in frames just go white.

I then have to restart IIS and the site comes back up. Is there any performance setting on the server that might help? Bandwidth is not great here. Will increasing the connection timeout from 120 to 240 help or hurt?

At first I thought it might be some really slow pages that had a lot of DRW's embedded that were the culprit. But last night I released a new version of the site with the pages removed. It ran about 14 hrs with no problem, then came down.

Any ideas?



paulie -> RE: Losing IIS at Random Times (2/23/2005 9:17:12)

quote:

Bandwidth is not great here. Will increasing the connection timeout from 120 to 240 help or hurt?


That's the kind of thing I would try. If I said anything else it would only be a guess.

Can you access the Event Viewer on the server to rule out other issues like harware problems with the server itself?

quote:

last night I released a new version of the site with the pages removed. It ran about 14 hrs with no problem, then came down.


That would indicate to me that your DRWs are not the issue. I would try to rule out bad hardware (a flaky nic, bad RAM module, etc). You could watch the processes and memory utilization under Task Manager while browsing the site and doing some db queries on your DRW at the same time. You didn't mention how many users are hitting this thing, so that might give you an indication of whether your processor is getting hammered, your RAM is getting used up, or it's something else entirely.

I recently encountered a situation where the power supply on a server failed. The symptoms were a little different (it was rebooting itself at random intervals) but the point is the same: check the physical connections first, then look at software. You'd be amazed at how often it's something that simple.

Hope that helps, and let me just take a second to say THANK YOU for what you're doing over there.



ScribeVision -> RE: Losing IIS at Random Times (2/24/2005 1:28:03)

After increasing the connection timeout from 120 to 240 seconds ... came in to work this morning and learned that the error had occurred again overnight. IIS had to be restarted.

While back at my room I read through an IIS Admin book that said the default connection timeout is supposed to be 900 seconds. I tried upping it to 900 this morning to see if it makes any difference.

The server is a brand new Dell Power Edge 2850. The server administrator says there is nothing wrong with the hardware. He is running terminal services for remote desktop access.

He says it must be some bad asp code. However, I cannot get the error to occur on my development machine. Not sure how to pin point the problem.



ScribeVision -> RE: Losing IIS at Random Times (2/24/2005 7:41:31)

Increasing the connection timeout to 900 seconds apparently did not fix the problem. IIS crashed again after about 12 hours. In fact, these occurrences are generally about 10 - 12 hours apart.

Looking at the system category in the event log, the error event states "The World Wide Web Publishing Service terminated unexpectedly. It has done this 6 time(s)."



Shirley -> RE: Losing IIS at Random Times (2/24/2005 10:25:45)

Is there more than one site on the server?
Does it have is own app pool?
If you stop and start the site or the app pool rather than IIS does the site come back up?



ScribeVision -> RE: Losing IIS at Random Times (2/25/2005 0:40:01)

I checked with the server administrator and ...

There is only the one site on the server.

No app pools.

Stopping/restarting the site does not correct problem. Only restarting IIS.

HTML pages still function when this occurs. Only asp pages tank. No errors, just blank pages.

We looked at the web logs to see what was happening at the time of the crash. Most of the traffic at the time was for a flash Instant Messanger (from http://www.semtechinteractive.com/). We are considering whether that may have contributed to the problem.



ScribeVision -> RE: Losing IIS at Random Times (2/25/2005 7:22:54)

Dug through the Instant Messenger files and at the bottom of the readme.txt file it states:

"This webapp uses Application variables as oppoed to a database to hold user info. If you experience any problems, clear the application memory by going to "http://yourdomain/im/clear_all.asp"

So I created a 'favorites' to execute that page. I've run it roughly every couple of hours to clear the app variables to see if that stops the problem. So far so good. Will let you know further results later.

In the meantime, I searching for another Instant Messenger program that will run on a W2003 server in IIS.

Any suggestions!



paulie -> RE: Losing IIS at Random Times (2/25/2005 7:59:12)

This might work:

http://www.soft32.com/download_585.html

Sorry I can't be more helpful but I don't have occasion to use IM.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
7.910156E-02