June 15, 2010 at 8:07 am
Hello,
I created a maintenance plan (in SSMS) with the tasks 'History Cleanup Task' and 'Maintenance Cleanup task'.
The associated job returns 'failed' while the maintplan is success. If I look at the history of the maintplan, I dont see the task 'History Cleanup Task'!!!;-)
If I execute the associated T-SQL, (declare @dt datetime select @dt = cast(N'2010-05-18T16:02:36' as datetime) exec msdb.dbo.sp_delete_backuphistory @dt
GO
EXEC msdb.dbo.sp_purge_jobhistory @oldest_date='2010-05-18T16:02:36'
GO
EXECUTE msdb..sp_maintplan_delete_log null,null,'2010-05-18T16:02:36'
)there are deleted lines!!;-)
Can anybody help me?
Thank you
June 17, 2010 at 8:54 am
no idea???
June 17, 2010 at 9:00 am
If you have the job set to output to a log does that give you any information?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
June 17, 2010 at 9:26 am
Yes but unuseable 😀
Job log :
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 17:17:42
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 17:17:42
Finished: 17:17:50
Elapsed: 8.203 seconds
MaintPlan log :
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3200
Report was generated on "***".
Maintenance Plan: test
Duration: 00:00:07
Status: Succeeded.
Details:
Maintenance Cleanup Task (srvgsysql02)
Task start: 2010-06-17T17:17:48.
Task end: 2010-06-17T17:17:48.
Success
😉
June 17, 2010 at 9:35 am
Did this job work prior? Are you aware of anything that changed if it did previously work (SP, CU installs)? Missed you stated you created it:-P
Is this server a 64-bit server?
DTExec: The package execution returned DTSER_FAILURE (1)
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
June 18, 2010 at 12:06 am
Try changing the user the job is running under to 'sa'.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
June 18, 2010 at 1:18 am
Make sure the OS Backup is not conflicting as it folder is accesse by other os backup than also SQL Server won't able to delete the file.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
June 18, 2010 at 3:25 am
Hi,
MeltonDBA : it's a 32-bit server.
OomBoom : sa is the owner of the maint plan and the job.
free_mascot : I tested at various hours and the problem is not that on the backup files but also in tables of the jobs and maintplans history
June 18, 2010 at 5:38 am
The next thing you can try is deleting the maint plan a recreating but do not create plan from remote pc, create the plan by logging on to the server with Remote Desktop.
Then for good measure make sure your service account have rights to the package folder and any other folders you are working on.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
June 18, 2010 at 7:52 am
The maintplan is already created directly on the server, I tried by creating another maintplan and it changes nothing.
I even tried by starting the services in Local System and nothing changes
June 18, 2010 at 1:52 pm
These kinds of issues are generally related to a mis-match between the client tools and the version of the server. Validate the version of the client tools is the same as the server (or greater).
Also, there are known issues with maintenance plans and SQL Server 2005 SP2. There were several hotfixes to fix these issues. I would recommend upgraded to SP3 for both the server and client tools.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply