I'm using v 3.4.24 of 24x7 scheduler
I have a script that starts MS Access and runs a macro.
The script starts ok, but doesn't complete.
I see the following message in the log file.
Processing error 21
VBScript error# -2147418110
Line in script 23
Error:

Line 23 is the line in which the macro is run (runmacro)

Here's part of the script. The database table is being accessed
from a mapped drive.

Set A = CreateObject("Access.Application")
A.Visible = true
A.OpenCurrentDatabase "I:\Databases\database1.mdb"
A.Visible = true
A.docmd.runmacro "DailyTableUpdate"
Set a=nothing

What could be causing the error? Is there documentation on
what the "processing error 21" refers to?

I am not sure if text case matters but try using DoCmd instead of docmd. Error 21 usually indicates "unknown command"

: I'm using v 3.4.24 of 24x7 scheduler
: I have a script that starts MS Access and runs a macro.
: The script starts ok, but doesn't complete.
: I see the following message in the log file.
: Processing error 21
: VBScript error# -2147418110
: Line in script 23
: Error: Line 23 is the line in which the macro is run (runmacro)

: Here's part of the script. The database table is being accessed
: from a mapped drive.

: Set A = CreateObject("Access.Application")
: A.Visible = true
: A.OpenCurrentDatabase "I:\Databases\database1.mdb"
: A.Visible = true
: A.docmd.runmacro "DailyTableUpdate"
: Set a=nothing

: What could be causing the error? Is there documentation on
: what the "processing error 21" refers to?

The jobs have run successfully in the past, but I will make the change as you suggest.

Thanks

: I am not sure if text case matters but try using DoCmd instead of docmd.
: Error 21 usually indicates "unknown command"

The error is still there, as stated in the orignal post. The "docmd" was changed as suggested, with no improvement.

Reference:
I'm using v 3.4.24 of 24x7 scheduler
I have a script that starts MS Access and runs a macro.
The script starts ok, but doesn't complete.
I see the following message in the log file.
Processing error 21
VBScript error# -2147418110
Line in script 23
Error:

Line 23 is the line in which the macro is run (runmacro)

Thanks for any help,
John
---------------------------------------
: The jobs have run successfully in the past, but I will make the change as you
: suggest.

: Thanks

Can you run this script from command line as a .VBS file?

If you haven't tried it yet save the script as myscript.vbs file using File/Export menu in 24x7 Editor then remove Sub Main() and End Sub lines from the file. Run the resulting file DOS prompt using "start myscript.vbs" command. Let us know what happens.

: The error is still there, as stated in the orignal post. The
: "docmd" was changed as suggested, with no improvement.

: Reference: I'm using v 3.4.24 of 24x7 scheduler
: I have a script that starts MS Access and runs a macro.
: The script starts ok, but doesn't complete.
: I see the following message in the log file.
: Processing error 21
: VBScript error# -2147418110
: Line in script 23
: Error: Line 23 is the line in which the macro is run (runmacro)

: Thanks for any help,
: John
: ---------------------------------------

Sysop,

No, had not tried that yet. Created the VBS script and ran it as suggested.
The script ran with no problems.

The job is still being disabled when run by 24x7.
Processing error # 21
VBS error # -2147418110

Regards,
John

: Can you run this script from command line as a .VBS file?

: If you haven't tried it yet save the script as myscript.vbs file using
: File/Export menu in 24x7 Editor then remove Sub Main() and End Sub lines
: from the file. Run the resulting file DOS prompt using "start
: myscript.vbs" command. Let us know what happens.

That's really strange. Let's check a few things
1. Did you use the same user account to run the job and the script from DOS?
2. Do you get this error when running job (not the VBS script) from command line as "24x7.exe /JOB job_id_here"?
3. Can you add some error checking in the "DailyTableUpdate" macro and make it log the macro start/finish events and also completion statuses after each internal operation?

I guess that some error occurs during this macro run, which is reported back to 24x7 and in 24x7 in turn terminates the process. When started from a VBS file the macro continues to run after an error and that's why it seems works because the error is ignored.

PS. To set the scheduler not to disable a job after any error, uncheck the "Disable on error" job property.

: Sysop,

: No, had not tried that yet. Created the VBS script and ran it as suggested.
: The script ran with no problems.

: The job is still being disabled when run by 24x7.
: Processing error # 21
: VBS error # -2147418110

: Regards,
: John

: The error is still there, as stated in the orignal post. The
: "docmd" was changed as suggested, with no improvement.

: Reference: I'm using v 3.4.24 of 24x7 scheduler
: I have a script that starts MS Access and runs a macro.
: The script starts ok, but doesn't complete.
: I see the following message in the log file.
: Processing error 21
: VBScript error# -2147418110
: Line in script 23
: Error: Line 23 is the line in which the macro is run (runmacro)

: Thanks for any help,
: John
: ---------------------------------------