Maintenance Plans Execution Failure

Question

I'm using SQL Server 2008R and I experince the following error on every package I create and execute:
"Executing the query "DECLARE @Guid UNIQUEIDENTIFIER      EXECUTE msdb..sp..." failed with the following error: "The INSERT statement conflicted with the FOREIGN KEY constraint "FK_sysmaintplan_log_subplan_id".
The conflict occurred in database "msdb", table "dbo.sysmaintplan_subplans", column 'subplan_id'.  The statement has been terminated.". Possible failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established correctly. "
Do you have any experience?
Below, the complete error messege
Executed as user: *******. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4000.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  6:37:47 AM  Error: 2014-02-01 06:37:47.81    
Code: 0xC002F210     Source: {A77A0D78-E4F8-48DA-9933-68E53270789C} Execute SQL Task     Description: Executing the query "DECLARE @Guid UNIQUEIDENTIFIER      EXECUTE msdb..sp..." failed
with the following error: "The INSERT statement conflicted with the FOREIGN KEY constraint "FK_sysmaintplan_log_subplan_id". The conflict occurred in database "msdb", table "dbo.sysmaintplan_subplans", column 'subplan_id'. 
The statement has been terminated.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.  End Error  Warning: 2014-02-01
06:37:47.81     Code: 0x80019002     Source: OnPreExecute      Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised
(1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.  End Warning  Progress: 2014-02-01 06:37:48.37    
Source: Check Database Integrity Task      Executing query "USE [*******]  ".: 50% complete  End Progress  Progress: 2014-02-01 06:37:51.58     Source: Check Database Integrity Task     
Executing query "DBCC CHECKDB(N'*******')  WITH NO_INFOMSGS...".: 100% complete  End Progress  Progress: 2014-02-01 06:37:51.58     Source: Check Database Integrity Task      Executing query
"USE [*******]  ".: 50% complete  End Progress  Progress: 2014-02-01 06:37:54.19     Source: Check Database Integrity Task      Executing query "DBCC CHECKDB(N'*******')  WITH
NO_INFOMSG...".: 100% complete  End Progress  Error: 2014-02-01 06:37:54.20     Code: 0xC0024104     Source: Check Database Integrity Task      Description: The Execute method
on the task returned error code 0x80131501 (An exception occurred while executing a Transact-SQL statement or batch.). The Execute method must succeed, and indicate the result using an "out" parameter.  End Error  Error: 2014-02-01 06:37:54.20    
Code: 0xC0024104     Source: {23A7637D-F19B-4BDA-BF4E-D82C1A7F3682}      Description: The Execute method on the task returned error code 0x80131501 (An exception occurred while executing a Transact-SQL statement
or batch.). The Execute method must succeed, and indicate the result using an "out" parameter.  End Error  Warning: 2014-02-01 06:37:54.20     Code: 0x80019002     Source: OnPostExecute     
Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified
in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.  End Warning  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  6:37:47 AM  Finished: 6:37:54 AM  Elapsed:  6.692 seconds.  The
package execution failed.  The step failed.
Thank you in advance for the help.
Martino Pavone

Answer 1

Hi,
The cause of this problem was that the job had become orphaned. We can prove this by doing the following test.
use msdb
go
select * from dbo.sysjobs
go
sysjobs in MSDB which stores the information for each scheduled job to be executed by SQL Server Agent.
Copy the job ID for the job that had stopped working and check in sysmaintplan_subplans for the same job ID.
use msdb
go
select * from sysmaintplan_subplans where job_id = <JOBID of that job that is a part of the maintenance plan which has stopped execution>
go
sysmaintplan_subplans in MSDB is updated by the SQL Server which contains the information like the job id ,Plan_id ,Sub_plan name, subplan_id.
If the job ID is present in the sysjobs but not in the sysmaintplan_subplans table then the job becomes orphaned.
You may get an output which returns no rows and returns only the column names. Or get the below error:
Msg 8169, Level 16, State 2, Line 1
Conversion failed when converting from a character string to uniqueidentifier.
To work around this problem, manually create the record of the maintenance plan that you import. See the below KB article for details:
BUG: Error message when you try to save a maintenance plan in SQL Server Management Studio: "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)"
http://support.microsoft.com/kb/922651
Thanks.
Tracy Cai
TechNet Community Support