June 17, 2013 at 7:30 am
Hi All
I have one backup database schedule Every night. It went well everyday but today it failed.
I check backup location, there is backup file but Job History says it failed.
Message
Executed as user:XXXXXXXXX. ...00.4035.00 for 32-bit Started: 3:00:04 AM Progress: 2013-06-17 03:00:07.73 Source: {B73199AA-F4BC-4962-AFC1-B033F62D7BCD} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Progress: 2013-06-17 03:00:07.93 Source: Maintenance Cleanup Task Executing query "EXECUTE master.dbo.xp_delete_file 0,N'\\ServerName".: 100% complete End Progress Progress: 2013-06-17 05:07:28.18 Source: Back Up Database Task Executing query "BACKUP DATABASE [AAAAA] TO DISK = N'\\ServerName-".: 100% complete End Progress Error: 2013-06-17 05:08:07.41 Code: 0xC0024104 Source: Reporting Task for subplan-{7F0A750F-B2C0-42DD-966F-7A70E4D2FC93} Description: The Execute method on the task returned error code 0x80131904 (Timeout expired. The timeout period elapsed prior to completion of the ... The package execution fa... The step failed.
Please help me to understand.
June 17, 2013 at 8:18 am
Looks like you're using a maintenance plan for your backups. In that case check the maintenance plan history or the maintenance plan logfile for the exact error details.
[font="Verdana"]Markus Bohse[/font]
June 17, 2013 at 8:50 am
It looks like the cleanup task failed, not the backup. Did you check the backup file?
As mentioned above, you should have a detailed log for the package. Don't use the job history result as it doesn't have enough informaiton.
June 17, 2013 at 8:53 am
Steve Jones - SSC Editor (6/17/2013)
It looks like the cleanup task failed, not the backup. Did you check the backup file?As mentioned above, you should have a detailed log for the package. Don't use the job history result as it doesn't have enough informaiton.
I check Maintenance Plan Log File but it has only Successful ran file Log.
Can You please help me to find Error Log File for Maintenance Plan, That will be more helpfull
June 17, 2013 at 10:34 am
Look in this page: http://msdn.microsoft.com/en-us/library/ms180370.aspx
That's where it's configured.
You can't have a failure reported by the job and no failure in a log. Either you picked the wrong log file or it's not configured.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply