Error: 2009-03-18 20:05:15.90 Code: 0xC020801E Source:theDBName Daily Backups Log provider "{67ECD4E2-53A3-4D1E-BFD6-BFF6091B5D11}" Description: The connection manager "Local server connection" is an incorrect type. The type required is "FILE". The type available to the component is "ADO.NET:SQL".End ErrorDTExec: The package execution returned DTSER_FAILURE (1).Started: 8:05:00 p.m.Finished: 8:10:05 p.m.Elapsed: 305.156 seconds--------------This has me completely stumped!The backup step works but not the last bit that deletes backup files older than 3 days.This server has 2 jobs. Backup systemDBs and delete old filesBackup a user DB and delete old filesThe problem is the userdb "job"Folder structure is (local server)H:\SQLBackups\SystemDBsH:\SQLBackups\theDBNameMy NT account is the owner of both jobs.I have full control over the share and both folders and am a local admin on the local server.I am also a member of the SA role on the SQL side.The SQL Agent service account is also an NT account that has all the same permissions as myself.How can 2 identical jobs not both succeed?What on earth does the error mean??Plan was created via the MP wizard.SQL Server 2005 64 bit SP2 on Win2.3k 64 bit

I was researching this this morning and found an answer after seeing that nobody had responded here. This happens because creating a maintenance plan using SSIS (which is what the wizard in SSMS uses) uses windows credentials. When you then schedule it as a job, it uses SQL Server credentials. When I did this I created the maintenance plan on my local machine logged in as myself (DOMAIN\UserName). I then added this SSIS Package to an existing job which was owned by sa. sa does not have rights to run the SSIS package. So, by changing the owner on the SQL job to DOMAIN\UserName I was able to fix this. Thanks, Jared

I was researching this this morning and found an answer after seeing that nobody had responded here. This happens because creating a maintenance plan using SSIS (which is what the wizard in SSMS uses) uses windows credentials. When you then schedule it as a job, it uses SQL Server credentials. When I did this I created the maintenance plan on my local machine logged in as myself (DOMAIN\UserName). I then added this SSIS Package to an existing job which was owned by sa. sa does not have rights to run the SSIS package. So, by changing the owner on the SQL job to DOMAIN\UserName I was able to fix this. Thanks, Jared Sorry Jared however this is not what is causing this error. The OP was using the wrong connection manager for their output log file (Daily Backups Log provider). They should have used a Flat File Destination instead of a ADO.NET Destination. Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA Blog: MrWharty.wordpress.com