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

SQL
4 Comments

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) 

Maintenance Plan, SQL Error Messages, SQL Server
Previous Post
SQL SERVER – AlwaysOn Availability Groups: Script to Sync Logins Between Replicas?
Next Post
SQL SERVER – Backup to URL error: Operating system error 50(The request is not supported.)

Related Posts

4 Comments. Leave new

  • Sathiya Kumar V M
    October 15, 2018 8:53 pm

    Yes. I just cross verified it by creating two sub plans under same Maintenance Plan which is showing the error. Thanks for this info.

    Reply
  • nice ,thank you

    Reply
  • Ghullam Mohiyuddin
    April 17, 2019 8:05 am

    Sir, when i gong to connect integrated server in ms sql 2014 the error comes that server execution fail

    Reply
  • Sir – this really solves/explains nothing. Having multiple subplans in a Maintenance Plan should NOT be an issue. It is designed to handle that. We have run multiple subplans as part of a single Maintenance Plan in SQL Server 2016 for years. This is a new error for us in SQL Server 2019. Running each subplan job individually and manually does not fix the problem with the automating the backups. Have you come across any actual resolution (rather than manual work around) to the error?

    Reply

Leave a Reply