Jobs not running at all

Question

Post reply

Jobs not running at all

Viewing 12 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic. Login to reply

mannu_leo SSChasing Mays Points: 614 More actions · Answer 1

Yes,

It is started with the account who has the appropriate permissions

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 2

quote:
Its as if new
plans are not being recognized in the system but they are enabled and show up in
jobs.

Do those old plans work? Had computer name been changed?

mannu_leo SSChasing Mays Points: 614 More actions · Answer 3

Hi,

Computer name has not been changed. And there was not any job or plan earlier on this server.

But Transaction Log backup job through DB Maintenance Plan is working and if I try to run that job too manually then also it doesnt work. its working as per its scheduled time only.

homebrew01 SSC Guru Points: 55548 More actions · Answer 4

The job itself is enabled, but how about the schedule entry ? Right click the job >> Properties >> Schedules >> Edit ......... Is the enabled box checked ?

mannu_leo SSChasing Mays Points: 614 More actions · Answer 5

Yes, for sure the schedule is also enabled and the time is also correct. and moreover when i try to run it manually then too it neither gives any error nor does any thing.

mccork SSC-Insane Points: 22288 More actions · Answer 6

Anything interesting in the SQL Errorlog?

Anything in your SQL Agent Error Log? (right-click SQL Server Agent and select "Display Error Log...").

Is your maintenance plan configured to write a report file? If not, do so. Review the report file (if any) after trying to execute it.

Cheers,

- Mark

Cheers,
- Mark

mannu_leo SSChasing Mays Points: 614 More actions · Answer 7

There is nothing in the SQL Agent Error Log or Windows Log.

And I tried the Reporting file too but that file never get created. I created it myself but still its not writing anything in it. Probably the job is not running at all thats why???....

mannu_leo SSChasing Mays Points: 614 More actions · Answer 8

Yipppeeeeeeeeeeee....................

Reinstallation of SP3a has done the trick. But dont know how...

Frank Kalis SSC Guru Points: 111183 More actions · Answer 9

Nice to see you've found a solution.

...as long as it works don't ask why

Frank

http://www.insidesql.de

http://www.familienzirkus.de

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

mbenothmane Mr or Mrs. 500 Points: 525 More actions · Answer 10

quote:
I will create a new job again and check if I have the proper permission on the location of the backup files. Are you backing up on a network or local drive? How are the permission are set up on that drive?

SQLBill SSC Guru Points: 51440 More actions · Answer 11

It might have been an issue with a driver or MDAC version. Reloading SP3a probably fixed the driver/MDAC problem.

But that's just a guess....

-SQLBill

mngong SSCertifiable Points: 6167 More actions · Answer 12

Before people start proposing out of whack things like reinstall if this was a new install is there a way out yet?

Mike