I have a VB Script that hangs with the following error:
"An error occurred while executing automation script: Line 2: Bad number of arguments."
Line 2 of my script is a comment line, if I ignore comment lines, line 2 is a Dim statement.
Does this error message indicate something supposedly wrong in my code, or is it some 24 x 7 error? My code runs fine under version 3.4.5. This particular script is running 20 Crystal Reports. I am currently running it Synchronous/"Attached".

Your have an error in your script. The VBScript engine reports line 2 as the error place and "Bad number of arguments" as the error message. 24x7 simply passes this information back to you and writes it to the job log.

Please note line that "2" is the line number within the procedure or function that errors out. It is not the line from the beginning of the script.

: I have a VB Script that hangs with the following error: "An error
: occurred while executing automation script: Line 2: Bad number of
: arguments."
: Line 2 of my script is a comment line, if I ignore comment lines, line 2 is a
: Dim statement.
: Does this error message indicate something supposedly wrong in my code, or is
: it some 24 x 7 error? My code runs fine under version 3.4.5. This
: particular script is running 20 Crystal Reports. I am currently running it
: Synchronous/"Attached".

Curiouser and curiouser. When I try the debugger on my script on the version 3.4.9 installation, every line of *every* script is giving the following message:
"Breakpoint line must contain an executable statement."
Yet, I can run the scripts. (except for the one mentioned in the message below.) All of the scripts are hilighting commands in the expected way, and yet the debug feature is telling me none of the commands are "executable statements."
I tried the debugger on my version 3.4.5 installation and it works fine with these *same* scripts.

What's the deal?

: Your have an error in your script. The VBScript engine reports line 2 as the
: error place and "Bad number of arguments" as the error message.
: 24x7 simply passes this information back to you and writes it to the job
: log.

: Please note line that "2" is the line number within the procedure
: or function that errors out. It is not the line from the beginning of the
: script.

This sounds as a side effect of some other problems, perhaps a VbScript debug DLL cannot be found?
Did you install 3.4.9 into a different directory by any chance or you are using 2 different computers?

If you are using 2 different computers make sure you restarted 3.4.9 computer after the installation.

Or you

: Curiouser and curiouser. When I try the debugger on my script on the version
: 3.4.9 installation, every line of *every* script is giving the following
: message: "Breakpoint line must contain an executable statement."
: Yet, I can run the scripts. (except for the one mentioned in the message
: below.) All of the scripts are hilighting commands in the expected way,
: and yet the debug feature is telling me none of the commands are
: "executable statements."
: I tried the debugger on my version 3.4.5 installation and it works fine with
: these *same* scripts.

: What's the deal?