Mintenance PLan issue

[niall5098]

HI All,

I have a maintenance plan that remove .bak and .trn files older than 4 days.

This job has run successfully for over a year without issue.

Since midnight on the 3rd May i am getting these errors:

Executing the query "EXECUTE master.dbo.xp_delete_file 0,N'\\\\servername\\SQL Backups\\foldername\\',N'trn',N'2010-04-30T11:00:18',1
" failed with the following error: "A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The files are on a remote server, but i can log into that server and remove files using the same login used to run the jobs. i can also map the drive without issue.

Most searches i have doen so far refer to permissions issues but if i can log in and delete files then the job should be able to it aswell, so i am looking for any other possible reasons for this issue.

Thanks in advance.

 

[SQLBill]

You don't say what version you are using, but I have found with SS2000 sometime Maintenance plans just 'break'. Try dropping the plan and re-creating it.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[niall5098]

The version of SQL SERVER is 2005 sp2. I will recreate the maintenance plans and see if that resolves the issue.

 

[Crowley16]

have you tried running the actual query, obviously substituting in the correct values?

EXECUTE master.dbo.xp_delete_file 0,N'\\\\servername\\SQL Backups\\foldername\\',N'trn',N'2010-04-30T11:00:18',1

--------------------
Procrastinate Now!

 

[niall5098]

i TRIED RUNNING THE SQL BUT RECIEVED AN ERROR ASWELL.

WHAT SEEMED TO WORK WAS UNMAPPING THE DRIVE AND REMAPPING.

 

[PRPhx]

You might want to check your event logs for clues as to what is going on. Is there a possibility that there was a network issue before/during the execution of the maint. plan?