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