You are running the command w/ 0 args. The command takes more than 0 args.
I figured out what the issue was - I didn't have the job path in double quotes, so the command was taking a lot more arguments than what it expected.
The part that got me confused - if I was to run any other commands with inappropriate number of arguments, I get error message like this: expected : 6 received : 0
However, for NSHScriptJob createNSHScriptJob, it will produce error like this: Could not find any instance of command "NSHScriptJob,createNSHScriptJob" with expected number of arguments: 8
That's why I ran NSHScriptJob createNSHScriptJob for a test and gave me the error message in the original post.
The quick glance at the error output made me think the command was not available for some reason.
1 of 1 people found this helpful
If there are multiple versions of the command i think you will get the error you saw for the createNSHScriptJob. If there is only one version you would get the expected n received z
I didn't know that. Good to know!