Cross-Language Calls Hang... Sometimes

Sorry, this is a long one. But I've spent a long time researching it before posting :)

I started out trying to do something very simple; have an email sent to me when a trappable error occurs in cross-language call from a VBS script. Now, I can't get cross-language calls to work at all?

Here's the script:
-------------------
Sub Main()

JALScript.Execute "OnErrorStop" & vbCrLf & "RaiseError ""Err Here!"""
End Sub

Here's the Trace window results:
---------------------------------
VBS Starting script execution
JALSS JALScript Service loaded
JALSS Request Event 732, Stop Event 736, Read Pipe 740, Write Pipe 744
JALSS JALScript Service Listener started
VBS Invoking sub Main...

The job starts, but never finishes. When I try to restart 24x7, I get the warning message about spawned process.

Now it get's more strange.... If I keep running the job (5 or 6 times), eventually it will go start to finish, but only if I have the trace window available (the first 5 never finish though). Without trace, I can run it 20 times and it never finishes.

Here's an even simpler variation:
---------------------------------
Sub Main()

JALScript.Execute "LogAddMessage(""INFO"",""My Info"")"
End Sub

This one runs, BUT only if the trace window is enabled????

Also, the following script:
---------------------------
' This script shows "Hello" message
Sub Main()

MsgBox "Hello"
End Sub

is reported as having a syntax error by the debugger? Maybe related?

All the jobs are Async + Detached and I'm using Ver 3.4.7
Thanks for helping!

I'm having the smae problem!!!!

: Sorry, this is a long one. But I've spent a long time researching it before
: posting :)

: I started out trying to do something very simple; have an email sent to me
: when a trappable error occurs in cross-language call from a VBS script.
: Now, I can't get cross-language calls to work at all?

: Here's the script: -------------------
: Sub Main()

: JALScript.Execute "OnErrorStop" & vbCrLf & "RaiseError
: ""Err Here!"""
: End Sub

: Here's the Trace window results: ---------------------------------
: VBS Starting script execution
: JALSS JALScript Service loaded
: JALSS Request Event 732, Stop Event 736, Read Pipe 740, Write Pipe 744
: JALSS JALScript Service Listener started
: VBS Invoking sub Main...

: The job starts, but never finishes. When I try to restart 24x7, I get the
: warning message about spawned process.

: Now it get's more strange.... If I keep running the job (5 or 6 times),
: eventually it will go start to finish, but only if I have the trace window
: available (the first 5 never finish though). Without trace, I can run it
: 20 times and it never finishes.

: Here's an even simpler variation: ---------------------------------
: Sub Main()

: JALScript.Execute
: "LogAddMessage(""INFO"",""My
: Info"")"
: End Sub

: This one runs, BUT only if the trace window is enabled????

: Also, the following script: ---------------------------
: ' This script shows "Hello" message
: Sub Main()

: MsgBox "Hello"
: End Sub

: is reported as having a syntax error by the debugger? Maybe related?

: All the jobs are Async + Detached and I'm using Ver 3.4.7
: Thanks for helping!

Which Windows Script Host version is installed on your system?

If you are not sure check version of check the Windows\System or WinNT\System32 folder for scrrun.dll.

If you have an old version you can get the new one here http://www.microsoft.com/msdownload/vbscript/scripting.asp

: I'm having the smae problem!!!!

I'm running 5.6 on Win2K SP3

: Which Windows Script Host version is installed on your system?

: If you are not sure check version of check the Windows\System or
: WinNT\System32 folder for scrrun.dll.

: If you have an old version you can get the new one here
: http://www.microsoft.com/msdownload/vbscript/scripting.asp

Try running this job in the debug mode: from the DOS prompt run
24x7.exe /DEBUG /JOB [job id]

If you get any additional warnings or errors in the job log please let us know.

: I'm running 5.6 on Win2K SP3

Thanks for helping here....

When I ran it this way, the same thing happens.

With Trace disabled:
The job starts, I get the "start" e-mail, then it hangs. 24x7 is in the SysTray, no context menu. I had to used Task Manager to kill the process.

When trace is enabled, the same as above with this in the trace window:

COMMAND LINE >> Start job #201
VBS Starting script execution
JALSS JALScript Service loaded
JALSS Request Event 656, Stop Event 660, Read Pipe 664, Write Pipe 668
JALSS JALScript Service Listener started
VBS Invoking sub Main...

In either case the Event Log is not updated.

Here's my VBS Script (repeat from previous posting)
Sub Main()
JALScript.Execute "LogAddMessage(""INFO"",""My Info"")"
End Sub

Curious, this one ran before when trace was enabled....

: Try running this job in the debug mode: from the DOS prompt run
: 24x7.exe /DEBUG /JOB [job id]

: If you get any additional warnings or errors in the job log please let us
: know.

Mike, I don't have an answer yet, just wanted to tell you that I didn't forget... we are still looking into this issue.

: Thanks for helping here....

: When I ran it this way, the same thing happens.

: With Trace disabled: The job starts, I get the "start" e-mail, then
: it hangs. 24x7 is in the SysTray, no context menu. I had to used Task
: Manager to kill the process.

: When trace is enabled, the same as above with this in the trace window:
: COMMAND LINE >> Start job #201
: VBS Starting script execution
: JALSS JALScript Service loaded
: JALSS Request Event 656, Stop Event 660, Read Pipe 664, Write Pipe 668
: JALSS JALScript Service Listener started
: VBS Invoking sub Main...

: In either case the Event Log is not updated.

: Here's my VBS Script (repeat from previous posting)
: Sub Main()
: JALScript.Execute
: "LogAddMessage(""INFO"",""My
: Info"")"
: End Sub

: Curious, this one ran before when trace was enabled....