August 3, 2009 at 1:24 pm
Remember, these jobs run under the context of the service account running the application. That account may not have access to the file share to either delete or deposit new backup files. Look at the event log on the server you are trying to write/delete from and see if there is any additional information that you can obtain. Can you post the results from your logs?
-- You can't be late until you show up.
August 3, 2009 at 1:37 pm
Thanks for the tip Terry. I guess I just figured that if the backups were working fine (which they are), then the correct file system permissions would be set. However, I'll check into it since I haven't yet. Since you asked, here are my logs. Maybe you can understand them better than I can. Hopefully I'm not missing something incredibly obvious.
Removes .bak files and .trn files
*Maintenance Plan log*
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3310
Report was generated on "KOF-DB-01".
Maintenance Plan: Cleanup_Files
Duration: 00:00:06
Status: Succeeded.
Details:
Maintenance Cleanup Task (KOF-DB-01)
Task start: 2009-08-03T01:00:35.
Task end: 2009-08-03T01:00:39.
Success
Maintenance Cleanup Task 1 (KOF-DB-01)
Task start: 2009-08-03T01:00:39.
Task end: 2009-08-03T01:00:40.
Success
*Job History Log*
Date8/3/2009 1:00:00 AM
LogJob History (Cleanup_Files.Cleanup_Backups)
Step ID0
ServerKOF-DB-01
Job NameCleanup_Files.Cleanup_Backups
Step Name(Job outcome)
Duration00:00:41
Sql Severity0
Sql Message ID0
Operator EmailedSQL DBAs
Operator Net sent
Operator Paged
Retries Attempted0
Message
The job failed. The Job was invoked by Schedule 18 (Cleanup_Files.Cleanup_Transaction_Logs). The last step to run was step 1 (Cleanup_Backups).
Date8/3/2009 1:00:00 AM
LogJob History (Cleanup_Files.Cleanup_Backups)
Step ID1
ServerKOF-DB-01
Job NameCleanup_Files.Cleanup_Backups
Step NameCleanup_Backups
Duration00:00:41
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
Executed as user: KOF-DB-01\SYSTEM. ...n 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:00:01 AM Progress: 2009-08-03 01:00:34.00 Source: {725AEFED-797E-4CC5-AFD3-0F866D6111C5} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Error: 2009-08-03 01:00:35.00 Code: 0xC0024104 Source: Reporting Task for subplan-{8AAADDA1-C0A7-40DC-B799-7B8C15C5010D} Description: The Execute method on the task returned error code 0x80131931 (Data is Null. This method or property cannot be called on Null values.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2009-08-03 01:00:35.00 Code: 0x80019002 Source: Cleanup_Files Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); re... The package execution fa... The step failed.
Removes Maintenance Plan logs
*Maintenance Plan log*
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3310
Report was generated on "KOF-DB-01".
Maintenance Plan: Cleanup_Files
Duration: 00:00:04
Status: Succeeded.
Details:
Maintenance Cleanup Task (KOF-DB-01)
Task start: 2009-08-03T01:00:35.
Task end: 2009-08-03T01:00:38.
Success
*Job History Log*
Date8/3/2009 1:00:00 AM
LogJob History (Cleanup_Files.Cleanup_Logging)
Step ID0
ServerKOF-DB-01
Job NameCleanup_Files.Cleanup_Logging
Step Name(Job outcome)
Duration00:00:41
Sql Severity0
Sql Message ID0
Operator EmailedSQL DBAs
Operator Net sent
Operator Paged
Retries Attempted0
Message
The job failed. The Job was invoked by Schedule 19 (Cleanup_Files.Cleanup_Logging). The last step to run was step 1 (Cleanup_Logging).
Date8/3/2009 1:00:00 AM
LogJob History (Cleanup_Files.Cleanup_Logging)
Step ID1
ServerKOF-DB-01
Job NameCleanup_Files.Cleanup_Logging
Step NameCleanup_Logging
Duration00:00:41
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
Executed as user: KOF-DB-01\SYSTEM. ...n 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:00:01 AM Progress: 2009-08-03 01:00:34.73 Source: {916A5901-E95D-4E6D-A84D-F50C268ABAE0} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Error: 2009-08-03 01:00:35.00 Code: 0xC0024104 Source: Reporting Task for subplan-{8AAADDA1-C0A7-40DC-B799-7B8C15C5010D} Description: The Execute method on the task returned error code 0x80131931 (Data is Null. This method or property cannot be called on Null values.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2009-08-03 01:00:35.00 Code: 0x80019002 Source: Cleanup_Files Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); re... The package execution fa... The step failed.
August 3, 2009 at 1:51 pm
Not sure if it's something with 2005 but I have found I had to delete and recreate various maintenance plans as they had a tendency to fail. I see nothing in your logs to signify a security issue but it appears parameters are not being passed accordingly/ Personally, create a new maintenance plan (disabling the original), and when that is running as expected, delete the old plan.
-- You can't be late until you show up.
February 9, 2012 at 4:40 pm
Bumping thread as I'm having exact problem in my Transaction Log Backups in SQL 2005. Anyone found a solution yet?
February 10, 2012 at 4:19 am
Please post new questions in a new thread and include as much detail as possible. Thanks
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply