Hi, I developed a SSIS package on Visual studio 2008 ( BIDS). My package runs absolutely fine from BIDS. I am populating SQL Server 2005 tables. However when I deploy my package on the SQL server 2005 I get the below error : Executed as user: ...sion 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:23:26 PM Error: 2012-08-06 22:23:26.53 Code: 0xC001700A Source: Description: The version number in the package is not valid. The version number cannot be greater than current version number. End Error Error: 2012-08-06 22:23:26.56 Code: 0xC0016020 Source: Description: Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.". End Error Error: 2012-08-06 22:23:26.56 Code: 0xC0010018 Source: Description: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS:Property>" from node "DTS:Property". End Error Could not load package "... The package could not be lo... The step failed. I did research about this and I get to know that : This happens when we try to run the SSIS 2008 package on SQL 2005 machine ( server). This machine that I am running SSIS 2008 package on does NOT have SQL 2008 BIDS installed. Please advice as to what I need to do inorder to run the package on SQL 2005 server machine? Are there any workarounds ? Thanks, EVA05

Hi Eva05, Indeed, you developed your package using SSIS 2008 and try to run in SSIS 2005 environment, this is why it does not work. The workaround is in either installing SQL Server 2005 shared (development tools), or you can try using the package downgrade utility from CodePlex called SSISDowngrade (do not like the name) http://ssisdowngrade.codeplex.com/Arthur My Blog

Hi, I understand that package is developed using SSIS 2008 and I am trying to run in SSIS 2005. I tired using the package downgrade utility from CodePlex called SSISDowngrade but still I do get error on the 2005 Environment: Executed as user: DS1\ds1sqlsvc. Microsoft (R) SQL Server Execute Package Utility Version 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:53:43 AM Error: 2012-08-07 00:53:45.47 Code: 0xC00470FE Source: DFLT -CSV Load to stage DTS.Pipeline Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Flat File Source" (16). End Error Error: 2012-08-07 00:53:45.50 Code: 0xC00470FE Source: DFLT -CSV Load to stage DTS.Pipeline Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Add-ETL Control ID" (135). End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:53:43 AM Finished: 12:53:45 AM Elapsed: 1.89 seconds. The package execution failed. The step failed. It seems the version of SSIS cannot cope up with the downgraded dtsx files either. ANOTHER option I tired is running the package on SQL2008 server. When I try to run the package on SQL 2008 server I get the following error : Message Executed as user: DS1\eHub. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 12:23:57 AM Error: 2012-08-07 00:24:04.66 Code: 0xC0202009 Source: LT_Unsubscribe_Leads Connection manager "cm_LT" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'DS1\eHub.". End Error Error: 2012-08-07 00:24:04.80 Code: 0xC0202009 Source: LT_Unsubscribe_Leads Connection manager "cm_LT" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'DS1\eHub'.". End Error Error: 2012-08-07 00:24:05.16 Code: 0xC0202009 Source: LT_Unsubscribe_Leads Connection manager "cm_LT" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'DS1\eHub'.". End Error Error: 2012-08-07 00:24:05.22 Code: 0xC00291EC Source: SQL-Start Process Execution Execute SQL Task Description: Failed to acquire connection "cm_LT". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:23:57 AM Finished: 12:24:05 AM Elapsed: 7.36 seconds. The package execution failed. The step failed. I guess the SQL Agent account that I am running on SQL 2008 server does not have enough permission to access the SQL Server 2005 ( server and database ). Is it possible to run the package on SQL 2008 server accessing the SQL 2005 (server and database) since my package is developed in SQL 2008 BIDS ? In that case how can I give access to the SQL Job account to access the SQL 2005 ( server and database ) ? OR Do I need to re-create the package using SSIS 2005 and deploy on the 2005 server ? Please advice Thanks, EVA05

The 1st error tells me you did not install the correct edition of SQL Server e.g. SQL Express. Check the version of SQL Server 2005 installed. it is also possible that you do not have the SSIS installed, or it was improperly un-installed. The 2nd issue needs to be resolved by granting the proper rights to DS1\eHub or running the SSIS job step using a proxy that has the needed privileges. You can run the SSIS 2008 package accessing the SQL Server 2005 no problem and the answer is in the sentence above. To run a package in SSIS 2005 you need SSIS 2005 installed and created in BIDS 2005/VS2005Arthur My Blog

Thank you for the prompt response. I guess it is appropriate to set up a jon on SQL 2008 machine to access data from SQL 2005 since I have built the package in SSIS 2008. What I did is created a SQL Server Authentication (Login and Password) to access the SQL 2005 server and database. I will supply these credentials when I set up a job on SQL 2008. But before that when I try to test using the SQL Server Authentication ( changed the connection manager to use the SQL Authentication- entered the login and passoword, the password does not get saved) in BIDS my package give the error : Login failed for user 'Mark' My package protection level is set to : EncriptSensitivewithuserkey I also created a package configuration -using SQL Server Table - stores connection string, login and password. I am trying to use package configuration while I run the package from BIDS - I still get the login failed for user error. What steps I need to follow inorder to run the package in BIDS AND SQL Agent job on server with SQL Authentication on connection Manager without getting login errors ? Please advice Thanks EVA05

Eva05: if you are accessing the SQL Server 2005 from a package you just need to set a connection manager to it. There will be no relation to the SQL Server 2008 or any other, just access the needed target, this is why we have connection managers. Now, it is important how you set it, with SQL authentication it must work, and while you are in BIDS the EncriptSensitivewithuserkey will work, and even when you are logged in on the server with your account it will, alas, it will fail if a different account will attempt to run your package (typically after you set to run in an automated way). So the Agent job must not run a package saved with  EncriptSensitivewithuserkey. Typically, rely on server for storage mode is used when deoloying, the SQL account must log in just fine. The Connection Manager suppose to save whatever you enter, this is a security issue accesing your DB. Nothing else. So make sure this SQL account can indeed access your DB say when you test in SSMS. Arthur My Blog

Thank you ArthurZ for the resposne. 1. I did create the job successfully using the SQL Authentication to SQL 2005 and am able to run the package from BIDS as well as SQL 2008 server. 2. I created an XML config file to store the password and use this config file. 3.However the requirements is to use the SQL server package configuration. I did create a SQL configuration table: The connection string property is set to : \Package.Connections[cm_LT].Properties[ConnectionString] Data Source=ARTDB01;User ID=mark;Initial Catalog=PROS_DATA;Provider=SQLNCLI10.1;Persist Security Info=True;Auto Translate=False;Application Name=SSIS-LT_Unsubscribe_Leads-{3E934E8B-A32D-4B8F-9343-ED45E3E9B064}ARTDB01.PROS_DATA; I was getting the login failed error so I changed the connection string property on SQL table to : Data Source=ARTDB01;User ID=mark;Password=Password;Initial Catalog=PROS_DATA;Provider=SQLNCLI10.1;Persist Security Info=True;Auto Translate=False;Application Name=SSIS-LT_Unsubscribe_Leads-{3E934E8B-A32D-4B8F-9343-ED45E3E9B064}ARTDB01.PROS_DATA; But it still throws the error Login failed for user Mark Additionally I have included following properties ( I have updated Password in the Passowrd property as well but to no success) \Package.Connections[cm_LT].Properties[UserName] \Package.Connections[cm_LT].Properties[ServerName] \Package.Connections[cm_LT].Properties[ProtectionLevel] \Package.Connections[cm_LT].Properties[Password] \Package.Connections[cm_LT].Properties[Name] \Package.Connections[cm_LT].Properties[InitialCatalog] \Package.Connections[cm_LT].Properties[ConnectionString] I want to use the config table instead of dtsconfig file. What changes I would need to make inorder for the package to get the connection properties ( userid and password ) from SQL table? Please adivice. ThanksEVA05

It is possible that the config file or table cannot be accessed, so the config setting is not being applied as for that you should see a warning in the log. If the config table is not read the design time settings get applied instead, thus the error. Make sure the package connects to the config db using the correct conn string.Arthur My Blog

Thank you for the guidance. I was able to run the package from the SQL 2008 server using the sql authentication to SQL 2005 and using SQL table configuration. Earlier my config table was located in SQL 2005 and as a result it was throwing error for login failed for user. As soon as I moved the SSIS config table to SQL 2008 I was good. EVA05

Excellent news! Please do not hesitate to always come back to our forum with any issue or question.Arthur My Blog