Hi Pat
1) Ok, I will give it another go. Are you saying that IISState can be run
on W2K Server via Terminal Services? It is the latest version as far as I
am able to make it through windows update etc.
2) My point is that those of us using T/S will need to run IISState so as to
accept the license agreement rather than schedule it to run as is suggested
on the IIS State Website. It is confusing... to accept the dialog you must
run it via T/S, but it says it will not work over T/S on W2K. What happens
if you do run it via T/S and the underlying API's are not the latest
version? Does it kill the IIS process?
Thanks
David
"Pat [MSFT]" <patfilot.RemoveThis@online.microsoft.com> wrote in message
news:uvsKaCUAEHA.4060@TK2MSFTNGP10.phx.gbl...
> 1) The reason it wouldn't run through terminal services was that the
> underlying OS Debug API's didn't allow it. These have been changed, so
for
> some machines it will, some (not fully up to date) it won't.
> 2) The license dialogue is for the downloading of symbols from
Microsoft.com
> which are needed for the analysis engine. IISState will hang until you
> click OK or Cancel on the dialogue.
> 3) When IISState runs the first time, it must download quite a few
symbols.
> This can take a while. Check the \symbols directory found in the IISState
> directory and see if there were any symbols downloaded. After they are
> downloaded, IISState will use the local copies to speed things along.
>
> You did use the correct command line.
>
> Pat
>
> "David Morgan" <david.RemoveThis@davidmorgan.me.uk> wrote in message
> news:OgAKfvQAEHA.2800@tk2msftngp13.phx.gbl...
> > Hi
> >
> > I am having a problem where by visitors to our website are failing to
> > receive all of the resulting HTML from a number of different ASPs. This
> > problem is intermittent and the amount of HTML delivered, (as seen in
view
> > source), varies for the same page for different requests.
> >
> > I was advised to install and run IIS State but of course this problem is
> > occurring on a server hosted with an ISP and I only have Terminal
Services
> > access to it. I set up a scheduled task to run but it kept failing. So
> > despite being told that it didn't run under T/S, I ran it and up popped
a
> MS
> > License Agreement Dialog. This may explain why it failed to run as a
S/T.
> > Is this license agreement for the symbols or something? Is this a new
> thing
> > since the IISState documentation for running under T/S or have I done
> > something wrong?
> >
> > I am not looking for a soft crash or hard crash, just some information
> that
> > may help someone ascertain why my pages are randomly not being fully
> > delivered to the client. This is the command I used: iistate.exe -p
> 1104 -d
> >
> > Then, the program appeared to hang so I hit Ctrl+C which was successful
> > although the webservice was hung/paused and could not be controlled
using
> > net stop/start. How long should IISState take to execute?
> >
> > Have had to reboot the server which is not good as we have about 50
> > concurrent users most of the time.
> >
> > Regards
> >
> > David M
> >
> >
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Running IIS State on Production Machine Hosted Externally