Classic ASP Site tying up application pool

Microsoft Windows server 2003
September 3, 2009 at 20:56:16
Specs: Windows Server 2003
Hey guys,

The situation:

I run a classic ASP site on windows server
2003. We use an MS Access DB for our
product listings and MS SQL Server 2005 for
our orders and cart database.

About two weeks ago our site just started
going down. The timing was weird, in that I had
been away and hadn't made any changes in
about 4 days. Since it has started, it generally
goes down once a day. When it goes down,
there is an error in the system log saying
'process serving has timed

The windows server log shows that an array of
different pages have been loaded before the
error... and oddly, even after we've been sent
the 'site down' message (
monitoring) there are still page loads
happening in the log successfully, even though
I personally can't load the site without
recycling the application pool.

I've gone through code I had uploaded at the
time, increased physical memory on the
server, changed some settings, everything I
can think of. Nothing seems to help.

Can anyone suggest some good/free stress
test software or anything along those lines? I
installed Process Monitor on the server one
night and let it run overnight, hoping to catch
the offending process in the act... instead it
ate up all the memory on the server and
crashed all of our sites.

So now, I'm hoping there is someone/company
out there that can come to our rescue.


Scott Carmichael

See More: Classic ASP Site tying up application pool

Report •

September 5, 2009 at 05:34:12
I'd assume it's problems with your Access DB, but who can say? Have you tried MS' stress test tools?

Report •
Related Solutions

Ask Question