![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a dts package that is scheduled as a job. This job is created under the admin ownership. The job is failing even when I log into the server as an admin and start (execute) the job. If I execute the dts package itself it runs successfully. Any ideas why this may be? Thanks, Ninel |
#3
| |||
| |||
|
|
I have a dts package that is scheduled as a job. This job is created under the admin ownership. The job is failing even when I log into the server as an admin and start (execute) the job. If I execute the dts package itself it runs successfully. Any ideas why this may be? Thanks, Ninel |
#4
| |||
| |||
|
|
Hello ngorbunov via SQLMonster.com, Invariably this will be down to permissions. Are you logging the jobs and their steps? Try using the Operating System (CmdExec) job step to get a better description of twhat may be going on. Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com I have a dts package that is scheduled as a job. This job is created under [quoted text clipped - 6 lines] Thanks, Ninel |
#5
| |||
| |||
|
|
I'm not a dba so maybe I'm not fully understanding, but this is what I have: The dts package is saved under the admin login (itiadmin). I scheduled the job also under the admin group and when I execute this job logged in as the admin it still fails. I don't know how to log the steps. It looks like there is only one step in this job. Allan Mitchell wrote: Hello ngorbunov via SQLMonster.com, Invariably this will be down to permissions. Are you logging the jobs and their steps? Try using the Operating System (CmdExec) job step to get a better description of twhat may be going on. Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com I have a dts package that is scheduled as a job. This job is created under [quoted text clipped - 6 lines] Thanks, Ninel |
![]() |
| Thread Tools | |
| Display Modes | |
| |