6
votes

Currently, WScript pops up message box when there is a script error. These scripts are called by other processes, and are ran on a server, so there is nobody to dismiss the error box.

What I'd like is for the error message to be dumped to STDOUT, and execution to return the calling process. Popping as a MSGBox just hangs the entire thing.

Ideas?

6

6 Answers

4
votes

This is how you should be running Script batch jobs:

cscript //b scriptname.vbs
2
votes

Don't use WScript; use CScript. At the Windows command prompt, type the following to display help.

cscript //?
cscript //H:CScript

You will also need to add some sort of error handling to keep the script from terminating on an error. In Visual Basic Scripting Edition, the easiest thing to do if you just want to ignore errors is to add the following to the top of your script.

On Error Resume Next
http://msdn.microsoft.com/en-us/library/53f3k80h(VS.85).aspx
1
votes

Use WScript.Echo instead of MsgBox. And also run the script using Cscript instead of Wscript.

0
votes

You haven't stated what language you're using. If you're using VBScript, you can write an error handler using the On Error... statement. If you're using JScript, you can use a try {} catch (x) {} block.

0
votes

I suggest you put your script code in a Sub - e.g. DoWork - and code your script something like:

On Error Resume Next

DoWork

If Err.Number <> 0 Then

    If "CSCRIPT.EXE" = UCase( Right( WScript.Fullname, 11 ) ) Then
        WScript.StdErr.Write Err.Number & ": " & Err.Description
    Else
        WScript.Echo Err.Number & ": " & Err.Description
    End If
    WScript.Quit 1
End If

Private Sub DoWork

    ... your code ...

End Sub

In this way, when you run your script using cscript //b, and it fails, you'll get an error message output to stderr and the caller will receive a non-zero errorlevel.

0
votes

don't do this:

vbscript: On error resume next

english: "when you have an error, ignore it & just keep going".