I have been reading around for about 2 weeks now and i still can't figure this out. I have 4 SSIS packages that i need to run via the SQL agent. In the past they worked, we then migrated our external data to a new database. I changed the SSIS connection to point to a new database and tried to run them. 2 of the 4 run without an issue. The other 2 fail at validation even though they have the same connection manager setup. This is on a 32bit SQL 2005 server with the latest service pack (i have even disabled the Run64BitRuntime just in case). The data is being pulled from a progress database using the v10 OpenEdge ODBC driver. Im baffled as to why 2 of the packages work without any issue whatsoever but the other 2 won't. I have deleted a re-created the system DSN multiple times also and tested and re-tested the connection. I have gone over the configuration of the SQL jobs and the SSIS configuration it seems like hundreds of times now, i have taken screen shots and compared the working to the non-working and tried various configurations and im still lost. Here is the error message i get from one of the logs. Any help here would be great and im starting to loose my hair. I have picked this up from a previous employee, not having any experience in the past with SSIS it's been a sharp learning curve, i have managed to make new packages and edit old ones. Just not get these workings. Microsoft (R) SQL Server Execute Package Utility Version 9.00.5000.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:50:16 AM Error: 2011-07-07 11:51:18.80 Code: 0xC0047062 Source: buyrmstr_transfer pms_buyrmstr [22] Description: System.Runtime.InteropServices.COMException (0x80131937): Exception from HRESULT: 0x80131937 at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) End Error Error: 2011-07-07 11:51:18.80 Code: 0xC0047017 Source: buyrmstr_transfer DTS.Pipeline Description: component "pms_buyrmstr" (22) failed validation and returned error code 0x80131937. End Error Error: 2011-07-07 11:51:18.82 Code: 0xC004700C Source: buyrmstr_transfer DTS.Pipeline Description: One or more component failed validation. End Error Error: 2011-07-07 11:51:18.82 Code: 0xC0024107 Source: buyrmstr_transfer Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:50:16 AM Finished: 11:51:18 AM Elapsed: 62.516 seconds

Since you get a validation issue I guess the metadata has changed. Can you drop and re-create the buyrmstr_transfer component? If the issue presists, re-create this package anew.Arthur My Blog

Sorry i forgot to mention i can run the package fine via BIDS. Any time the buyrmstr_transfer component runs the target table get's dropped and re-created. There are about 20 components in this particular package, i tried disabling the buyrmstr_transfer component and the exact same error happened on the next component. All components drop their target table and re-create it before importing data (we have no use for the previous weeks data). This is the same on the working packages.

How do you run your packages outside the BIDS (when the issue occurs)?Arthur My Blog

We have jobs setup in SQL 2005 SQL Job agent. These have always been there. I have script's that start them using DTexec but i also right click and run them if i need to, both methods fail.

Check this http://support.microsoft.com/kb/969845-------------------------------------------------------- Surender Singh Bhadauria

How did you deployed the package? what did you set as protectionLevel? set it as EncryptSensitiveWithPassword, then apply password whenever you want to run it. http://www.rad.pasfu.com

Thanks, i currently have it set as EncryptSensitiveWithPassword. These packages were created and deployed before i started in this position. I simply changed the data source to the new database and that's when the trouble started. 2 of the packages work fine and 2 don't. Im going to try the suggestions given in the link Surender Singh Bhadauria.

what is authentication types? sql authentication? windows authentication?http://www.rad.pasfu.com

Do you mean within the package or the authentication type of the SQL Job??

Do you mean within the package or the authentication type of the SQL Job?? I mean the connections inside the package? did you connect to sql server db? if yes, sql authentication? or windows authentication?http://www.rad.pasfu.com

*slaps forhead* I seem to have fixed the issue. Within the SQL job under the connections tab the connections available in the package were checked. I unchecked these and they now work :/ Not sure why this is the case but it is. Sorry for wasting your time and thanks for the help.

*slaps forhead* I seem to have fixed the issue. Within the SQL job under the connections tab the connections available in the package were checked. I unchecked these and they now work :/ Not sure why this is the case but it is. Sorry for wasting your time and thanks for the help.