VB Scripts not Working with 3.4.8?

Having upgraded to version 3.4.8 to take advantage of the @V macro changes, I've discovered that I can no longer run any VB scripts. I tried the following script

Sub Main

MsgBox "Hello"
End Sub

The Trace window shows:
VBS Starting script execution
JALSS JALScript Service loaded
JALSS Request Event 656, Stop Event 660, Read Pipe 664, Write Pipe 668
JALSS JALScript Service unloaded

and the dialog pops up with "Running ... Waiting for process to exit"

At this point I have to Kill 24x7. It doesn't matter if I run the job using "Run Now" or scheduled.

My system is as follows:
24x7 - v3.4.8
Win2K Server SP3
VB Script - 5.6

Thanks

I have some more (useful?) info. I remember about running with /DEBUG. Here's the error:

"Internal Error #35/88 occurred in wsh/wsh while executing execute
Error: Error calling external object function init
Call Technical Support."

after I press OK I get
"Internal Error #21/88 occurred in wsh/wsh while executing execute
Error: Bad runtime function reference
Call Technical Support."

then
"Internal Error #21/73 occurred in q_processor/q_processor while executing runjob
Error: Bad runtime function reference
Call Technical Support."

Mike

: Having upgraded to version 3.4.8 to take advantage of the @V macro changes,
: I've discovered that I can no longer run any VB scripts. I tried the
: following script

: Sub Main

: MsgBox "Hello"
: End Sub

: The Trace window shows: VBS Starting script execution
: JALSS JALScript Service loaded
: JALSS Request Event 656, Stop Event 660, Read Pipe 664, Write Pipe 668
: JALSS JALScript Service unloaded

: and the dialog pops up with "Running ... Waiting for process to
: exit"

: At this point I have to Kill 24x7. It doesn't matter if I run the job using
: "Run Now" or scheduled.

: My system is as follows: 24x7 - v3.4.8
: Win2K Server SP3
: VB Script - 5.6

: Thanks

Please run the full setup program. If this "Bad runtime function reference" error appear again please contact support@softtreetech.com to open a case.

: I have some more (useful?) info. I remember about running with /DEBUG. Here's
: the error: "Internal Error #35/88 occurred in wsh/wsh while executing
: execute
: Error: Error calling external object function init
: Call Technical Support."

: after I press OK I get
: "Internal Error #21/88 occurred in wsh/wsh while executing execute
: Error: Bad runtime function reference
: Call Technical Support."

: then
: "Internal Error #21/73 occurred in q_processor/q_processor while
: executing runjob
: Error: Bad runtime function reference
: Call Technical Support."

: Mike

That worked.

Thank you

: Please run the full setup program. If this "Bad runtime function
: reference" error appear again please contact support@softtreetech.com
: to open a case.