February 26, 2007 at 9:23 am
Environment:
Windows 2003
SQL 2005 Standard Edition, RTM
I have a maintenance plan that includes 2 steps, backups and integrity checks. The job has a 2nd step that does file cleanup.
When this job is run, it succeeds, but nothing happens.
Any idea what might be wrong?
February 26, 2007 at 10:50 am
Anders,
first of all you should check the logfile to see what has been done and what hasn't. Second I know there was an issue with file cleanup in the RTM version. Basically files in a subfolder where not removed.
Markus
[font="Verdana"]Markus Bohse[/font]
February 26, 2007 at 11:28 am
It doesn't even create a log file, for either of the steps.
The cleanup job is basically 5 individual cleanup items for the 5 databases I want to clean up, the rest are small so didn't bother.
It's all really strange. I suspect it has something to do with us changing the domain the server (and SQL) is running under as we did that last weekend. But it ran succesfully until Friday morning. I at that time dropped the Maintenance plan, and the job, then completely recreated it. It ran succesfully at that time. Then failed to do anything again this morning.
For now I have gotten around it by making my own T-SQL maintenance plan that will do what I need.
February 27, 2007 at 4:39 pm
Not sure if you have tried this earlier.
Can you please check history of "Maintenance Plan" (NOT job) and see if something is alarming there?
February 28, 2007 at 5:36 am
It showed nothing either. I mean, absolutely nothing. Which indicates to me that the call to run the maintenance plan actualy never executed it, I would think....
February 28, 2007 at 9:02 am
R u backing these to local disk or external storage device. If external check for permissions...just a guess
February 28, 2007 at 9:08 am
Nah these are all local jobs, run off local packages on the server to local hard drives.
I do belive it has something to do with the domain change for the server, but that doesn't explain why they would have worked earlier in the week after the domain change, but then suddenly quit. I can even create a brand new maintenance plan and have the same happen. I even remote controlled into the server to create and do all maintenance on just to make sure it wasn't my locel SSMS causing a problem since it is on SP1. Still same problem.
As I said though, for now I have created my own backup and cleanup procs that handle it fine. Will retry using the maintenance plan after I get the server up to SP2 (currenlty in internal testing).
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply