Windows 2000 SP2
24x7 automation Suite 3.0.5

I have a script a couple of jobs that I wrote in VBscript instead of JAL just for testing purposes. The scripts run correctly. The problem is that is I try to run the scripts using the debugger I get the following error messages.

(1) If I don't put in any break points the script runs and after the last line is executed I get the following message box:

24x7 VBScript Debugger
Syntax errors found in the Script. Debugger Halted!
Run this job in the Run Now mode to find out which line has a syntax error

As I stated above when you run the job in the Run Now mode it just works without any errors.

(2) If I have a database connection in the VBScript and attempt to STEP INTO the line to create the connection object: Set db_conn = CreateObject("ADODB.Connection") the server pegs at 100% utilization.

(3) Sometimes after getting these errors the scheduler will just quit. I think that is probably just because the previous error wacked something.

John

Turn on the tracing feature (Tools/Options/Log/Trace enabled). Some additional information may be written by the debugger to the trace window. This may help to find out what is going on before that "Debugger Halted" message is displayed.

: Windows 2000 SP2
: 24x7 automation Suite 3.0.5

: I have a script a couple of jobs that I wrote in VBscript instead of JAL just
: for testing purposes. The scripts run correctly. The problem is that is I
: try to run the scripts using the debugger I get the following error
: messages.

: (1) If I don't put in any break points the script runs and after the last
: line is executed I get the following message box: 24x7 VBScript Debugger
: Syntax errors found in the Script. Debugger Halted!
: Run this job in the Run Now mode to find out which line has a syntax error

: As I stated above when you run the job in the Run Now mode it just works
: without any errors.

: (2) If I have a database connection in the VBScript and attempt to STEP INTO
: the line to create the connection object: Set db_conn =
: CreateObject("ADODB.Connection") the server pegs at 100%
: utilization.

: (3) Sometimes after getting these errors the scheduler will just quit. I
: think that is probably just because the previous error wacked something.

: John

Turned on TRACE and now the debugger just blows up at the end.

Script Log: VBS Starting script execution in Debug mode ...

VBS Resuming script execution in debug mode ...

The Following error dialog is displayed:

24x7.EXE - Application Error

The instruction at "0x0bae1efc" referenced memory at "0x00000000". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

I clicked CANCEL:

0BAE1EF0 push ecx
0BAE1EF1 mov eax,[0BAFE764]
0BAE1EF6 lea edx,[esp]
0BAE1EFA push edx
0BAE1EFB push eax
0BAE1EFC mov ecx,dword ptr [eax]
0BAE1EFE call dword ptr [ecx+10h]
0BAE1F01 mov edx,dword ptr ds:[0BAFE764h]
0BAE1F07 push 2
0BAE1F09 mov eax,dword ptr [esp+4]
0BAE1F0D push 1
0BAE1F0F push edx
0BAE1F10 push eax
0BAE1F11 mov ecx,dword ptr [eax]
0BAE1F13 call dword ptr [ecx+0Ch]
0BAE1F16 mov eax,dword ptr [esp]
0BAE1F1A push eax
0BAE1F1B mov ecx,dword ptr [eax]
0BAE1F1D call dword ptr [ecx+8]
0BAE1F20 mov eax,1
0BAE1F25 pop ecx

Debugger appeard to indicate the problem was in the 24x7ad.dll file.

John

Hello again,

I tried reinstalling the software, that actually does help sometimes, but it didn't in this case.

I then attempted to run the Excel Automation script from the VBScript Examples that are supplied with the Example Jobs Database.

I didn't blowup the EXE but I did get the debugger halted error message.

(1) The job log shows the job started but there is no finish
(2) The Script logs only shows the following with TRACE on:

VBS Starting script execution in debug mode...

VBS Script execution finished

JALSS JALScript Service Listener stopped

JALSS JALScript Service unloaded

John

Which version of IE Explorer do you have?
Have you recently installed a new IE version (MSN, 6.0 ,etc...) or any other software that directly supports VBScript?

From the trace, it looks like the debugging session was abnormally aborted and the debugger was in a process of unloading VBScript engine when it blew up. The session was possible aborted because the debugger reached the line past the last line in the script main procedure and it didn't get a notice from the script engine that the screen is completed. This could be caused by various incompatibility issues. That's why I asked what was recently installed on your system.

PS. 24x7ad.dll is the VBScript Active Debugger implementation.

: Hello again,

: I tried reinstalling the software, that actually does help sometimes, but it
: didn't in this case.

: I then attempted to run the Excel Automation script from the VBScript
: Examples that are supplied with the Example Jobs Database.

: I didn't blowup the EXE but I did get the debugger halted error message.

: (1) The job log shows the job started but there is no finish
: (2) The Script logs only shows the following with TRACE on: VBS Starting
: script execution in debug mode...

: VBS Script execution finished

: JALSS JALScript Service Listener stopped

: JALSS JALScript Service unloaded

: John

IE Version 5.00.3315.1000

The computer that I am running this on has MS Visual Studio 6.0 Enterprise Edition on it. Also Office 97 has Visual Basic for Applications support.

I really can't think of anything else that does VBScript on this particular computer.

John

: Which version of IE Explorer do you have?
: Have you recently installed a new IE version (MSN, 6.0 ,etc...) or any other
: software that directly supports VBScript?

Can you check using Visual Studio or any Office application (insert OLE object) which version of MS Script Control you have on your computer)?

: IE Version 5.00.3315.1000

: The computer that I am running this on has MS Visual Studio 6.0 Enterprise
: Edition on it. Also Office 97 has Visual Basic for Applications support.

: I really can't think of anything else that does VBScript on this particular
: computer.

: John