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 |
|
mdhingra01
Posting Yak Master
179 Posts |
 Posted - 2004-08-12 : 13:20:29
|
| Does anyone know why I am able to run a DTS package manually, but when I schedule it as a job in EM, it doesn't execute.The package zips a backup of a database and places it on a mapped drive. Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-12 : 13:32:27
|
| When a job runs, it uses the context of the database server. So any files or drive mappings or anything else must exist on the database server. Also the job runs under the SQLSERVERAGENT service account, so if it needs to connect to a file on a share on the network, then that account needs access. Local System Account for that service is not enough when accessing network files.Tara |
 |
|
|
mdhingra01
Posting Yak Master
179 Posts |
Posted - 2004-08-12 : 15:49:04
|
| SQLSERVERAGENT is currently using LocalSystem account and password. In order to have SQLSERVERAGENT access the remote server:1. I set up a new Account on the remote server called SQLSERVERAGENT and assign a password2. I share out the folder I want SQLSERVERAGENT to access and provide rights accordinly to the new user I set up.3. I set up a new user on the local server called SQLSERVERAGENT and assign the same password4. I change the logon username and password in the SQLSERVERAGENT Service to be the new accoutn I set up on local and remote machines.5. I restart the service for the changes to take effect5. Now when I execute the job, it should be using the SQLSERVERAGENT account to process the job not the LocalSystem account and it should be able to connect to the remote server because the account was set up there with appropriate rights and security on the folder.Is that all, because this still doesn't work.Thanks |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-12 : 15:55:22
|
| You need to use domain users for the services. The domain user would also have local admin privileges. You should also change the MSSQLSERVER account to use this account as well. The same account should be used on all SQL Servers.Tara |
|
|
|
|
|
|
Scheduling a package...doesn't work