Job having Pre/Post command of which command was written in VBScript may fail
Article ID: 100000902
Updated On:
Description
Error Message
0xe0081d1 - The job did not start.
V-79-57344-33233
Error: Could not start Pre Job Command
Error (193) : [FILE NAME] is not a valid Win32 application.
Error: Could not start Post Job Command
Error (193) : (null) is not a valid Win32 application.
Resolution
If Pre/Post command which was written in VBScript is specified in Job, the Job may fail even if the VBScript command had completed successfully. (Figure 1)
Figure 1
Cause:
The completion status of VBScript Pre/Post command can be retrieved only from the script engine.
If the Pre/Post command does not have the script engine specified, however, the return status is not able to be retrieved.
Workaround:
Specify the script engine along with the script itself. VBScript command will be executed with wscript.exe or cscript.exe. (Figure 2)
With this way, VBScript Pre/Post command would work successfully. (Figure 3)
Figure 2
Figure 3
Figure 1
Cause:
The completion status of VBScript Pre/Post command can be retrieved only from the script engine.
If the Pre/Post command does not have the script engine specified, however, the return status is not able to be retrieved.
Workaround:
Specify the script engine along with the script itself. VBScript command will be executed with wscript.exe or cscript.exe. (Figure 2)
With this way, VBScript Pre/Post command would work successfully. (Figure 3)
Figure 2
Figure 3
Issue/Introduction
Job having Pre/Post command of which command was written in VBScript may fail
Was this article helpful?
Yes
No
Powered by
