Home SQL Compliance Manager SQL SERVER – Execution Failed. See the Maintenance Plan and SQL Server...

SQL SERVER – Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details

8
0
SHARE


While doing my consulting, I created a maintenance plan for my client to take full and log backups on a regular basis. The client was a little impatient, and he wanted to test everything before I get off the call. So, they tried to execute the maintenance plan which I created. It failed like below

SQL SERVER - Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details mp-subplan-err-01

When we click on a hyperlink, we see below message. Here is the text of the message.

SQL SERVER - Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details mp-subplan-err-02

Maintenance Plan ‘Full and Log Backup’ contains multiple subplans. You can execute them individually by selecting their associated jobs under the SQL Server Agent node of Object Explorer. (SqlManagerUI)

The error message appeared because I created to subplans in the same plan. Below is the screenshot when we edit the plan. As we can see Subplan_1 is for full backup and another one was for log backup.

SQL SERVER - Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details mp-subplan-err-03

WORKAROUND / SOLUTION

As mentioned in the error message, I need to use SQL Server Agent to pick the job and run the subplan which I need to run.

SQL SERVER - Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details mp-subplan-err-04

Rather than having names like Subplan_1, I prefer to rename the subplan by editing, maintenance plan to have some meaningful names. Here is what I do.

SQL SERVER - Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details mp-subplan-err-05

I hope this blog has helped you in fixing errors and a trick to get the job name little more meaningful when it’s created via maintenance plan.

Reference: Pinal Dave (https://blog.sqlauthority.com



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here