Dumb question I'm sure, but...
I'm trying to install the iisstate tool to see if I'm having the infamous
jet database problem.  I don't see the inetinfo.exe process in the processes
list?!  I am logged in (via terminal services) as administrator.

I'm running w2k3.

Thanks.

And, is there really no fix for this problem?  Jeez I just spent $7K on a
new server and setup to migrate MANY sites over to which I've been running
for years and which are heavy Access sites and heavy traffic and have no
problems.  Now, I move to w2k3, iis6, the latest stuff, and put only a few
sites only to find immediately this strange hang on asp pages accessing
access db (using jet.oledb I might add).

Can I go back from jet 8 to an earler version and solve the problem?

Help!

Thanks,
Kevin

[ Post a follow-up to this message ]

1) In taskman, did you check the box to show all user's processes?

2) There is currently no fix, but regressing to an older build will not
help.  The issue has been there for a while, but some other OS changes have
exposed the problem.

Once confirmed, your best course of action will be to open a support
incident.

Pat

<nospam@4.me> wrote in message news:HuadnaULHp-fkN3dRVn-sw@comcast.com...
> Dumb question I'm sure, but...
> I'm trying to install the iisstate tool to see if I'm having the infamous
> jet database problem.  I don't see the inetinfo.exe process in the
processes
> list?!  I am logged in (via terminal services) as administrator.
>
> I'm running w2k3.
>
> Thanks.
>
> And, is there really no fix for this problem?  Jeez I just spent $7K on a
> new server and setup to migrate MANY sites over to which I've been running
> for years and which are heavy Access sites and heavy traffic and have no
> problems.  Now, I move to w2k3, iis6, the latest stuff, and put only a few
> sites only to find immediately this strange hang on asp pages accessing
> access db (using jet.oledb I might add).
>
> Can I go back from jet 8 to an earler version and solve the problem?
>
> Help!
>
> Thanks,
> Kevin
>
>

[ Post a follow-up to this message ]

Great - thanks.

Yes I just didn't have the box checked.  Woke up this morning to find things
hung again so ran it.

Next question: I ran it against the inetinfo.exe process but in the dump it
couldn't determine/show the actual asp page names.

Do I need to run iisstate against the inetinfo.exe, or against the w3wp.exe
processes?  If w3wp, how do I know which one to run it against (I have two,
one for the default pool and one for a new test pool)?

Thanks,
Kevin

"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:Or0TJ2b$DHA.2336@TK2MSFTNGP11.phx.gbl...
> 1) In taskman, did you check the box to show all user's processes?
>
> 2) There is currently no fix, but regressing to an older build will not
> help.  The issue has been there for a while, but some other OS changes
have
> exposed the problem.
>
> Once confirmed, your best course of action will be to open a support
> incident.
>
> Pat
>
> <nospam@4.me> wrote in message news:HuadnaULHp-fkN3dRVn-sw@comcast.com... 
infamous 
> processes 
a 
running 
few 
>
>

[ Post a follow-up to this message ]

w3wp.exe.

Just run it against both.

Pat

<nospam@4.me> wrote in message news:dpydnavjGcmDPt3d4p2dnA@comcast.com...
> Great - thanks.
>
> Yes I just didn't have the box checked.  Woke up this morning to find
things
> hung again so ran it.
>
> Next question: I ran it against the inetinfo.exe process but in the dump
it
> couldn't determine/show the actual asp page names.
>
> Do I need to run iisstate against the inetinfo.exe, or against the
w3wp.exe
> processes?  If w3wp, how do I know which one to run it against (I have
two,
> one for the default pool and one for a new test pool)?
>
> Thanks,
> Kevin
>
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
> news:Or0TJ2b$DHA.2336@TK2MSFTNGP11.phx.gbl... 
> have 
news:HuadnaULHp-fkN3dRVn-sw@comcast.com... 
> infamous 
on
> a 
> running 
no 
> few 
accessing 
>
>

[ Post a follow-up to this message ]