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 |
|
pazzy11
Posting Yak Master
145 Posts |
 Posted - 2008-02-08 : 04:19:26
|
| HiI have a strange scheduling problem.I have a job, i test it through BIDS - WorksI test it through SSMS - worksI run the job - WorksI schedule for a run time job - WorksI schedule for a recurring job - WorksHowever (here is the really annoying part) it fails to run at the night run (11.20PM)there are 6 other packages that run fine after it , 11.30 , 1AM .. 4 AM etc ...Solast night I changed the package to run at a later time, and it worked, but the other package thatran 2nd (which now ran 1st) failed !!its almost as if the 1st package has to fail !!!!!When i look at the history and detailed log all it says is "The step Failed"anyway , I can set up a workaround by starting a dummy job that is supposed to fail..FYI the jobs are run under administrator and they are protected by a password (encryptSensitiveWithpassword) . |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2008-02-08 : 04:21:53
|
| Just so I can be clear, if you execute any of those jobs separately , they all work?Jack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
 |
|
|
pazzy11
Posting Yak Master
145 Posts |
Posted - 2008-02-08 : 05:32:58
|
| yes they all work separately. |
|
|
|
Qualis
Posting Yak Master
145 Posts |
Posted - 2008-02-08 : 09:05:15
|
| My suggestion would be to set up logging in your package. Turn on the OnError event and let it run and look at the log to see why. |
|
|
|
|
|
|
SSIS scheduling jobs