UPDATE!!
Moved over a few websites that use Access to a brand new more powerful W2K3
server from a W2K server. These websites had functioned flawlessly for a
couple of years.
After the move, after periods of time (ranging from 10 minutes to 2 hours)
the server would stop serving ASP pages and would only serve static pages
until it was restarted.
I was getting the following error in the Application log:
"ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy
for the following reason: 'ASP unhealthy because 100% of executing requests
are hung and 36% of the request queue is full.'."
I paid for a support incident with Microsoft and after a few days of them
looking at the dumps they sent me a BETA version of a fix to the MS Jet.
The file is a beta fixed msjtes40.dll. The server has been functioning fine
now for about 24 hours.
"Pat [MSFT]" <patfilot DeleteThis @online.microsoft.com> wrote in message
news:%23b00OyxLEHA.1192@TK2MSFTNGP11.phx.gbl...
> Next time the problem happens, run IISState (www.iisfaq.com/iisstate)
> against the w3wp.exe process. It will dump a log that you can post and we
> can see what the issue is.
>
> Pat
>
> "John Cesta" <lists DeleteThis @lookwww.com> wrote in message
> news:200443016295.006375@poolfact...
>
>
> Try using the unicode access driver.
>
> John Cesta
>
> ---------------------------------
> The CPU Checker - Maximize Server Uptime
> LogFileManager - The only IIS Logfile Management Tool
> DomainReportIt PRO - Helps Convert IIS Installs
<font color=purple> > <a style='text-decoration: underline;' href="http://www.serverautomationtools.com</font" target="_blank">http://www.serverautomationtools.com</font</a>>
>
>
> On Fri, 30 Apr 2004 14:49:44 -0400, Ruben N wrote:
> > I moved over our websites to a new DELL Poweredge Server
> > running W2K3 standard edition and every hour or so ASP
> > pages stop working. The event viewer has the following
> > message:
> >
> > "ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported
> > itself as unhealthy for the following reason: 'ASP
> > unhealthy because 100% of executing requests are hung and
> > 34% of the request queue is full.'."
> >
> > I did a few searches and found there might be a problem
> > with the JET and IIS 6.
> >
> > We run a few sites that use Access databases, but not
> > with that high of traffic.
> >
> > They worked fine on Windows 2000 on a machine with a lot
> > less power and half the memory.
> >
> > Any ideas?
>
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: ASP.DLL Hangs