SQL Server 2008 R2 Maint Plan Backup Error

Looks to me like you have a problem with your msdb database.  It could be that your msdb is inaccessible due to insufficient space.  Why don't you take a look at the SQL Server Error log and see what is being reported there.  Or, even just go into SSMS, the databases folder, then system databases, msdb.  Right click the msdb and choose properties.  It will return a dialog box to you with varied properties.  See what it says for 'space available'.  

If it is insufficient space, that is an easy fix.  We'd need only to expand the files where needed.  It could also be other reasons that the msdb is inaccessible to you.  I think first thing is to get into the Error  log and see what the server is telling us.

>> Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.

From the error message, it is clear that the Backup is successful but it wasn't able to log the history records into msdb database tables.
Kindly check whether the records are huge in the related backup table and execute the procedure sp_delete_backuphistory to cleanup all those historical records to get rid of this error message. More details on backup history cleanup procedure below..
https://www.mssqltips.com/sqlservertip/1727/purging-msdb-backup-and-restore-history-from-sql-server/

Check if your msdb isn't full. If so turn on the autogrow for msdb so it can grow when it's full. Alternatively you can grow it manually by setting a new file size for the .mdf file.

Hey guys.  Thanks for the suggestions.  I will get access to this server in the next day or so.  I'll report back.

Very good, Michael.  As I said before, most likely you are having a problem accessing the msdb database, and I am betting this is due to available space/file size.  The fastest path to confirm this is just to get into the SQL ERROR LOG and check for errors/warnings on the msdb.  Or even just right click the msdb, choose properties, or run the query below.  It will tell you your current file state.  If you're files are full, you'll need to run an ALTER statement like the example below.

USE msdb;
SELECT RTRIM(name) AS [Segment Name], groupid AS [Group Id], filename [FileName],
   CAST(size/128.0 AS DECIMAL(10,2)) [SizeMB],
   CAST(FILEPROPERTY(name, 'SpaceUsed')/128.0 AS DECIMAL(10,2)) [SpaceUsedMB],
   CAST([maxsize]/128.0 AS DECIMAL(10,2)) [MaxMB],
   CAST(size/128.0-(FILEPROPERTY(name, 'SpaceUsed')/128.0) AS DECIMAL(10,2)) [AvailableMB],
   CAST((CAST(FILEPROPERTY(name, 'SpaceUsed')/128.0 AS DECIMAL(10,2))/CAST(size/128.0 AS DECIMAL(10,2)))*100 AS DECIMAL(10,2)) [PercentUsed]
FROM sysfiles
ORDER BY groupid DESC


ALTER DATABASE msdb
MODIFY FILE (
   name = msdbdata,
   size = XXXMB   ----<<< i typically build out my msdb's at 250MB, but this is totally your own call.  If it's already that size, go larger..
)

OK did a properties on msdb:
 
Size: 38.88 MB
Space available: 1.02 MB

Is there by any chance you have restricted the growth of data/log files for msdb, if so tables can't have new records inserted into it.

Here is a screen capture of that information
Capture.JPG

Ok, seems good.
Kindly try running the backup command directly from Query window and see whether you are getting any errors or not.
Ideally you shouldn't, if so please share the complete error message from Query window to troubleshoot further..

Are you talking running the Maintenance plan from the Query window or just a manual backup of the database?  

I am not sure how to run either from a Query window??

If I just run a manual backup backup of the msdb (or any of the databases) by right clicking the database, selecting the backup. It always runs successful.

Ok, seems good.

I don't think it seems good. The log file has a restricted grow. Can you check what value is set for the restricted grow?
Avoid using percentage for the autogrow. Instead, use a fixed value as for example 20MB.
The msdb files are being stored in D: . How much free space the drive has?

The drive has 1.38 TB of free space.  
MSDBData: By 10 percent, unrestricted growth
MSDBLog: By 10 percent, restricted growth to 2097152 MB

Curious.  Did you ever check the ERROR log to see what SQL is reporting regarding the msdb?

The log files are big with a lot of text.  Is there something in particular to look at or filter out?

As usual, search for "ERROR" entry in the log.

Did a find on the error logs and the only thing that was in there was "returned no errors' on many lines

Ok Found this in an older log:

2017-12-04 14:15:31.87 spid13s     Error: 9003, Severity: 20, State: 9.
2017-12-04 14:15:31.87 spid13s     The log scan number (448:40:1) passed to log scan in database 'msdb' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2017-12-04 14:15:31.87 spid13s     Error: 3414, Severity: 21, State: 1.
2017-12-04 14:15:31.87 spid13s     An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2017-12-04 14:15:31.89 spid10s     Error: 9003, Severity: 20, State: 1.
2017-12-04 14:15:31.89 spid10s     The log scan number (64:192:1) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2017-12-04 14:15:31.89 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Do we have any backups available for msdb and model from before this problem began?

No, Not that far back.  We only keep 2 weeks

Do I need to run any manual backups before i run this?  This wont cause any database damage or instability??

While backups are always good, I don't think you're at risk here.  The database is not usable as is.  Also I don't expect it will cause any instability or damage.  Again, the database is not usable as is.

OK I will run this later on, once all users have been logged out.  The Databases used are for Made to Manage software and are there own separate databases called:  M2MDATA01 & M2MSystems

Those are my main concerns and don't what to cause any issues with those databases.
Capture.JPG

>> I don't think it seems good. The log file has a restricted grow. Can you check what value is set for the restricted grow?

Thanks for pointing it Vitor, but by default it will be set to Restrictred growth for 2 TB and hence I said OK.

As dbaSQL mentioned, try running DBCC CHECKDB and post us the outcome for the same.

Michael, any news on this?

Hi guys sorry for the long delay.  I had Spinal Fusion Surgery and have been out for a while.  I will run the following command tonight:

USE MASTER;
DBCC CHECKDB (msdb, REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS
go

Results:

Msg 7919, Level 16, State 3, Line 2
Repair statement not processed. Database needs to be in single user mode.

Ok looked up this error and set the database to single user mode.  Here are the results now:

DBCC results for 'msdb'.
Service Broker Msg 9675, State 1: Message Types analyzed: 16.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 7.
Service Broker Msg 9667, State 1: Services analyzed: 6.
Service Broker Msg 9668, State 1: Service Queues analyzed: 6.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.
Repair: The extent (1:2384) has been deallocated from object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown).
Msg 8905, Level 16, State 1, Line 2
Extent (1:2376) in database ID 4 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
        The error has been repaired.
Msg 8905, Level 16, State 1, Line 2
Extent (1:2384) in database ID 4 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
        The error has been repaired.
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 546719272992768 (type Unknown), page ID (1:2384) contains an incorrect page ID in its page header. The PageId in the page header = (179:-248840177).
        The error has been repaired.
CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB fixed 2 allocation errors and 1 consistency errors not associated with any single object.
DBCC results for 'sys.sysrscols'.
There are 2209 rows in 21 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
There are 317 rows in 3 pages for object "sys.sysrowsets".
DBCC results for 'sys.sysallocunits'.
There are 400 rows in 5 pages for object "sys.sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syspriorities'.
There are 0 rows in 0 pages for object "sys.syspriorities".
DBCC results for 'sys.sysfgfrag'.
There are 2 rows in 1 pages for object "sys.sysfgfrag".
DBCC results for 'sys.sysphfg'.
There are 1 rows in 1 pages for object "sys.sysphfg".
DBCC results for 'sys.sysprufiles'.
There are 2 rows in 1 pages for object "sys.sysprufiles".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysowners'.
There are 34 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 562 rows in 4 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 1208 rows in 24 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 4516 rows in 81 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 4 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 2 rows in 1 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 1 rows in 1 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 35 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 488 rows in 9 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 730 rows in 5 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 29 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysaudacts'.
There are 0 rows in 0 pages for object "sys.sysaudacts".
DBCC results for 'sys.sysobjvalues'.
There are 1353 rows in 307 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 24 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 497 rows in 3 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 4503 rows in 34 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.syscompfragments'.
There are 0 rows in 0 pages for object "sys.syscompfragments".
DBCC results for 'sys.sysftstops'.
There are 0 rows in 0 pages for object "sys.sysftstops".
DBCC results for 'sys.sysqnames'.
There are 127 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 149 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 112 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 85 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 939 rows in 34 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 3 rows in 1 pages for object "sys.sysbinsubobjs".
DBCC results for 'sys.syssoftobjrefs'.
There are 1665 rows in 31 pages for object "sys.syssoftobjrefs".
DBCC results for 'syspolicy_policies_internal'.
There are 0 rows in 0 pages for object "syspolicy_policies_internal".
DBCC results for 'sysproxies'.
There are 0 rows in 0 pages for object "sysproxies".
DBCC results for 'sysdbmaintplan_history'.
There are 0 rows in 0 pages for object "sysdbmaintplan_history".
DBCC results for 'sysutility_ucp_space_utilization_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_space_utilization_stub".
DBCC results for 'syscollector_execution_stats_internal'.
There are 0 rows in 0 pages for object "syscollector_execution_stats_internal".
DBCC results for 'syssubsystems'.
There are 12 rows in 1 pages for object "syssubsystems".
DBCC results for 'backupmediaset'.
Repair:  Successfully inserted row in index "dbo.backupmediaset, backupmediasetuuid" in database "msdb".
Repair:  Successfully inserted row in index "dbo.backupmediaset, backupmediasetuuid" in database "msdb".
Msg 8951, Level 16, State 1, Line 2
Table error: table 'backupmediaset' (ID 46623209). Data row does not have a matching index row in the index 'backupmediasetuuid' (ID 2). Possible missing or invalid keys for the index row matching:
        The error has been repaired.
Msg 8955, Level 16, State 1, Line 2
Data row (1:2027:66) identified by (media_set_id = 2147) with index values 'media_uuid = '259EF241-829C-4F4C-8F07-CD6E9476B8ED' and media_set_id = 2147'.
Msg 8951, Level 16, State 1, Line 2
Table error: table 'backupmediaset' (ID 46623209). Data row does not have a matching index row in the index 'backupmediasetuuid' (ID 2). Possible missing or invalid keys for the index row matching:
        The error has been repaired.
Msg 8955, Level 16, State 1, Line 2
Data row (1:2027:67) identified by (media_set_id = 2148) with index values 'media_uuid = 'CAB24C1F-C06D-49BC-B011-E678692D95FD' and media_set_id = 2148'.
There are 2154 rows in 27 pages for object "backupmediaset".
CHECKDB found 0 allocation errors and 2 consistency errors in table 'backupmediaset' (object ID 46623209).
CHECKDB fixed 0 allocation errors and 2 consistency errors in table 'backupmediaset' (object ID 46623209).
DBCC results for 'sysproxysubsystem'.
There are 0 rows in 0 pages for object "sysproxysubsystem".
DBCC results for 'sysproxylogin'.
There are 0 rows in 0 pages for object "sysproxylogin".
DBCC results for 'log_shipping_primary_secondaries'.
There are 0 rows in 0 pages for object "log_shipping_primary_secondaries".
DBCC results for 'backupmediafamily'.
Repair:  Successfully deleted row in index "dbo.backupmediafamily, backupmediafamilyuuid" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupmediafamily, backupmediafamilyuuid" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupmediafamily, backupmediafamilyuuid" in database "msdb".
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupmediafamily' (ID 110623437). Index row in index 'backupmediafamilyuuid' (ID 2) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1860:27) with values (media_family_id = '4B4B3774-0000-0000-0000-000000000000' and media_set_id = 2147 and family_sequence_number = 1 and mirror = 0) pointing to the data row identified by (media_set_id = 2147 and family_sequence_number = 1 and mirror = 0).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupmediafamily' (ID 110623437). Index row in index 'backupmediafamilyuuid' (ID 2) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1950:23) with values (media_family_id = '703AF7C0-0000-0000-0000-000000000000' and media_set_id = 2146 and family_sequence_number = 1 and mirror = 0) pointing to the data row identified by (media_set_id = 2146 and family_sequence_number = 1 and mirror = 0).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupmediafamily' (ID 110623437). Index row in index 'backupmediafamilyuuid' (ID 2) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1950:34) with values (media_family_id = '6A3E30C2-0000-0000-0000-000000000000' and media_set_id = 2144 and family_sequence_number = 1 and mirror = 0) pointing to the data row identified by (media_set_id = 2144 and family_sequence_number = 1 and mirror = 0).
There are 2149 rows in 47 pages for object "backupmediafamily".
CHECKDB found 0 allocation errors and 3 consistency errors in table 'backupmediafamily' (object ID 110623437).
CHECKDB fixed 0 allocation errors and 3 consistency errors in table 'backupmediafamily' (object ID 110623437).
DBCC results for 'sqlagent_info'.
There are 0 rows in 0 pages for object "sqlagent_info".
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object "sysdownloadlist".
DBCC results for 'log_shipping_monitor_primary'.
There are 0 rows in 0 pages for object "log_shipping_monitor_primary".
DBCC results for 'sysjobhistory'.
Repair:  Successfully inserted row in index "dbo.sysjobhistory, nc1" in database "msdb".
Repair:  Successfully inserted row in index "dbo.sysjobhistory, nc1" in database "msdb".
Repair:  Successfully inserted row in index "dbo.sysjobhistory, nc1" in database "msdb".
Repair:  Successfully inserted row in index "dbo.sysjobhistory, nc1" in database "msdb".
Msg 8951, Level 16, State 1, Line 2
Table error: table 'sysjobhistory' (ID 149575571). Data row does not have a matching index row in the index 'nc1' (ID 2). Possible missing or invalid keys for the index row matching:
        The error has been repaired.
Msg 8955, Level 16, State 1, Line 2
Data row (1:1786:0) identified by (instance_id = 1457) with index values 'job_id = '32D6FBF7-3F20-4AE9-A54B-1E0A87D879DA' and instance_id = 1457'.
Msg 8951, Level 16, State 1, Line 2
Table error: table 'sysjobhistory' (ID 149575571). Data row does not have a matching index row in the index 'nc1' (ID 2). Possible missing or invalid keys for the index row matching:
        The error has been repaired.
Msg 8955, Level 16, State 1, Line 2
Data row (1:1786:1) identified by (instance_id = 1458) with index values 'job_id = '32D6FBF7-3F20-4AE9-A54B-1E0A87D879DA' and instance_id = 1458'.
Msg 8951, Level 16, State 1, Line 2
Table error: table 'sysjobhistory' (ID 149575571). Data row does not have a matching index row in the index 'nc1' (ID 2). Possible missing or invalid keys for the index row matching:
        The error has been repaired.
Msg 8955, Level 16, State 1, Line 2
Data row (1:1786:2) identified by (instance_id = 1459) with index values 'job_id = '32D6FBF7-3F20-4AE9-A54B-1E0A87D879DA' and instance_id = 1459'.
Msg 8951, Level 16, State 1, Line 2
Table error: table 'sysjobhistory' (ID 149575571). Data row does not have a matching index row in the index 'nc1' (ID 2). Possible missing or invalid keys for the index row matching:
        The error has been repaired.
Msg 8955, Level 16, State 1, Line 2
Data row (1:1786:3) identified by (instance_id = 1460) with index values 'job_id = '32D6FBF7-3F20-4AE9-A54B-1E0A87D879DA' and instance_id = 1460'.
There are 402 rows in 96 pages for object "sysjobhistory".
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sysjobhistory' (object ID 149575571).
CHECKDB fixed 0 allocation errors and 4 consistency errors in table 'sysjobhistory' (object ID 149575571).
DBCC results for 'sysoriginatingservers'.
There are 0 rows in 0 pages for object "sysoriginatingservers".
DBCC results for 'log_shipping_monitor_history_detail'.
There are 0 rows in 0 pages for object "log_shipping_monitor_history_detail".
DBCC results for 'backupset'.
Repair:  Successfully deleted row in index "dbo.backupset, backupsetuuid" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetuuid" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetuuid" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetDate" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetDate" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetDate" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetDate" in database "msdb".
Repair:  Successfully deleted row in index "dbo.backupset, backupsetDate" in database "msdb".
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetuuid' (ID 2) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1731:102) with values (backup_set_uuid = 'E024CC94-CE5D-4657-BCF3-4E04B817A9EF' and backup_set_id = 2147) pointing to the data row identified by (backup_set_id = 2147).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetuuid' (ID 2) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1862:143) with values (backup_set_uuid = '257704CC-853A-4F8C-9BD3-B0E19B55ECF1' and backup_set_id = 2145) pointing to the data row identified by (backup_set_id = 2145).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetuuid' (ID 2) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1979:139) with values (backup_set_uuid = 'EB585368-726A-4276-8E4E-C34C32F2185A' and backup_set_id = 2148) pointing to the data row identified by (backup_set_id = 2148).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetDate' (ID 3) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1865:119) with values (backup_finish_date = '2017-11-03 23:00:56.000' and backup_set_id = 2144) pointing to the data row identified by (backup_set_id = 2144).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetDate' (ID 3) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1865:120) with values (backup_finish_date = '2017-11-03 23:00:56.000' and backup_set_id = 2145) pointing to the data row identified by (backup_set_id = 2145).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetDate' (ID 3) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1865:121) with values (backup_finish_date = '2017-11-03 23:00:56.000' and backup_set_id = 2146) pointing to the data row identified by (backup_set_id = 2146).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetDate' (ID 3) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1865:122) with values (backup_finish_date = '2017-11-03 23:00:56.000' and backup_set_id = 2147) pointing to the data row identified by (backup_set_id = 2147).
Msg 8952, Level 16, State 1, Line 2
Table error: table 'backupset' (ID 206623779). Index row in index 'backupsetDate' (ID 3) does not match any data row. Possible extra or invalid keys for:
        The error has been repaired.
Msg 8956, Level 16, State 1, Line 2
Index row (1:1865:123) with values (backup_finish_date = '2017-11-03 23:00:56.000' and backup_set_id = 2148) pointing to the data row identified by (backup_set_id = 2148).
There are 2149 rows in 144 pages for object "backupset".
CHECKDB found 0 allocation errors and 8 consistency errors in table 'backupset' (object ID 206623779).
CHECKDB fixed 0 allocation errors and 8 consistency errors in table 'backupset' (object ID 206623779).
DBCC results for 'log_shipping_monitor_error_detail'.
There are 0 rows in 0 pages for object "log_shipping_monitor_error_detail".
DBCC results for 'log_shipping_secondary'.
There are 0 rows in 0 pages for object "log_shipping_secondary".
DBCC results for 'sysmail_attachments'.
There are 0 rows in 0 pages for object "sysmail_attachments".
DBCC results for 'backupfilegroup'.
There are 2149 rows in 31 pages for object "backupfilegroup".
DBCC results for 'log_shipping_secondary_databases'.
There are 0 rows in 0 pages for object "log_shipping_secondary_databases".
DBCC results for 'sysmail_send_retries'.
There are 0 rows in 0 pages for object "sysmail_send_retries".
DBCC results for 'log_shipping_monitor_secondary'.
There are 0 rows in 0 pages for object "log_shipping_monitor_secondary".
DBCC results for 'log_shipping_primaries'.
There are 0 rows in 0 pages for object "log_shipping_primaries".
DBCC results for 'backupfile'.
Repair: The Clustered index successfully rebuilt for the object "dbo.backupfile" in database "msdb".
Repair: The extent (1:2376) has been allocated to object ID 366624349, index ID 1, partition ID 72057594043826176, alloc unit ID 72057594045267968 (type In-row data).
Msg 8945, Level 16, State 1, Line 2
Table error: Object ID 366624349, index ID 1 will be rebuilt.
        The error has been repaired.
Msg 8978, Level 16, State 1, Line 2
Table error: Object ID 366624349, index ID 1, partition ID 72057594043826176, alloc unit ID 72057594045267968 (type In-row data). Page (1:2376) is missing a reference from previous page (1:2359). Possible chain linkage problem.
        The error has been repaired.
There are 4306 rows in 240 pages for object "backupfile".
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupfile' (object ID 366624349).
CHECKDB fixed 0 allocation errors and 1 consistency errors in table 'backupfile' (object ID 366624349).
DBCC results for 'sysjobs'.
There are 6 rows in 1 pages for object "sysjobs".
DBCC results for 'sysutility_ucp_mi_file_space_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_mi_file_space_health_internal".
DBCC results for 'log_shipping_monitor_alert'.
There are 0 rows in 0 pages for object "log_shipping_monitor_alert".
DBCC results for 'sysjobservers'.
There are 6 rows in 1 pages for object "sysjobservers".
DBCC results for 'log_shipping_secondaries'.
There are 0 rows in 0 pages for object "log_shipping_secondaries".
DBCC results for 'sysutility_mi_configuration_internal'.
There are 0 rows in 0 pages for object "sysutility_mi_configuration_internal".
DBCC results for 'syssessions'.
There are 11 rows in 1 pages for object "syssessions".
DBCC results for 'sysmail_log'.
There are 0 rows in 0 pages for object "sysmail_log".
DBCC results for 'restorehistory'.
There are 3 rows in 1 pages for object "restorehistory".
DBCC results for 'sysutility_ucp_mi_database_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_mi_database_health_internal".
DBCC results for 'syscollector_blobs_internal'.
There are 0 rows in 0 pages for object "syscollector_blobs_internal".
DBCC results for 'sysjobactivity'.
There are 35 rows in 1 pages for object "sysjobactivity".
DBCC results for 'sysutility_mi_dac_execution_statistics_internal'.
There are 0 rows in 0 pages for object "sysutility_mi_dac_execution_statistics_internal".
DBCC results for 'restorefile'.
There are 6 rows in 1 pages for object "restorefile".
DBCC results for 'syscollector_tsql_query_collector'.
There are 0 rows in 0 pages for object "syscollector_tsql_query_collector".
DBCC results for 'sysjobsteps'.
There are 8 rows in 1 pages for object "sysjobsteps".
DBCC results for 'sysmail_query_transfer'.
There are 0 rows in 0 pages for object "sysmail_query_transfer".
DBCC results for 'restorefilegroup'.
There are 3 rows in 1 pages for object "restorefilegroup".
DBCC results for 'sysjobstepslogs'.
There are 0 rows in 0 pages for object "sysjobstepslogs".
DBCC results for 'sysutility_ucp_dac_file_space_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_dac_file_space_health_internal".
DBCC results for 'logmarkhistory'.
There are 0 rows in 0 pages for object "logmarkhistory".
DBCC results for 'suspect_pages'.
There are 0 rows in 0 pages for object "suspect_pages".
DBCC results for 'sysmail_attachments_transfer'.
There are 0 rows in 0 pages for object "sysmail_attachments_transfer".
DBCC results for 'sysutility_mi_session_statistics_internal'.
There are 0 rows in 0 pages for object "sysutility_mi_session_statistics_internal".
DBCC results for 'sysdtscategories'.
There are 3 rows in 1 pages for object "sysdtscategories".
DBCC results for 'syspolicy_target_sets_internal'.
There are 0 rows in 0 pages for object "syspolicy_target_sets_internal".
DBCC results for 'sysutility_ucp_mi_volume_space_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_mi_volume_space_health_internal".
DBCC results for 'sysschedules'.
There are 13 rows in 1 pages for object "sysschedules".
DBCC results for 'sysutility_ucp_snapshot_partitions_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_snapshot_partitions_internal".
DBCC results for 'sysdtspackages'.
There are 0 rows in 0 pages for object "sysdtspackages".
DBCC results for 'syspolicy_target_set_levels_internal'.
There are 0 rows in 0 pages for object "syspolicy_target_set_levels_internal".
DBCC results for 'sysdac_instances_internal'.
There are 0 rows in 0 pages for object "sysdac_instances_internal".
DBCC results for 'sysssispackages'.
There are 11 rows in 1 pages for object "sysssispackages".
DBCC results for 'sysutility_ucp_computer_cpu_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_computer_cpu_health_internal".
DBCC results for 'sysutility_mi_volumes_stage_internal'.
There are 0 rows in 0 pages for object "sysutility_mi_volumes_stage_internal".
DBCC results for 'sysssispackagefolders'.
There are 4 rows in 1 pages for object "sysssispackagefolders".
DBCC results for 'sysdac_history_internal'.
There are 0 rows in 0 pages for object "sysdac_history_internal".
DBCC results for 'sysjobschedules'.
There are 6 rows in 1 pages for object "sysjobschedules".
DBCC results for 'sysutility_mi_cpu_stage_internal'.
There are 0 rows in 0 pages for object "sysutility_mi_cpu_stage_internal".
DBCC results for 'sysssislog'.
There are 0 rows in 0 pages for object "sysssislog".
DBCC results for 'sysutility_ucp_aggregated_dac_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_aggregated_dac_health_internal".
DBCC results for 'syscategories'.
There are 21 rows in 1 pages for object "syscategories".
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object "systargetservers".
DBCC results for 'systargetservergroups'.
There are 0 rows in 0 pages for object "systargetservergroups".
DBCC results for 'systargetservergroupmembers'.
There are 0 rows in 0 pages for object "systargetservergroupmembers".
DBCC results for 'syspolicy_policy_category_subscriptions_internal'.
There are 0 rows in 0 pages for object "syspolicy_policy_category_subscriptions_internal".
DBCC results for 'sysalerts'.
There are 0 rows in 0 pages for object "sysalerts".
DBCC results for 'sysoperators'.
There are 0 rows in 0 pages for object "sysoperators".
DBCC results for 'sysnotifications'.
There are 0 rows in 0 pages for object "sysnotifications".
DBCC results for 'sysdtspackagelog'.
There are 0 rows in 0 pages for object "sysdtspackagelog".
DBCC results for 'sysmaintplan_subplans'.
There are 5 rows in 1 pages for object "sysmaintplan_subplans".
DBCC results for 'syspolicy_system_health_state_internal'.
There are 0 rows in 0 pages for object "syspolicy_system_health_state_internal".
DBCC results for 'sysdtssteplog'.
There are 0 rows in 0 pages for object "sysdtssteplog".
DBCC results for 'sysutility_ucp_aggregated_mi_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_aggregated_mi_health_internal".
DBCC results for 'syscollector_config_store_internal'.
There are 5 rows in 1 pages for object "syscollector_config_store_internal".
DBCC results for 'sysutility_mi_smo_stage_internal'.
There are 0 rows in 0 pages for object "sysutility_mi_smo_stage_internal".
DBCC results for 'sysmanagement_shared_server_groups_internal'.
There are 5 rows in 1 pages for object "sysmanagement_shared_server_groups_internal".
DBCC results for 'sysmaintplan_log'.
There are 711 rows in 12 pages for object "sysmaintplan_log".
DBCC results for 'sysutility_mi_smo_objects_to_collect_internal'.
There are 5 rows in 1 pages for object "sysutility_mi_smo_objects_to_collect_internal".
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object "sysdtstasklog".
DBCC results for 'syspolicy_policy_execution_history_internal'.
There are 0 rows in 0 pages for object "syspolicy_policy_execution_history_internal".
DBCC results for 'sysmaintplan_logdetail'.
There are 1769 rows in 1430 pages for object "sysmaintplan_logdetail".
DBCC results for 'sysutility_mi_smo_properties_to_collect_internal'.
There are 84 rows in 1 pages for object "sysutility_mi_smo_properties_to_collect_internal".
DBCC results for 'systaskids'.
There are 0 rows in 0 pages for object "systaskids".
DBCC results for 'sysmanagement_shared_registered_servers_internal'.
There are 0 rows in 0 pages for object "sysmanagement_shared_registered_servers_internal".
DBCC results for 'syscachedcredentials'.
There are 0 rows in 0 pages for object "syscachedcredentials".
DBCC results for 'syscollector_collection_sets_internal'.
There are 4 rows in 1 pages for object "syscollector_collection_sets_internal".
DBCC results for 'syspolicy_policy_execution_history_details_internal'.
There are 0 rows in 0 pages for object "syspolicy_policy_execution_history_details_internal".
DBCC results for 'sysutility_ucp_dac_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_dac_health_internal".
DBCC results for 'MSdbms'.
There are 8 rows in 1 pages for object "MSdbms".
DBCC results for 'MSdbms_datatype'.
There are 180 rows in 2 pages for object "MSdbms_datatype".
DBCC results for 'MSdbms_map'.
There are 374 rows in 5 pages for object "MSdbms_map".
DBCC results for 'sysutility_ucp_supported_object_types_internal'.
There are 8 rows in 1 pages for object "sysutility_ucp_supported_object_types_internal".
DBCC results for 'sysmail_profile'.
There are 0 rows in 0 pages for object "sysmail_profile".
DBCC results for 'sysutility_ucp_managed_instances_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_managed_instances_internal".
DBCC results for 'syspolicy_execution_internal'.
There are 0 rows in 0 pages for object "syspolicy_execution_internal".
DBCC results for 'sysmail_principalprofile'.
There are 0 rows in 0 pages for object "sysmail_principalprofile".
DBCC results for 'syspolicy_management_facets'.
There are 83 rows in 1 pages for object "syspolicy_management_facets".
DBCC results for 'sysutility_ucp_mi_health_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_mi_health_internal".
DBCC results for 'syscollector_collector_types_internal'.
There are 4 rows in 1 pages for object "syscollector_collector_types_internal".
DBCC results for 'sys.queue_messages_1568724641'.
There are 0 rows in 0 pages for object "sys.queue_messages_1568724641".
DBCC results for 'syspolicy_configuration_internal'.
There are 4 rows in 1 pages for object "syspolicy_configuration_internal".
DBCC results for 'syspolicy_facet_events'.
There are 84 rows in 2 pages for object "syspolicy_facet_events".
DBCC results for 'sysutility_ucp_processing_state_internal'.
There are 1 rows in 1 pages for object "sysutility_ucp_processing_state_internal".
DBCC results for 'sys.queue_messages_1627152842'.
There are 0 rows in 0 pages for object "sys.queue_messages_1627152842".
DBCC results for 'sysmail_account'.
There are 0 rows in 0 pages for object "sysmail_account".
DBCC results for 'syspolicy_conditions_internal'.
There are 0 rows in 0 pages for object "syspolicy_conditions_internal".
DBCC results for 'MSdbms_datatype_mapping'.
There are 493 rows in 4 pages for object "MSdbms_datatype_mapping".
DBCC results for 'sys.queue_messages_1659152956'.
There are 0 rows in 0 pages for object "sys.queue_messages_1659152956".
DBCC results for 'sysutility_ucp_health_policies_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_health_policies_internal".
DBCC results for 'sysmail_profileaccount'.
There are 0 rows in 0 pages for object "sysmail_profileaccount".
DBCC results for 'syscollector_collection_items_internal'.
There are 6 rows in 2 pages for object "syscollector_collection_items_internal".
DBCC results for 'sysmail_servertype'.
There are 1 rows in 1 pages for object "sysmail_servertype".
DBCC results for 'sysutility_ucp_filegroups_with_policy_violations_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_filegroups_with_policy_violations_internal".
DBCC results for 'sysutility_ucp_policy_check_conditions_internal'.
There are 12 rows in 1 pages for object "sysutility_ucp_policy_check_conditions_internal".
DBCC results for 'sysutility_ucp_configuration_internal'.
There are 13 rows in 1 pages for object "sysutility_ucp_configuration_internal".
DBCC results for 'sysdbmaintplans'.
There are 1 rows in 1 pages for object "sysdbmaintplans".
DBCC results for 'sysutility_ucp_policy_target_conditions_internal'.
There are 24 rows in 1 pages for object "sysutility_ucp_policy_target_conditions_internal".
DBCC results for 'sysmail_server'.
There are 0 rows in 0 pages for object "sysmail_server".
DBCC results for 'syspolicy_policy_categories_internal'.
There are 0 rows in 0 pages for object "syspolicy_policy_categories_internal".
DBCC results for 'sysutility_ucp_policy_violations_internal'.
There are 0 rows in 0 pages for object "sysutility_ucp_policy_violations_internal".
DBCC results for 'sysutility_ucp_dacs_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_dacs_stub".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'sysutility_ucp_volumes_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_volumes_stub".
DBCC results for 'syspolicy_object_sets_internal'.
There are 0 rows in 0 pages for object "syspolicy_object_sets_internal".
DBCC results for 'sysdbmaintplan_jobs'.
There are 0 rows in 0 pages for object "sysdbmaintplan_jobs".
DBCC results for 'sysutility_ucp_computers_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_computers_stub".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'sysutility_ucp_smo_servers_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_smo_servers_stub".
DBCC results for 'sysutility_ucp_databases_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_databases_stub".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'sysmail_configuration'.
There are 7 rows in 1 pages for object "sysmail_configuration".
DBCC results for 'sysutility_ucp_filegroups_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_filegroups_stub".
DBCC results for 'sys.filestream_tombstone_2073058421'.
There are 0 rows in 0 pages for object "sys.filestream_tombstone_2073058421".
DBCC results for 'sysutility_ucp_datafiles_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_datafiles_stub".
DBCC results for 'sys.syscommittab'.
There are 0 rows in 0 pages for object "sys.syscommittab".
DBCC results for 'sysdbmaintplan_databases'.
There are 0 rows in 0 pages for object "sysdbmaintplan_databases".
DBCC results for 'sysutility_ucp_logfiles_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_logfiles_stub".
DBCC results for 'syscollector_execution_log_internal'.
There are 0 rows in 0 pages for object "syscollector_execution_log_internal".
DBCC results for 'sysutility_ucp_cpu_utilization_stub'.
There are 0 rows in 0 pages for object "sysutility_ucp_cpu_utilization_stub".
DBCC results for 'log_shipping_primary_databases'.
There are 0 rows in 0 pages for object "log_shipping_primary_databases".
DBCC results for 'sysmail_mailitems'.
There are 0 rows in 0 pages for object "sysmail_mailitems".
CHECKDB found 2 allocation errors and 19 consistency errors in database 'msdb'.
CHECKDB fixed 2 allocation errors and 19 consistency errors in database 'msdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Hope your errors might have been resolved now, kindly try running below code once to see if everything is fine or not.

dbcc checkdb(‘msdb’) with no_infomsgs

Select allOpen in new window

If everything is fine, then just take a full backup of msdb database and you should be good to go..

just a suggestion, for these kind of long messages, attach it as a text file instead of such a long comment..

Sorry, will do that next time.  Thanks!!

thanks, as requested above, kindly try running below script and see everything is working fine or not..

dbcc checkdb(‘msdb’) with no_infomsgs

Select allOpen in new window

Ran you script.
dbcc checkdb(‘msdb’) with no_infomsgs

Got this result:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '‘'.
Msg 319, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.

Command(s) completed successfully.

Looks good

Good, then try to take the full backup of your msdb database and then try running your Maintenance plan once to see whether it works successfully or not..

Manual Backup of msdb database was successful.

The Maintenance Plan runs successfully now too!

Thanks, kindly request you to close the question by splitting points to all experts whose suggestions were helpful..

Thanks everyone for the help in solving my problem.  Also thanks for your patience with me.