We started getting an error in part of our maintenance plan.  This has been running forever and within the last week, started erroring out.

Event Type:      Warning
Event Source:      SQLSERVERAGENT
Event Category:      Job Engine
Event ID:      208
Date:            4/19/2011
Time:            7:27:28 AM
User:            N/A
Computer:      SERVER01
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'Non AA database backup'' (0xFB47AEB8DD6DED4898606D6E954CAC8E) - Status: Failed - Invoked on: 2011-04-19 07:27:26 - Message: The job failed.  The Job was invoked by User MES\administrator.  The last step to run was step 1 (Step 1).

EXECUTE master.dbo.xp_sqlmaint N'-PlanID D1772498-25D5-45D6-9C9D-2317BBB65CC5 -WriteHistory  -VrfyBackup -BkUpMedia DISK -BkUpLog "C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP_TRN" -DelBkUps 4DAYS -BkExt "TRN"'
Who is Participating?
lcohanDatabase AnalystCommented:
Is that all you het from the Job history on that maintenance plan?
Was/is there any entry in the Event Viewer on that SQL Box besides this?
Was there any database dropped/moved recently that is still part of the Maintenance Plan?
Is there enough space for backups?
yostnetAuthor Commented:
hmm | guess it has not run in quite some time.

is there a way to reset the TRN maintenance plan?
Where is your backup going? Local drive, remote networked drive or tape?

Has anything changed with your network. How much space is free on your disk or tape?

How much space is available in MSDB and master. I have seen backups error out if there is not enough space in these databases. SQL does not grow these databas well and can fail when trying to grow.
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

yostnetAuthor Commented:
goes to a local drive.

Nothing has changed |

disk space is about 3gb or so.

How about the available space in MSDB and master
Anthony PerkinsCommented:
>>Nothing has changed<<
You need to start with the premise that something has changed.  Contrary to popular belief computers do not wake up one morning with a headache and decide not to work.  If you can at least accept that then will have a better chance of finding the problem.

For example, have you checked the Windows Event Log for errors?
Have you checked the detail from the SQL Server Agent "View History" option?
Have you tried executing the maintenance job from the SSMS query window with a valid login?
What is the startup account used by the SQL Server Agent service?  A domain account, a local sytem account, something else?
Anthony PerkinsCommented:
And another question:
Do you have a valid Full backup for the database?
yostnetAuthor Commented:
thx all
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.