Vista - Re: Script works well, but not as scheduled tasks ?

"francois" <francois@newsgroup> wrote in message
news:eVtRfj4SKHA.4028@newsgroupI would take the following steps:
1. Check the Task Scheduler log file.
2. Instead of invoking the above script directly, invoke the following batch
file:
@echo off
echo %date% %time% %UserName% >> c:\test.txt
cscript //nologo c:\françois.vbs 1>> c:\test.txt 2>>&1
echo %date% %time% >> c:\test.txt
3. Remove the line "On error resume next" from your script. It makes
debuggin almost impossible.
4. Examine the file c:\test.txt.

"francois" <francois@newsgroup> wrote in message
news:ekveeE5SKHA.1232@newsgroupLet's have a look at your script and your version of the batch file I
suggested!

*** See below.
"francois" <francois@newsgroup> wrote in message
news:%23JVQ%235CTKHA.4144@newsgroup*** There have been numerous threads where I suggested
*** a certain batch file or script and the OP subsequently
*** claimed that it did not work. In most cases the failure
*** was caused by a poorly understood modification that
*** the OP made. This is why I now always ask for the
*** actual script or batch file.
*** The "run" method will execute your command in
*** the background. It will be invisible to you. If you
*** want to see the output generated by a console
*** command then you need to use the Exec method,
*** e.g. like so:
Set oWshShell = CreateObject("WScript.Shell")
commande = "c:\Windows\System32\shutdown.exe -s -m \\" & name & " -t 5"
Set oExec = oWshShell.Exec(commande)
While oExec.Status = 0
WScript.Sleep 500
Wend
While Not oExec.StdOut.AtEndOfStream
WScript.Echo oExec.StdOut.ReadLine
Wend
No, you did not forget anything. If you modify your VB Script as I suggested
then you will probably see why the shutdown command does not work. You could
also do some experimenting of your own, e.g. like so:

commande = "c:\Windows\System32\cmd.exe dir c:\"

This should write the output from the "dir" command into your log file
c:\test.txt.

francois wrote:Your shutdown.vbs does not contain any lines to create output. I would add a
Wscript.Echo line near the top and another one at the end so test.txt will
reflect that shutdown.vbs is being executed to completion.

Wscript.Echo Wscript.ScriptFullName & " started at " & now
....
Wscript.Echo Wscript.ScriptFullName & " finished at " & now

Once satisfied the script is running, I would try changing .run method to
..exec method. The difference being .run method creates a new seperate
process while .exec is a child of the current process.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

"Todd Vargo" <tlvargo@newsgroup> wrote in message
news:eE1jXsHTKHA.4360@newsgroupHas anyone thought to ask if the scheduled batch script is able to find
shutdown.vbs? Is it on the path or in the same directory as go.bat?

/Al

"Al Dunbar" <alandrub@newsgroup> wrote in message
news:OAsBo7HTKHA.1280@newsgroupWhile it is true that the line

cscript //nologo shutdown.vbs 1>> c:\test.txt 2>>&1

lacks a full path definition for shutdown.vbs, it would still generate the
following error message in c:\test.txt:

Input Error: Can not find script file "shutdown.vbs".

However, there is also a possibility that the OP has more than one file
called "shutdown.vbs", which emphasises the point of your argument: When
running a scheduled task then *all file names must be fully qualified*.

Pegasus [MVP] wrote:....toAdding the lines I suggested would expose the fact that the intended
shutdown.vbs was not being run, but yes, a fully qualified path would remove
doubt.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

On Oct 14, 5:43*am, "Todd Vargo" <tlva...@newsgroup> wrote:Just add this line to the batch file (first line)

cd /d "%~dp0"

francois wrote:....Read my first post again for explanation.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

"francois" <francois@newsgroup> wrote in message
news:OzCRoeRTKHA.504@newsgroupIt is perfectly OK to use the Run method under a scheduled task. Scheduled
tasks behave in exactly the same way as foreground tasks. It's only that you
cannot capture the console output from a Run command.

When trying to solve a problem, it often helps to simplify things. In order
to prove that the Run method works when scheduled, I created the following
simple script:

Set oWshShell = CreateObject("WScript.Shell")
sCmd = oWshShell.ExpandEnvironmentStrings("%comspec% /c dir c:\ >
c:\test.txt")
oWshShell.Run sCmd

I then ran it under the Task Scheduler and it worked exactly as I expected,
creating some output lines in c:\test.txt. The scheduled task looked like
so:

cscript c:\test.vbs

In an earlier reply I recommended that you should capture the output from
the Exec method. I did not respond to my suggestion. What did you see?