I am trying to schedule a scpg3 batch file that runs fine when run manually. Scheduling tool is SQL server. batch file looks like this; scpg3 user@remoteserver:program/ftp/filename.txt E:destloc
This works 100% when run manually from command prompt, using a passphrase-less key, but when scheduled to run under the same credentials produces error 'Could not connect to broker'
asked Jun 10 '11 at 13:58
Under what user account is the SQL job running as? If it's running as the SYSTEM account it might be failing because the SYSTEM account is unable to start Tectia Broker. That is not currently supported.
One alternative is to configure your SQL job to run as a regular user account. I'm not that familiar with SQL Server scheduling so I don't know if it supports running scripts under specific Windows user accounts. If not, you might be able to get around this using "runas" or some other third party tool that allows you start a process as another user.
answered Jun 15 '11 at 15:41