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 |
|
cannonier
Starting Member
4 Posts |
 Posted - 2007-04-19 : 07:05:42
|
| I'm hoping that someone has experienced this problem before and knows how to get round it.The problem we are having is that we have a job that is scheduled to run at 4:00 am each morning, for the past 6 weeks it has done this with no problem. However, this morning it failed. we know it failed because it didn't produce the results it was supposed to. However the monitor said that the job had completed successfully. On examining the history of the job we found that the job was still running!!! When we tried to stop the job by right clicking and selecting the appropriate action. The action available to us was to start the job. After arguing for a bit we decided to try and run the job again. We did this and found that the job running in the history screen terminated with an error and than ran and completed successfully.Confused? So are we any ideas or solutions gratefully received |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-19 : 09:53:22
|
| What's the error in job history? What does the job do? Did you check blocking? |
 |
|
|
cannonier
Starting Member
4 Posts |
Posted - 2007-04-19 : 10:43:30
|
| This is the error message that appeared after the job was restarted "Executed as user: MOTHERCARE\SQLUsr. The package execution failed." We did a check for blocking at the time and found nothing. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-19 : 17:04:30
|
| Enable package logging, you'll get more details next time. |
|
|
|
|
|
|
SQL Server Agent - Job Activity Monitor