![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We have a dts that has been running for months. Now it won't run - it doesn't even start. Nothing in the logs. And if we try and create a new job from the package, it won't run either. We can't even run it manually. Also when we create a new dts that runs fine when executed as a dts, it won't run as a job. The time never shows up in the "next run date" column and it doesn't run. However, we have other jobs that run every half hour or hour throughout the day and they are still running. Any ideas? Thanks, |
#3
| |||
| |||
|
|
As a first guess, I'd look into whether the security settings that the job runs under have been changed. Dan D. wrote: We have a dts that has been running for months. Now it won't run - it doesn't even start. Nothing in the logs. And if we try and create a new job from the package, it won't run either. We can't even run it manually. Also when we create a new dts that runs fine when executed as a dts, it won't run as a job. The time never shows up in the "next run date" column and it doesn't run. However, we have other jobs that run every half hour or hour throughout the day and they are still running. Any ideas? Thanks, |
![]() |
| Thread Tools | |
| Display Modes | |
| |