Error when using DatabaseConnect from Remote Control

We are using version 3.4.26 and have set up 24x7 to run as a service on our server. Using Remote Control, I set up a job that should connect to a database using DatabaseConnect. The job works correctly when I run it using the Master scheduler on the server; however, when I run it overnight using 24x7 as a service the job fails stating that I'm passing a 'bad number of arguments' on the DatabaseConnect line.

When I debug through the Remote Control I get the same error when it tries to connect to the database, even though I choose to run the job Remotely, not locally. Is there a way to get around this remotely?

The problem description is kind of contradictive. Can you provide a trace file for the job run so we can see what the job is doing in run-time? Please let me know if you need help with turning on the trace.

I figured it out, thanks. Even though the log says it fails on line 13 which is the DatabaseConnect line, the script.log on the server showed the actual error message had to do with the next line which was a FileReadAll line with an incorrect path.