 |
|
|
|
Next: IIS hang investigation ?
|
| Author |
Message |
External
Since: Sep 01, 2003
Posts: 15
|
(Msg. 1) Posted: Tue Sep 02, 2003 9:53 am
Post subject: Trying to understand how to use iisstate...but not getting much result
Archived from groups: microsoft>public>inetserver>iis (more info?)
|
|
|
I need to determine where I am getting into a loop on a production system.
To do this I need to understand how I can use iisstate. To do that, I set
up a test situation as follows:
(All of the following is being done under Win 2000 Pro; "localhost"; IIS
5.0)
I set up a TIGHT loop in VB.SCRIPT; then set my ScriptTimeout to 10 minutes.
Then I started iisstate. Since DLLHOST.EXE is in the loop, should I be
monitoring it's ProcessID, or the ProcessID of inetinfo? Anyway, I tried
both...at different times. One of the entries in the log that keeps showing
up is:
"Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis."
....and I don't see anything that identifies the name of the ASP page, nor
much of anything else that makes any sense.
What can I do so that I can at least recognize the name of the ASP page that
I am on. Also, in my "real world" problem, I have a component that might be
causing the loop. How will I be able to identify it?
TIA,
Larry Woods |
|
| Back to top |
|
 | |
External
Since: Aug 24, 2003
Posts: 1478
|
(Msg. 2) Posted: Tue Sep 02, 2003 9:18 pm
Post subject: Re: Trying to understand how to use iisstate...but not getting much result [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
You run IISState against the process that is hosting the page. In this
case, it would be dllhost.exe.
The 'Possible ASP' and 'Possible DCOM' mean just that. IISState scans
threads looking for ones that are likely candidates for running ASP pages.
Since, in the real world, symbols are not always available and threads are
not always fully scanned (due to optimizers,etc.), a certain 'flexibility'
is required. For example, if IISState sees that RPCRT4.dll is on the stack,
then it will report that the thread is a possible ASP page and a Possible
DCOM call. RPCRT4 owns things like cross apartment and cross process
marshalling.
If the ASP.dll is not on the stack, then the ASP symbols won't be found and
you will get that message. So, basically you are seeing that the thread is
not running an ASP page.
As to the component identification, IISState will show the full thread
stack. You should be able to see the dll on the thread in question. If you
want more information (i.e. function name, source line number), you will
need to provide symbols for the dll. When you compile the dll, place the
generated symbols (.pdb files) in the directory with the dll on the server.
Keep in mind that symbols are build specific, so if you use change control,
make sure you build the symbols for the dll that is running on the server.
If you need help w/a log you can post it to the group.
iisstate -p <pid for dllhost> <enter>
Pat
"Larry Woods" <larry DeleteThis @lwoods.com> wrote in message
news:eqoM%23mVcDHA.2932@tk2msftngp13.phx.gbl...
> I need to determine where I am getting into a loop on a production system.
> To do this I need to understand how I can use iisstate. To do that, I set
> up a test situation as follows:
>
> (All of the following is being done under Win 2000 Pro; "localhost"; IIS
> 5.0)
>
> I set up a TIGHT loop in VB.SCRIPT; then set my ScriptTimeout to 10
minutes.
> Then I started iisstate. Since DLLHOST.EXE is in the loop, should I be
> monitoring it's ProcessID, or the ProcessID of inetinfo? Anyway, I tried
> both...at different times. One of the entries in the log that keeps
showing
> up is:
>
> "Thread Type: Possible ASP page. Possible DCOM activity
> Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> Continuing with other analysis."
>
> ...and I don't see anything that identifies the name of the ASP page, nor
> much of anything else that makes any sense.
>
> What can I do so that I can at least recognize the name of the ASP page
that
> I am on. Also, in my "real world" problem, I have a component that might
be
> causing the loop. How will I be able to identify it?
>
> TIA,
>
> Larry Woods
>
><!-- ~MESSAGE_AFTER~ --> |
|
| Back to top |
|
| |
External
Since: Sep 01, 2003
Posts: 15
|
(Msg. 3) Posted: Tue Sep 02, 2003 9:48 pm
Post subject: Re: Trying to understand how to use iisstate...but not getting much result [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Great help, Pat. Thanks much. I don't think I will have very good luck
with the dll though since it's a VB 6.0-based component. But at least I can
figure out whether it's an ASP page, or the component that is causing the
problem. That will be a BIG help.
Larry
"Pat [MSFT]" <patfilot.TakeThisOut@online.microsoft.com> wrote in message
news:eLvEdlbcDHA.1828@TK2MSFTNGP10.phx.gbl...
> You run IISState against the process that is hosting the page. In this
> case, it would be dllhost.exe.
>
> The 'Possible ASP' and 'Possible DCOM' mean just that. IISState scans
> threads looking for ones that are likely candidates for running ASP pages.
> Since, in the real world, symbols are not always available and threads are
> not always fully scanned (due to optimizers,etc.), a certain 'flexibility'
> is required. For example, if IISState sees that RPCRT4.dll is on the
stack,
> then it will report that the thread is a possible ASP page and a Possible
> DCOM call. RPCRT4 owns things like cross apartment and cross process
> marshalling.
>
> If the ASP.dll is not on the stack, then the ASP symbols won't be found
and
> you will get that message. So, basically you are seeing that the thread
is
> not running an ASP page.
>
> As to the component identification, IISState will show the full thread
> stack. You should be able to see the dll on the thread in question. If
you
> want more information (i.e. function name, source line number), you will
> need to provide symbols for the dll. When you compile the dll, place the
> generated symbols (.pdb files) in the directory with the dll on the
server.
> Keep in mind that symbols are build specific, so if you use change
control,
> make sure you build the symbols for the dll that is running on the server.
>
> If you need help w/a log you can post it to the group.
>
> iisstate -p <pid for dllhost> <enter>
>
> Pat
>
>
> "Larry Woods" <larry.TakeThisOut@lwoods.com> wrote in message
> news:eqoM%23mVcDHA.2932@tk2msftngp13.phx.gbl...
> > I need to determine where I am getting into a loop on a production
system.
> > To do this I need to understand how I can use iisstate. To do that, I
set
> > up a test situation as follows:
> >
> > (All of the following is being done under Win 2000 Pro; "localhost"; IIS
> > 5.0)
> >
> > I set up a TIGHT loop in VB.SCRIPT; then set my ScriptTimeout to 10
> minutes.
> > Then I started iisstate. Since DLLHOST.EXE is in the loop, should I be
> > monitoring it's ProcessID, or the ProcessID of inetinfo? Anyway, I
tried
> > both...at different times. One of the entries in the log that keeps
> showing
> > up is:
> >
> > "Thread Type: Possible ASP page. Possible DCOM activity
> > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> > Continuing with other analysis."
> >
> > ...and I don't see anything that identifies the name of the ASP page,
nor
> > much of anything else that makes any sense.
> >
> > What can I do so that I can at least recognize the name of the ASP page
> that
> > I am on. Also, in my "real world" problem, I have a component that
might
> be
> > causing the loop. How will I be able to identify it?
> >
> > TIA,
> >
> > Larry Woods
> >
> >
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Trying to understand how to use iisstate...but not getting.. |
|
| Back to top |
|
| |
External
Since: Aug 24, 2003
Posts: 1478
|
(Msg. 4) Posted: Wed Sep 03, 2003 1:18 am
Post subject: Re: Trying to understand how to use iisstate...but not getting much result [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Actually even if it is VB, if you compile the symbols (it is in the Project
Properties, Compile Options), you will get a lot of information. The thread
stack (if it is the problem) will show:
DllName!ClassName::FunctionName (c:\codedir\classfilename.cls line xx)
Pat
"Larry Woods" <larry.TakeThisOut@lwoods.com> wrote in message
news:espcd2bcDHA.1488@TK2MSFTNGP12.phx.gbl...
> Great help, Pat. Thanks much. I don't think I will have very good luck
> with the dll though since it's a VB 6.0-based component. But at least I
can
> figure out whether it's an ASP page, or the component that is causing the
> problem. That will be a BIG help.
>
> Larry
>
> "Pat [MSFT]" <patfilot.TakeThisOut@online.microsoft.com> wrote in message
> news:eLvEdlbcDHA.1828@TK2MSFTNGP10.phx.gbl...
> > You run IISState against the process that is hosting the page. In this
> > case, it would be dllhost.exe.
> >
> > The 'Possible ASP' and 'Possible DCOM' mean just that. IISState scans
> > threads looking for ones that are likely candidates for running ASP
pages.
> > Since, in the real world, symbols are not always available and threads
are
> > not always fully scanned (due to optimizers,etc.), a certain
'flexibility'
> > is required. For example, if IISState sees that RPCRT4.dll is on the
> stack,
> > then it will report that the thread is a possible ASP page and a
Possible
> > DCOM call. RPCRT4 owns things like cross apartment and cross process
> > marshalling.
> >
> > If the ASP.dll is not on the stack, then the ASP symbols won't be found
> and
> > you will get that message. So, basically you are seeing that the thread
> is
> > not running an ASP page.
> >
> > As to the component identification, IISState will show the full thread
> > stack. You should be able to see the dll on the thread in question. If
> you
> > want more information (i.e. function name, source line number), you will
> > need to provide symbols for the dll. When you compile the dll, place
the
> > generated symbols (.pdb files) in the directory with the dll on the
> server.
> > Keep in mind that symbols are build specific, so if you use change
> control,
> > make sure you build the symbols for the dll that is running on the
server.
> >
> > If you need help w/a log you can post it to the group.
> >
> > iisstate -p <pid for dllhost> <enter>
> >
> > Pat
> >
> >
> > "Larry Woods" <larry.TakeThisOut@lwoods.com> wrote in message
> > news:eqoM%23mVcDHA.2932@tk2msftngp13.phx.gbl...
> > > I need to determine where I am getting into a loop on a production
> system.
> > > To do this I need to understand how I can use iisstate. To do that, I
> set
> > > up a test situation as follows:
> > >
> > > (All of the following is being done under Win 2000 Pro; "localhost";
IIS
> > > 5.0)
> > >
> > > I set up a TIGHT loop in VB.SCRIPT; then set my ScriptTimeout to 10
> > minutes.
> > > Then I started iisstate. Since DLLHOST.EXE is in the loop, should I
be
> > > monitoring it's ProcessID, or the ProcessID of inetinfo? Anyway, I
> tried
> > > both...at different times. One of the entries in the log that keeps
> > showing
> > > up is:
> > >
> > > "Thread Type: Possible ASP page. Possible DCOM activity
> > > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> > > Continuing with other analysis."
> > >
> > > ...and I don't see anything that identifies the name of the ASP page,
> nor
> > > much of anything else that makes any sense.
> > >
> > > What can I do so that I can at least recognize the name of the ASP
page
> > that
> > > I am on. Also, in my "real world" problem, I have a component that
> might
> > be
> > > causing the loop. How will I be able to identify it?
> > >
> > > TIA,
> > >
> > > Larry Woods
> > >
> > >
> >
> >
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Trying to understand how to use iisstate...but not getting.. |
|
| Back to top |
|
| |
External
Since: Aug 26, 2003
Posts: 4
|
(Msg. 5) Posted: Thu Sep 04, 2003 9:12 pm
Post subject: Re: Trying to understand how to use iisstate...but not getting much result [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I saw the usage of IISState is "iisstate.exe -p <PID> [-d] [-hc] [-sc]
<enter>"
Does it mean the PID should be the PID of "dllhost.exe" but not the PID of
"inetinfo.exe"
"Pat [MSFT]" <patfilot RemoveThis @online.microsoft.com> 在郵件
news:eLvEdlbcDHA.1828@TK2MSFTNGP10.phx.gbl 中撰寫...
> You run IISState against the process that is hosting the page. In this
> case, it would be dllhost.exe.
>
> The 'Possible ASP' and 'Possible DCOM' mean just that. IISState scans
> threads looking for ones that are likely candidates for running ASP pages.
> Since, in the real world, symbols are not always available and threads are
> not always fully scanned (due to optimizers,etc.), a certain 'flexibility'
> is required. For example, if IISState sees that RPCRT4.dll is on the
stack,
> then it will report that the thread is a possible ASP page and a Possible
> DCOM call. RPCRT4 owns things like cross apartment and cross process
> marshalling.
>
> If the ASP.dll is not on the stack, then the ASP symbols won't be found
and
> you will get that message. So, basically you are seeing that the thread
is
> not running an ASP page.
>
> As to the component identification, IISState will show the full thread
> stack. You should be able to see the dll on the thread in question. If
you
> want more information (i.e. function name, source line number), you will
> need to provide symbols for the dll. When you compile the dll, place the
> generated symbols (.pdb files) in the directory with the dll on the
server.
> Keep in mind that symbols are build specific, so if you use change
control,
> make sure you build the symbols for the dll that is running on the server.
>
> If you need help w/a log you can post it to the group.
>
> iisstate -p <pid for dllhost> <enter>
>
> Pat
>
>
> "Larry Woods" <larry RemoveThis @lwoods.com> wrote in message
> news:eqoM%23mVcDHA.2932@tk2msftngp13.phx.gbl...
> > I need to determine where I am getting into a loop on a production
system.
> > To do this I need to understand how I can use iisstate. To do that, I
set
> > up a test situation as follows:
> >
> > (All of the following is being done under Win 2000 Pro; "localhost"; IIS
> > 5.0)
> >
> > I set up a TIGHT loop in VB.SCRIPT; then set my ScriptTimeout to 10
> minutes.
> > Then I started iisstate. Since DLLHOST.EXE is in the loop, should I be
> > monitoring it's ProcessID, or the ProcessID of inetinfo? Anyway, I
tried
> > both...at different times. One of the entries in the log that keeps
> showing
> > up is:
> >
> > "Thread Type: Possible ASP page. Possible DCOM activity
> > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> > Continuing with other analysis."
> >
> > ...and I don't see anything that identifies the name of the ASP page,
nor
> > much of anything else that makes any sense.
> >
> > What can I do so that I can at least recognize the name of the ASP page
> that
> > I am on. Also, in my "real world" problem, I have a component that
might
> be
> > causing the loop. How will I be able to identify it?
> >
> > TIA,
> >
> > Larry Woods
> >
> >
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Trying to understand how to use iisstate...but not getting.. |
|
| Back to top |
|
| |
External
Since: Aug 24, 2003
Posts: 1478
|
(Msg. 6) Posted: Thu Sep 04, 2003 9:12 pm
Post subject: Re: Trying to understand how to use iisstate...but not getting much result [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Right.
"Fiona" <fiona DeleteThis @fionacheung.com> wrote in message
news:uEfHWzscDHA.1656@TK2MSFTNGP10.phx.gbl...
> I saw the usage of IISState is "iisstate.exe -p <PID> [-d] [-hc] [-sc]
> <enter>"
>
> Does it mean the PID should be the PID of "dllhost.exe" but not the PID of
> "inetinfo.exe"
>
>
> "Pat [MSFT]" <patfilot DeleteThis @online.microsoft.com> 在郵件
> news:eLvEdlbcDHA.1828@TK2MSFTNGP10.phx.gbl 中撰寫...
> > You run IISState against the process that is hosting the page. In this
> > case, it would be dllhost.exe.
> >
> > The 'Possible ASP' and 'Possible DCOM' mean just that. IISState scans
> > threads looking for ones that are likely candidates for running ASP
pages.
> > Since, in the real world, symbols are not always available and threads
are
> > not always fully scanned (due to optimizers,etc.), a certain
'flexibility'
> > is required. For example, if IISState sees that RPCRT4.dll is on the
> stack,
> > then it will report that the thread is a possible ASP page and a
Possible
> > DCOM call. RPCRT4 owns things like cross apartment and cross process
> > marshalling.
> >
> > If the ASP.dll is not on the stack, then the ASP symbols won't be found
> and
> > you will get that message. So, basically you are seeing that the thread
> is
> > not running an ASP page.
> >
> > As to the component identification, IISState will show the full thread
> > stack. You should be able to see the dll on the thread in question. If
> you
> > want more information (i.e. function name, source line number), you will
> > need to provide symbols for the dll. When you compile the dll, place
the
> > generated symbols (.pdb files) in the directory with the dll on the
> server.
> > Keep in mind that symbols are build specific, so if you use change
> control,
> > make sure you build the symbols for the dll that is running on the
server.
> >
> > If you need help w/a log you can post it to the group.
> >
> > iisstate -p <pid for dllhost> <enter>
> >
> > Pat
> >
> >
> > "Larry Woods" <larry DeleteThis @lwoods.com> wrote in message
> > news:eqoM%23mVcDHA.2932@tk2msftngp13.phx.gbl...
> > > I need to determine where I am getting into a loop on a production
> system.
> > > To do this I need to understand how I can use iisstate. To do that, I
> set
> > > up a test situation as follows:
> > >
> > > (All of the following is being done under Win 2000 Pro; "localhost";
IIS
> > > 5.0)
> > >
> > > I set up a TIGHT loop in VB.SCRIPT; then set my ScriptTimeout to 10
> > minutes.
> > > Then I started iisstate. Since DLLHOST.EXE is in the loop, should I
be
> > > monitoring it's ProcessID, or the ProcessID of inetinfo? Anyway, I
> tried
> > > both...at different times. One of the entries in the log that keeps
> > showing
> > > up is:
> > >
> > > "Thread Type: Possible ASP page. Possible DCOM activity
> > > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
> > > Continuing with other analysis."
> > >
> > > ...and I don't see anything that identifies the name of the ASP page,
> nor
> > > much of anything else that makes any sense.
> > >
> > > What can I do so that I can at least recognize the name of the ASP
page
> > that
> > > I am on. Also, in my "real world" problem, I have a component that
> might
> > be
> > > causing the loop. How will I be able to identify it?
> > >
> > > TIA,
> > >
> > > Larry Woods
> > >
> > >
> >
> >
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Trying to understand how to use iisstate...but not getting.. |
|
| Back to top |
|
| |
| Related Topics: | IISState No logs - I want to use Iisstate v3.1 to debug an intermittent crashing IIS4 install due to 100% cpu utilisation on a production sever. At present I'm testing the iisstate program on a non production NT4/IIS4 server using a CRASH.ASP script that forces ASP into....
Any other way to find out WHY dllhost.exe is looping...bes.. - My site gets into a loop about once a day. Luckily the server has dual cpus so the other dllhost.exe keeps the site up. On the other hand, once in a while BOTH cpus get the loop so that brings us down. All I know is that dllhost.exe is looping. How d...
IISState - Debugging package. How can I tell if it is ins.. - I have access to an ISP's server, and need to install iisstate, BUT I don't know whether the "dump pack" is on the server. Ist there some way I can test for this? And, if it is NOT on the server, if it is installed does it require a reboot? ...
IIS5 Freezes - Please examine IISState Logs - I am getting periodic freezeups in VB DLLs under IIS5 / Win2K Advanced Server SP4. The DLLs all have RetainInMemory & UnattendedExecution =true. The server has been patched with the latest MSVBVM60.dll, as per.. |
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
