March 20, 2009 at 2:52 pm
The Maintenance plans i was using for backups was running fine till yesterday.
Yesterday night we moved the server from one data center to another physically and started the services.
Since then the maintenance plans are failing.
Actually the view history tab of maintenance plan does not show anything. the error is shown in SQL server jobs only. i think the job is not able to go to maintenance plan.
Here is the error.
Executed as user: Domain\devsqlservice. his task is "Maintenance Plan Reporting Task; Microsoft Corporation; Microsoft SQL Server v9; ? 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1". End Error Error: 2009-03-20 16:42:23.56 Code: 0xC0024107 Source: Reporting Task for subplan-{587BE1DE-326E-4A79-B159-9B0A65E70316} Description: There were errors during task validation. End Error Error: 2009-03-20 16:42:23.56 Code: 0xC0010025 Source: TLog_Backup Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:42:07 PM Finished: 4:42:23 PM Elapsed: 15.61 seconds. The package execution failed. The step failed.
Please let me know if you need more info...
March 21, 2009 at 1:34 am
First plz clarify whether the server is moved to different domain and secondly check whether the maintenance plan still exists
March 21, 2009 at 9:34 pm
i have checked the domain and the maintenance plans.
Domain is same and the maintenanace plans exists.
other SQL server jobs are working fine but the backup subplans created during the creation of maintenance plans are failing.
i tried to create a sql job which takes the backup of all databases but i is also failing.
March 22, 2009 at 2:33 pm
Did you change the server name?
Do you backup to a network share that is no longer available?
Can you open the maintenance plans and verify the connection and setup for each plan?
One thing you can try is dropping the server and adding it back in:
Execute sp_dropserver 'your instance name';
Execute sp_addserver 'your instance name', 'local';
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
March 22, 2009 at 3:16 pm
Can you set up logging for the maint plan and capture a text file log? It should have more info in there.
March 23, 2009 at 2:42 pm
Double check the recovery mode of the database. The output states the TLOG portion failed - if the database is in 'simple' recovery mode that could explain it.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
March 31, 2009 at 2:49 pm
it is not working for any of the maintenance plans that we set up...
i have created the sql agent jobs instead of maintenance plans and they are running fine.
I think the problem is with SSIS packages that will be created at the time of maintenance plans.
November 16, 2009 at 9:24 am
Jeffrey Williams-493691 (3/22/2009)
Did you change the server name?Do you backup to a network share that is no longer available?
Can you open the maintenance plans and verify the connection and setup for each plan?
One thing you can try is dropping the server and adding it back in:
Execute sp_dropserver 'your instance name';
Execute sp_addserver 'your instance name', 'local';
how to run this
May 16, 2011 at 1:43 am
After changing Simple to Full you need to have a fresh backup.
February 3, 2012 at 8:17 am
Answer to a very old problem..I know.
But I got into this situation when we changed our server.
The maintenance plans are SSIS packages stored in the Package Store of your server.
Once you upgrade your server and export your packages, the XML for the package wont get changed automatically and SSMS doesnt have any way of making that change for you.
Hence you will need to change the XML itself. Please use the script found at
http://msdn.microsoft.com/en-us/library/ms143799(v=sql.90).aspx (Scroll to the comments section..some good fella provided the script in there).
This script works perfectly fine and you will be able to see the changes being made. Good Luck to anyone facing the same issue.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply