If you are logging in through terminal services, then you
won't be able to see that command fire off.
I would execute that at the console, but only have it
execute the cmd.exe process. Then type in the rest of
that iis command manually, just to see the output.
Oh, well scheduled tasks still work, it is just that they
run on the console, and therefore you can't interact with
them through terminal services. You need to be at the
console.
I don't need to interact with it. All I need to see is the log file after
the crash.
Do you know the answer to my question? What is wrong with the syntax?
7As I said before, why don't you try using the scheduled
tasks to bring up a cmd prompt, then try typing in the
command manually. I'm sure from this small experiment
you'll see your problem, since you are doing the exact
same thing your script would do.
If sitting at the console that works like a champ. You won't be able to
see/test anything while logged into TS if you do it that way. That is the
entire idea behind making it run as a scheduled task.
I know this is possible since I have seen several places that this is the
only way to run iisstate when using TS