Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jones_d
Yak Posting Veteran
61 Posts |
 Posted - 2004-09-29 : 05:32:21
|
| Hi,I am setting up a job in SQL 2000 to run a VB program on a remote server. When setting up the job step I set the type to "Operating System Command CmdExec" and I entered in the path to the executable file in the command box. This file is on a network share (e.g. \\sqltest\Db_technology\figapp\figapp.exe )Is this the correct way to setup a job to run on a remote server? This doesn't work for me.The user that is running the job also has full access to the directories where figapp.exe is located.Any ideas or suggestion would be much appreciated.Thanks |
|
|
schuhtl
Posting Yak Master
102 Posts |
Posted - 2004-09-29 : 08:44:14
|
| How do you have your Startup Service Account configured, System Account or an account that has domain privlages? If your Sql Server is running under the System Account the job will not be able to access anything outside of the local server (no network privlages). Once you have confirmed that sql server is running under a domain account and that account has proper access to network share that contains the executable, try this.exec master.dbo.xp_cmdshell '\\sqltest\Db_technology\figapp\figapp.exe'I use the syntax above to execute batch files on remote servers. Should work the same? |
 |
|
|
|
|
|
Scheduling a job on a remote server