I created a SSIS package that loops through a table with two columns filename and data. The data is written out to the associated filename. I imported the package to SQL 2005 sp2 with "rely on server" protection level. I can right click the package and execute without any problem. I created a SQL job to execute the package nightly and receive the error: Executed as user: xxxxx\sqlacct3. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:45:43 AM Error: 2010-11-21 11:45:44.63 Code: 0xC004706C Source: Data Flow Task DTS.Pipeline Description: Component "component "Recordset Destination" (37)" could not be created and returned error code 0x80070005. Make sure that the component is registered correctly. End Error Error: 2010-11-21 11:45:44.65 Code: 0xC0048021 Source: Data Flow Task Recordset Destination [37] Description: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Recordset Destination;Microsoft Corporation;Microsoft SqlServer v9; (C) 2005 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;0". End Error Error: 2010-11-21 11:45:44.65 Code: 0xC0047017 Source: Data Flow Task DTS.Pipeline Descript... The package execution fa... The step failed. Recordset Destination 37 takes an OLEDB source and writes the record to a variable. I have a ForEach loop after that that loops through each record in the table, writes to the variable, then creates the file. The only reason I can think this wouldn't work is the sqlacct3 doesn't have rights to the SSIS dll's. Any idea what's wrong? I've tried everything I can think of. Thanks Ben

Hello Ben, When you run it, do you use the same account? If you extract the command line from the job step that runs it, can you execute it successfully with both accounts?Arthur My Blog

what type of file is that? is it an excel? if so check.... 1- if you have sql 2008 ....http://blogs.msdn.com/b/mattm/archive/2008/06/12/use-32bit-runtime-option-for-sql-agent.aspx 2- if you have sql 2005 ....http://msdn.microsoft.com/en-us/library/ms162810.aspx the section that says ... <drive>:\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn you have to use the 32bit DTExec.exe and maybe you will need to use PROXY users.Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

ArthurZ - I will try changing the SQL Agent to use my login to see if that makes any difference. Thanks for the suggestion. Nik - It is an XML file.

Hi MrKrabs I think that ArthurZ is right can you tell us how you are calling the package through the SQL job , what are the settings? Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

I added a step to call the SSIS package which is set to rely on server storage. I run as the sql agent account and change no other settings. Are there settings I should be changing on the SSIS step?

The SQL Agent execution account has permission to msdb or SSIS File System folder (where you've imported packages)?Vctor M. Snchez Garca (ES) (BI) Hope this help. Please vote if you find this posting was helpful. if this is an answer to your question, please mark it. http://bifase.blogspot.com | http://twitter.com/atharky

I added a step to call the SSIS package which is set to rely on server storage. I run as the sql agent account and change no other settings. Are there settings I should be changing on the SSIS step? Once you mention that you call the package (file base) and it working and now you are saying that its a SQL Based package, see http://www.mssqltips.com/tip.asp?tip=1775 i think this may be what you are looking for and also check http://www.mssqltips.com/tip.asp?tip=1180 http://decipherinfosys.wordpress.com/2008/09/17/scheduling-ssis-packages-with-sql-server-agent/ http://msdn.microsoft.com/en-us/library/bb986815(MAG.9).aspx and you may need http://support.microsoft.com/kb/918760Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Nik - From my original request: "I imported the package to SQL 2005 sp2 with "rely on server" protection level." I am using method #2 from the kb article you linked. Arthur - The user has full access to the folder where I'm trying to write the files. I just tried granting sqlacct3 sysadmin rights and then running the job, but get the same error. SqlAcct3 is a local administrator of the server as well.