IISState Question

I downloaded and installed the file iisstate.msi which contained the
debugging files and was installed in C:\iisstate. I ran it from the command
line with the following syntax: c:\iisstate>iisstate -p 1440 -d -sc. It came
up version 6.2.0013.1. The output and symbols folders were created.

Where it "seemed" to fail was with the following line: "The call to
LoadLibrary (exts) failed, WIN32 error 2 The system cannot find the file
specified" Below that was the line: Executable search path is: followed by
ModLoad.. etc.. with dozens of .dll files
No symbols where downloaded to the symbols folder.

Is what I am seeing normal or did I set it up wrong? Do I need to leave the
command prompt window open allowing this program to continue running?

Pat
Thu Dec 09 14:39:09 CST 2004

What problem are you trying to debug?

If you are trying to identify a hang, the command line to use is:

iisstate -p <pid> -d <enter>

For a crash (i.e. terminating process):

iisstate -p <pid> -d -sc <enter>

For either, you need to leave the command window open until iisstate
completes. In the crash configuration, IISState will attach to the suspect
process and wait for the crash to occur. This can take hours or even days.
Just leave it there.


Pat

"Ozzie" <none@none.com> wrote in message
news:%23BW0qdh3EHA.3616@TK2MSFTNGP11.phx.gbl...
>I downloaded and installed the file iisstate.msi which contained the
>debugging files and was installed in C:\iisstate. I ran it from the command
>line with the following syntax: c:\iisstate>iisstate -p 1440 -d -sc. It
>came up version 6.2.0013.1. The output and symbols folders were created.
>
> Where it "seemed" to fail was with the following line: "The call to
> LoadLibrary (exts) failed, WIN32 error 2 The system cannot find the file
> specified" Below that was the line: Executable search path is: followed by
> ModLoad.. etc.. with dozens of .dll files
> No symbols where downloaded to the symbols folder.
>
> Is what I am seeing normal or did I set it up wrong? Do I need to leave
> the command prompt window open allowing this program to continue running?
>

George
Thu Dec 09 22:06:14 CST 2004

He has a "not found error." That is not good and likely the dump will =
never be made or be erroneous. As far as I
know we have to download the debugging tools and install them prior to =
installing iisstate. It is a 7MB file
available from Microsoft. It is called debugplus.msi

--=20
George Hester
_________________________________
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message =
news:uyVno8i3EHA.2676@TK2MSFTNGP12.phx.gbl...
> What problem are you trying to debug?
>=20
> If you are trying to identify a hang, the command line to use is:
>=20
> iisstate -p <pid> -d <enter>
>=20
> For a crash (i.e. terminating process):
>=20
> iisstate -p <pid> -d -sc <enter>
>=20
> For either, you need to leave the command window open until iisstate=20
> completes. In the crash configuration, IISState will attach to the =
suspect=20
> process and wait for the crash to occur. This can take hours or even =
days.=20
> Just leave it there.
>=20
>=20
> Pat
>=20
> "Ozzie" <none@none.com> wrote in message=20
> news:%23BW0qdh3EHA.3616@TK2MSFTNGP11.phx.gbl...
> >I downloaded and installed the file iisstate.msi which contained the=20
> >debugging files and was installed in C:\iisstate. I ran it from the =
command=20
> >line with the following syntax: c:\iisstate>iisstate -p 1440 -d -sc. =
It=20
> >came up version 6.2.0013.1. The output and symbols folders were =
created.
> >
> > Where it "seemed" to fail was with the following line: "The call to=20
> > LoadLibrary (exts) failed, WIN32 error 2 The system cannot find the =
file=20
> > specified" Below that was the line: Executable search path is: =
followed by=20
> > ModLoad.. etc.. with dozens of .dll files
> > No symbols where downloaded to the symbols folder.
> >
> > Is what I am seeing normal or did I set it up wrong? Do I need to =
leave=20
> > the command prompt window open allowing this program to continue =
running?
> >=20
>=20
>

Ozzie
Fri Dec 10 07:36:43 CST 2004

I left off the -sc and the symbols were downloaded. I was only looking for
a hang. The program did finish after a number of threads were recorded, so
it looks like there would be no reason to leave the window open. I am
guessing here as this is the first time I ran it.


"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:uyVno8i3EHA.2676@TK2MSFTNGP12.phx.gbl...
> What problem are you trying to debug?
>
> If you are trying to identify a hang, the command line to use is:
>
> iisstate -p <pid> -d <enter>
>
> For a crash (i.e. terminating process):
>
> iisstate -p <pid> -d -sc <enter>
>
> For either, you need to leave the command window open until iisstate
> completes. In the crash configuration, IISState will attach to the
> suspect process and wait for the crash to occur. This can take hours or
> even days. Just leave it there.
>
>
> Pat
>
> "Ozzie" <none@none.com> wrote in message
> news:%23BW0qdh3EHA.3616@TK2MSFTNGP11.phx.gbl...
>>I downloaded and installed the file iisstate.msi which contained the
>>debugging files and was installed in C:\iisstate. I ran it from the
>>command line with the following syntax: c:\iisstate>iisstate -p
>>1440 -d -sc. It came up version 6.2.0013.1. The output and symbols folders
>>were created.
>>
>> Where it "seemed" to fail was with the following line: "The call to
>> LoadLibrary (exts) failed, WIN32 error 2 The system cannot find the file
>> specified" Below that was the line: Executable search path is: followed
>> by ModLoad.. etc.. with dozens of .dll files
>> No symbols where downloaded to the symbols folder.
>>
>> Is what I am seeing normal or did I set it up wrong? Do I need to leave
>> the command prompt window open allowing this program to continue running?
>>
>
>

Ozzie
Fri Dec 10 07:38:03 CST 2004

The debug files came with iisstate.msi so it looks to be working thus far.


"George Hester" <hesterloli@hotmail.com> wrote in message
news:uBP9Y2m3EHA.3120@TK2MSFTNGP12.phx.gbl...
He has a "not found error." That is not good and likely the dump will never
be made or be erroneous. As far as I
know we have to download the debugging tools and install them prior to
installing iisstate. It is a 7MB file
available from Microsoft. It is called debugplus.msi

--
George Hester
_________________________________
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:uyVno8i3EHA.2676@TK2MSFTNGP12.phx.gbl...
> What problem are you trying to debug?
>
> If you are trying to identify a hang, the command line to use is:
>
> iisstate -p <pid> -d <enter>
>
> For a crash (i.e. terminating process):
>
> iisstate -p <pid> -d -sc <enter>
>
> For either, you need to leave the command window open until iisstate
> completes. In the crash configuration, IISState will attach to the
> suspect
> process and wait for the crash to occur. This can take hours or even
> days.
> Just leave it there.
>
>
> Pat
>
> "Ozzie" <none@none.com> wrote in message
> news:%23BW0qdh3EHA.3616@TK2MSFTNGP11.phx.gbl...
> >I downloaded and installed the file iisstate.msi which contained the
> >debugging files and was installed in C:\iisstate. I ran it from the
> >command
> >line with the following syntax: c:\iisstate>iisstate -p 1440 -d -sc. It
> >came up version 6.2.0013.1. The output and symbols folders were created.
> >
> > Where it "seemed" to fail was with the following line: "The call to
> > LoadLibrary (exts) failed, WIN32 error 2 The system cannot find the file
> > specified" Below that was the line: Executable search path is: followed
> > by
> > ModLoad.. etc.. with dozens of .dll files
> > No symbols where downloaded to the symbols folder.
> >
> > Is what I am seeing normal or did I set it up wrong? Do I need to leave
> > the command prompt window open allowing this program to continue
> > running?
> >
>
>

Pat
Fri Dec 10 11:36:25 CST 2004

The "file not found" message refers to the debug extensions that the
debugger engine attempts to initialize. IISState does not use them, it only
uses sos.dll (for .Net debugging) which is not on that list.

Pat

"Ozzie" <none@none.com> wrote in message
news:Ozy041r3EHA.3452@TK2MSFTNGP14.phx.gbl...
> The debug files came with iisstate.msi so it looks to be working thus far.
>
>
> "George Hester" <hesterloli@hotmail.com> wrote in message
> news:uBP9Y2m3EHA.3120@TK2MSFTNGP12.phx.gbl...
> He has a "not found error." That is not good and likely the dump will
> never be made or be erroneous. As far as I
> know we have to download the debugging tools and install them prior to
> installing iisstate. It is a 7MB file
> available from Microsoft. It is called debugplus.msi
>
> --
> George Hester
> _________________________________
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
> news:uyVno8i3EHA.2676@TK2MSFTNGP12.phx.gbl...
>> What problem are you trying to debug?
>>
>> If you are trying to identify a hang, the command line to use is:
>>
>> iisstate -p <pid> -d <enter>
>>
>> For a crash (i.e. terminating process):
>>
>> iisstate -p <pid> -d -sc <enter>
>>
>> For either, you need to leave the command window open until iisstate
>> completes. In the crash configuration, IISState will attach to the
>> suspect
>> process and wait for the crash to occur. This can take hours or even
>> days.
>> Just leave it there.
>>
>>
>> Pat
>>
>> "Ozzie" <none@none.com> wrote in message
>> news:%23BW0qdh3EHA.3616@TK2MSFTNGP11.phx.gbl...
>> >I downloaded and installed the file iisstate.msi which contained the
>> >debugging files and was installed in C:\iisstate. I ran it from the
>> >command
>> >line with the following syntax: c:\iisstate>iisstate -p 1440 -d -sc. It
>> >came up version 6.2.0013.1. The output and symbols folders were created.
>> >
>> > Where it "seemed" to fail was with the following line: "The call to
>> > LoadLibrary (exts) failed, WIN32 error 2 The system