| Author |
Topic |
|
wilso_s
Starting Member
10 Posts |
 Posted - 2003-05-30 : 14:17:46
|
| when running sp_start_job it says it started the job successfully but the job doesn't start. Can't start the job from enterprise manager either. Also can't disable an enabled job. Jobs which have been created and scheduled (prior to 4 weeks ago) still run on schedule. Can create new jobs but they don't run on command or when scheduled. No error messages. Have full adminstrative rights. Ran DBCC CheckDB on MSDB. |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-05-30 : 14:35:43
|
| $1000.00 says the job is not enabled.Do you see anything in History?Brett8-) |
 |
|
|
wilso_s
Starting Member
10 Posts |
Posted - 2003-05-30 : 14:54:28
|
| The job(s) is enabled. There are scheduled jobs which were created 4 weeks prior which do run on schedule successfully. However, we cannot manually run those jobs at command. We can change the schedule say from 5 days to 1 day but the jobs still run on all 5 days. Right click on the job... start... but doesn't run. Exec sp_start_job and it says it started succesfully but it didn't run. |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-05-30 : 15:00:05
|
| That was a quick "thou..."What does the job history show in EM?What does the job do that you know it didn't run?Brett8-) |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-05-30 : 15:07:02
|
| Look at sysjobs, sysjobservers and sysjobsteps to see if the entries are ok.See if there is anything in sysjobhistory.I assume you have restarted the server.Create a job with select 1 in a step and try that.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
ValterBorges
Master Smack Fu Yak Hacker
1429 Posts |
Posted - 2003-05-30 : 15:09:23
|
| My try,Is it a job scheduled to run a dts package and if so is the dtsrun command using an encrypted string?What are the job commands under job-->properties-->steps-->edit |
|
|
|
wilso_s
Starting Member
10 Posts |
Posted - 2003-05-30 : 15:10:12
|
| The job has no history. It is for backing up transaction logs.Actually, I have 2 jobs which are the same, other than the name.Job1 which was created over a year ago and scheduled to run every 15 mins. Always runs on sched and is succesful. I see the dumps on the filesystem. I wanted to change this ocurance to run every 1 hour instead. I updated the sched to 1 hour intervals, applied it and saved it. It still runs every 15 min as before but the schedule shows it schedule for 1 hour. It's on its own behavior. Can't controll it. Can't stop it. Can't disable it. Can't start it. Job2 which is the same as job1 is there, enabled. (no schedule) can start it via EM or sp_start_job, but sp_start_job reports success, but no dumps on the filesystem.This is for any type of job. |
|
|
|
wilso_s
Starting Member
10 Posts |
Posted - 2003-05-30 : 15:20:29
|
| sysjobs, sysjobservers and sysjobsteps look normal to me.created new job TEST with step = select 1 and still no success.sp_start_job still reports job started succesfully.I profiled the sp_Start_job in profiler all the way to the point where it issued the last statement of RAISERROR(14243, 0, 1, @job_name) which is the message for success. |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2003-06-02 : 11:15:37
|
| A little info on sp_start_job for you. It is reporting that is sucessfully started the job you asked it to. It doesn't care what happens after that. I think the only way sp_start_job will fail is if you give it an invalid job name. If I had to guess right now, I'd say that it sounds like the SQL Agent Service isn't running. Other than that stab in the dark, you're going to need to tell us more about the jobs that seem to be running on their own schedule. How were they created? Are they a part of a maintenance plan? Has anything changed on the server such as the server name?Jeff Banschbach, MCDBA |
|
|
|
wilso_s
Starting Member
10 Posts |
Posted - 2003-06-02 : 14:43:07
|
| Problem went away after stopping and starting the sqlagent with out a reboot. Still don't know what has caused this. Domain account which serves this agent was not locked out. Passwords were ok. In fact, I know the agent was running because services indicated so and the fact that the scheduled jobs were running with success. All I can think of is that something with the executable was corrupt.strange problem, hope it doesn't ocur again. |
|
|
|
|
JOBS