We migrated our web sites from windows 2000 Server to Windows 2003 server
and we're having a frequent problem for many application pools, which result
in IIS hanging and not serving any more .asp page, while answering to static
files requests.
All the web sites hanging use MS Access and ADO via OLEDB connections.
The problem occurs frequently, about 5/6 times a day for the most accessed
websites.
The event viewer sometimes reports errors for the W3SVC application: when
this happens the application seems to recycle and continue working. When the
pool hangs, not event is written into the event viewer.
Watching into Microsoft forums we heard about the Jet bug, we tryed to
install the Jet Engine sp8, but that didn't solve the problem.
What can we do?

Many thanks,
Andrea Frigo

Re: IIS on Windows 2003 hang on ASP sites by Tom

Tom
Mon Apr 26 08:21:35 CDT 2004

"Andrea Frigo" <a.frigo@monforte.it> wrote in message
news:jG7jc.685$%x6.106@news.edisontel.com...
> We migrated our web sites from windows 2000 Server to Windows 2003 server
> and we're having a frequent problem for many application pools, which
result
> in IIS hanging and not serving any more .asp page, while answering to
static
> files requests.
> All the web sites hanging use MS Access and ADO via OLEDB connections.
> The problem occurs frequently, about 5/6 times a day for the most accessed
> websites.
> The event viewer sometimes reports errors for the W3SVC application: when
> this happens the application seems to recycle and continue working. When
the
> pool hangs, not event is written into the event viewer.
> Watching into Microsoft forums we heard about the Jet bug, we tryed to
> install the Jet Engine sp8, but that didn't solve the problem.
> What can we do?

Here is the most current info available from Microsoft on this issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;838306

--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserver2003/community/centers/iis/




Re: IIS on Windows 2003 hang on ASP sites by Charley

Charley
Mon Apr 26 16:38:34 CDT 2004


>-----Original Message-----
>"Andrea Frigo" <a.frigo@monforte.it> wrote in message
>news:jG7jc.685$%x6.106@news.edisontel.com...
>> We migrated our web sites from windows 2000 Server to
Windows 2003 server
>> and we're having a frequent problem for many
application pools, which
>result
>> in IIS hanging and not serving any more .asp page,
while answering to
>static
>> files requests.
>> All the web sites hanging use MS Access and ADO via
OLEDB connections.
>> The problem occurs frequently, about 5/6 times a day
for the most accessed
>> websites.
>> The event viewer sometimes reports errors for the
W3SVC application: when
>> this happens the application seems to recycle and
continue working. When
>the
>> pool hangs, not event is written into the event viewer.
>> Watching into Microsoft forums we heard about the Jet
bug, we tryed to
>> install the Jet Engine sp8, but that didn't solve the
problem.
>> What can we do?
>
>Here is the most current info available from Microsoft
on this issue:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;838306
>
>--
>Tom Kaminski IIS MVP
>http://www.iistoolshed.com/ - tools, scripts, and
utilities for running IIS
>http://mvp.support.microsoft.com/
>http://www.microsoft.com/windowsserver2003/community/cent
ers/iis/
>
>
>
>.
I've had that paged bookmarked for a few weeks now, is
that really the most current info microsoft has
available? It is over 6 weeks old now. Recycling
processes on a production server and losing session state
is not a viable work around. I was so happy to see that
kb article when I found it a month ago, I assumed that
once Microsoft recognized it as a bug they would do
something about it.

Should we be moving our applications back to windows 2000
or someother OS, or is Microsoft going to do something
about this problem?

Charley

Re: IIS on Windows 2003 hang on ASP sites by Pat

Pat
Mon Apr 26 21:27:10 CDT 2004

Before jumping to any conclusions, we can verify that the issue is the Jet
bug. Just run IISState (www.iisfaq.com/iisstate) against the w3wp.exe
process. If you post the log, we can verify the issue. If it is confirmed
as the Jet issue, then you will need to open a support incident. The
incident should be free of charge.

Pat


"Andrea Frigo" <a.frigo@monforte.it> wrote in message
news:jG7jc.685$%x6.106@news.edisontel.com...
> We migrated our web sites from windows 2000 Server to Windows 2003 server
> and we're having a frequent problem for many application pools, which
result
> in IIS hanging and not serving any more .asp page, while answering to
static
> files requests.
> All the web sites hanging use MS Access and ADO via OLEDB connections.
> The problem occurs frequently, about 5/6 times a day for the most accessed
> websites.
> The event viewer sometimes reports errors for the W3SVC application: when
> this happens the application seems to recycle and continue working. When
the
> pool hangs, not event is written into the event viewer.
> Watching into Microsoft forums we heard about the Jet bug, we tryed to
> install the Jet Engine sp8, but that didn't solve the problem.
> What can we do?
>
> Many thanks,
> Andrea Frigo
>
>



Re: IIS on Windows 2003 hang on ASP sites by Ruben

Ruben
Mon May 03 10:39:38 CDT 2004

We are currently having the same exact problem.
We migrated over sites from W2k to W2k3 to a much more
powerful machine.

The sites ran perfectly on W2K but now cause the asp.dll
to hang after various lengths of time (usually between 15
minutes and 2 hours).

We have paid for a support incident with Microsoft and
they are looking at the logs. It only occurs on two of
our sites that are accessing an Access Database through
Jet OLEDB. These sites ran perfectly for months without
having to reboot the server on W2K.

It gives the following error in Event Viewer:
"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
29% of the request queue is full.'."

I tried looking for the KB article, but it has been taken
down by Microsoft.

Re: IIS on Windows 2003 hang on ASP sites by jon

jon
Sat May 08 17:09:09 CDT 2004

Any news on this?

I have the same JET 2003 IIS hanging problem...

I am having to migrate the DB from MS Access to mysql to fix the prob
as from looking around the net there is still no fix for this bug?


"Ruben N" <anonymous@discussions.microsoft.com> wrote in message news:<7ac901c43124$d838a0b0$a001280a@phx.gbl>...
> We are currently having the same exact problem.
> We migrated over sites from W2k to W2k3 to a much more
> powerful machine.
>
> The sites ran perfectly on W2K but now cause the asp.dll
> to hang after various lengths of time (usually between 15
> minutes and 2 hours).
>
> We have paid for a support incident with Microsoft and
> they are looking at the logs. It only occurs on two of
> our sites that are accessing an Access Database through
> Jet OLEDB. These sites ran perfectly for months without
> having to reboot the server on W2K.
>
> It gives the following error in Event Viewer:
> "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
> 29% of the request queue is full.'."
>
> I tried looking for the KB article, but it has been taken
> down by Microsoft.

Re: IIS on Windows 2003 hang on ASP sites by Pat

Pat
Sun May 09 11:50:17 CDT 2004

Open a case w/MS-Support. There is a beta fix that addresses the issue.

Pat

"Jon Eastwood" <jon@spiralsites.com> wrote in message
news:3b88a457.0405081409.38b1d0d0@posting.google.com...
> Any news on this?
>
> I have the same JET 2003 IIS hanging problem...
>
> I am having to migrate the DB from MS Access to mysql to fix the prob
> as from looking around the net there is still no fix for this bug?
>
>
> "Ruben N" <anonymous@discussions.microsoft.com> wrote in message
news:<7ac901c43124$d838a0b0$a001280a@phx.gbl>...
> > We are currently having the same exact problem.
> > We migrated over sites from W2k to W2k3 to a much more
> > powerful machine.
> >
> > The sites ran perfectly on W2K but now cause the asp.dll
> > to hang after various lengths of time (usually between 15
> > minutes and 2 hours).
> >
> > We have paid for a support incident with Microsoft and
> > they are looking at the logs. It only occurs on two of
> > our sites that are accessing an Access Database through
> > Jet OLEDB. These sites ran perfectly for months without
> > having to reboot the server on W2K.
> >
> > It gives the following error in Event Viewer:
> > "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
> > 29% of the request queue is full.'."
> >
> > I tried looking for the KB article, but it has been taken
> > down by Microsoft.



Re: IIS on Windows 2003 hang on ASP sites by David

David
Tue Aug 31 20:28:28 CDT 2004

To use IISState, do this the next time the hang happens:

run "cscript.exe %windir%\system32\iisapp.vbs" to list the PIDs of the
worker process(es) in your IIS app pools.

Then, run "iisstate -d -p xxxx" where xxxx is the PID of worker process
experiencing the hang.

"David" <David@discussions.microsoft.com> wrote in message
news:F85A6970-DD89-4623-998C-CEA28F2D0786@microsoft.com...
> I've got the same problem but on a site using SQL Server 2000 not access!
> I'm
> currently at a complete loss what to do. I've installed IISState, but
> don't
> know how to use it. The event viewer shows "ASP unhealthy because 100% of
> executing requests are hung". Any suggestions beyong the Jet solution VERY
> gratefully received.
>
> "Matt Temple" wrote:
>
>> I had this problem, too. I haven't seen any type of patch/update
>> available to download or any mention of steps to fix the problem
>> permanently. So, I moved over 30 sites back to W2K. =(
>>
>>
>>
>> *** Sent via Devdex http://www.devdex.com ***
>> Don't just participate in USENET...get rewarded for it!
>>



RE: IIS on Windows 2003 hang on ASP sites by JF

JF
Fri Sep 03 07:23:04 CDT 2004

We have the same structure like you are and also experiencing this exact same
problem for three days now since we moved to w2k3. It is ridicules after
reading so many people experiencing this issue and no solutions yet.

We also noticed something else that is strange. On our webserver itself, we
did a test by opening an asp page that takes authentication information to
see if you are a member or guest, it calls another asp to check, if the
account is valid, and returns TRUE and opens a session to keep this
connection. Then we click a test asp page that does not have jet or any
other application pool in that page. On that page it will have 'logout'
option if you are currently login. Vice versa if you have not log in it will
show 'login'. We notice if we keep on refresh this test page (reload or
press F5), the page will show login, logout, login,logout.......cycling
itself every time we refresh. Then we will see the ASP Template cache
counter in the performance monitor climb. This is really strange.

Tomorrow we are going to move back to w2k since this problem is jeopardizing
our business reputation and too many complain calls from our customers.

"Andrea Frigo" wrote:

> We migrated our web sites from windows 2000 Server to Windows 2003 server
> and we're having a frequent problem for many application pools, which result
> in IIS hanging and not serving any more .asp page, while answering to static
> files requests.
> All the web sites hanging use MS Access and ADO via OLEDB connections.
> The problem occurs frequently, about 5/6 times a day for the most accessed
> websites.
> The event viewer sometimes reports errors for the W3SVC application: when
> this happens the application seems to recycle and continue working. When the
> pool hangs, not event is written into the event viewer.
> Watching into Microsoft forums we heard about the Jet bug, we tryed to
> install the Jet Engine sp8, but that didn't solve the problem.
> What can we do?
>
> Many thanks,
> Andrea Frigo
>
>
>