Article ID: 938085 - View products that this article applies to.
Bug #: 50001017 (SQL Hotfix)
After you install Microsoft SQL Server 2005 Service Pack 2 (SP2), you use a clean-up task in SQL Server 2005. However, the clean-up task does not delete database maintenance plan reports. Additionally, you receive an error message that resembles the following:
Error: 2006-12-06 16:52:39.92 Code: 0xC002F210 Source: Maintenance Cleanup Task 1 Execute SQL Task Description: Executing the query "EXECUTE master.dbo.xp_delete_file 1,N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\sdtest.txt' " failed with the following error: "Error executing xp_delete_file extended stored procedure: Specified file is not a Maintenance Plan report file.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error Warning: 2006-12-06 16:52:39.92 Code: 0x80019002 ... The package execution fa... The step failed.
This problem occurs because the first line of the report contains the following text:
NEW COMPONENT OUTPUTThe xp_delete_file system stored procedure examines the first line of the report to determine whether the report is a database maintenance plan report. If the first line of the report is "NEW COMPONENT OUTPUT," the xp_delete_file system stored procedure cannot recognize the report as a database maintenance plan report.
Cumulative update informationTo resolve this problem, obtain cumulative update package 2 for SQL Server 2005 Service Pack 2. For more information about how to obtain cumulative update package 2, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/936305/ )Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
To work around this problem, delete the first line of the report if the first line of the report is "NEW COMPONENT OUTPUT". After you do this, the report will be deleted the next time that you use the clean-up task.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 938085 - Last Review: January 21, 2008 - Revision: 2.1