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 |
|
Joe Irvine
Starting Member
1 Post |
 Posted - 2004-09-15 : 09:50:43
|
| Here is my setup:2 SQL 2000 servers, Server1 is a Domain member, Server2 is isolated behind a firewall and is not. Server2 has a DTS package set up to copy tables from a database to Server1. When I execute the package manually it succeeds. When I execute it as a job (created by the schedule option in DTS) it fails. I am sure it is a permissions problem but cannot find the solution. the DTS package is set up with SQL logins to both databases and works. Server2 cannot be jooined to the domain for security reasons. Any help would be appreciated. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-09-15 : 14:19:03
|
| The most likely cause of your problem is the account being used for the SQL services. When a DTS package is scheduled, it uses that account. So if the account doesn't have access to anything inside the DTS package like mapped network drives, UNC paths, etc..., then it'll fail. The other reason you might be having problems is that the package runs from the database server when scheduled and not from your client machine. So any files or paths inside the DTS package must be valid on the database server. For instance, if you are referring to C:\test.txt, then that file must be on the C drive of the database server. What I do to make sure the package will work when scheduled is after I am done developing it, I log onto the database user using the SQL service account. Then I manually test it via the execute option. Any errors found there need to be resolved before it'll ever work scheduled.Tara |
 |
|
|
|
|
|
DTS failing from scheduler