ASP/SQL Server app not responding

We have a domain which we "hang" several applications off in separate
folders. In other words:
www.mydomain.com/app1
www.mydomain.com/app2
www.mydomain.com/app3
Each application functions differently. App1 may access a Microsoft Access
database through regular ASP pages while app2 accesses a MS SQL database
through ASP.NET, and app3 access a MS SQL Server database through regular
ASP. The MS SQL Server is running on a different server within the same
LAN. Our web server is running Windows Server 2003, and the server hosting
the database is running Windows Server 2000.
What is happening is after a few hours of running, the application that
accesses MS SQL Server through ASP (App3) starts slowing down, and will
eventually stop responding all-together. The progress bar in the browser
will just move very slowly, and never get there. I've let it run for
between 5 and 10 minutes with no response. We reboot the web server (which
I really hate to do, but don't have a choice), and the application starts
responding again.
When App3 stops responding, I can still go to app1, and it works just fine,
no problem. App2 (accessing SQL Server through ASP.NET) will not respond
either. However, when App 3 stops responding, I can't access anything in
that folder at all, not even a standard .asp page that contains no code at
all, let alone a SQL Server connection. So, I'm not sure if it's got
anything to do with SQL Server or not. The only thing that makes me suspect
that is that the ASP.NET which access SQL Server also has stopped
responding.
Does anyone know any reason the application would do this? It just started
doing this recently. We have had some changes, including having to rebuild
our domain controller, which is also the machine that hosts our SQL Server
database. We also recently bought a new router, and we also installed all
of the latest patches and updates on our Windows 2003 server (this is the
most recent change). I tend to suspect the updates as causing the problems,
because we ran fine all last week, which is after our router upgrade, and
the server rebuild. But I desperately need to figure this out. This
application is a national application, so could have hundreds of users
ticked off at us for this problem.
Any help or hints that anyone can give us is really appreciated.
Thanks,
Jesse
what is the memory usage of your 3 applications?
have you setup different application pool?
restarting IIS should solve the issue. (iisreset instead-of a reboot)
look at different performance counters to understand what's appends. maybe
you don't close your database connections.
look at your SQL server side to verify how many connections are opened and
if there is no dead lock.
you can configure an application pool to restarts himself at a regular
basis. maybe this could solve your issue. only the app3 could restart every
3 hours for example.
"Jesse" <nospam@.fake.com> wrote in message
news:ehfYxmDqFHA.3084@.TK2MSFTNGP09.phx.gbl...
> We have a domain which we "hang" several applications off in separate
> folders. In other words:
> www.mydomain.com/app1
> www.mydomain.com/app2
> www.mydomain.com/app3
> Each application functions differently. App1 may access a Microsoft
> Access database through regular ASP pages while app2 accesses a MS SQL
> database through ASP.NET, and app3 access a MS SQL Server database through
> regular ASP. The MS SQL Server is running on a different server within
> the same LAN. Our web server is running Windows Server 2003, and the
> server hosting the database is running Windows Server 2000.
> What is happening is after a few hours of running, the application that
> accesses MS SQL Server through ASP (App3) starts slowing down, and will
> eventually stop responding all-together. The progress bar in the browser
> will just move very slowly, and never get there. I've let it run for
> between 5 and 10 minutes with no response. We reboot the web server
> (which I really hate to do, but don't have a choice), and the application
> starts responding again.
> When App3 stops responding, I can still go to app1, and it works just
> fine, no problem. App2 (accessing SQL Server through ASP.NET) will not
> respond either. However, when App 3 stops responding, I can't access
> anything in that folder at all, not even a standard .asp page that
> contains no code at all, let alone a SQL Server connection. So, I'm not
> sure if it's got anything to do with SQL Server or not. The only thing
> that makes me suspect that is that the ASP.NET which access SQL Server
> also has stopped responding.
> Does anyone know any reason the application would do this? It just
> started doing this recently. We have had some changes, including having
> to rebuild our domain controller, which is also the machine that hosts our
> SQL Server database. We also recently bought a new router, and we also
> installed all of the latest patches and updates on our Windows 2003 server
> (this is the most recent change). I tend to suspect the updates as
> causing the problems, because we ran fine all last week, which is after
> our router upgrade, and the server rebuild. But I desperately need to
> figure this out. This application is a national application, so could
> have hundreds of users ticked off at us for this problem.
> Any help or hints that anyone can give us is really appreciated.
> Thanks,
> Jesse
>
|||> what is the memory usage of your 3 applications?
I don't know how to track memory usage for individaul apps. How do I do
that?

> have you setup different application pool?
Yes, I have separate application pools for each application. Perhaps this
is what allows one app to continue functioning while one seems to freeze up.

> restarting IIS should solve the issue. (iisreset instead-of a reboot)
It doesn't. That was one of the first things I did. Actually, I stopped and
restarted the one web site. I didn't try stopping and restarting all of IIS.
Maybe I'll try that next time.

> look at different performance counters to understand what's appends. maybe
> you don't close your database connections.
This is one issue that I'm thinking may be causing the problem. I'm about to
go through all of my files from all of my applications and check for that
sort of problem. I kind of suspect that is the issue.

> look at your SQL server side to verify how many connections are opened and
> if there is no dead lock.
How do I do that?

> you can configure an application pool to restarts himself at a regular
> basis. maybe this could solve your issue. only the app3 could restart
> every 3 hours for example.
Good suggestion. How do I do that? Also, when it restarts, will it affect
anyone that is in the app at the time?
Thanks for all the good suggestions.
Jesse