I developed an ssis package on windows xp with visual studio 2008. I'm trying to deploy it to a windows 2008 r2 stnd server 64bit running sql server 2008 r2. I copy over my deployment folder to the server and double click on the integration services deployment manifest file. the goal is to deploy the package to the local server and set up a sql server agent job to run the package at a set time each day. i go through the ssis package install wizard: 1. sql server deployment and check validate package after install 2. server -local, use sql auth and select to use the SA account for now; package path: ssispackage/datacollector/myfolder 3. install folder: C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Packages\myPackageSSIS The Package validation show errors in order: 1. error ssis error code dts_e_cannotacquireconnectionfromconnectionmanager. the acquireconnection method call to the connection manager 'destinationconnectionoledb failed with error code 0xc0202009. there may be error messages posted before this with more information on why the acquireconnection method failed. 2. error: component desitnation- mydata (34) failed validation and returned error code 0xc020801c. 3. error one or more component failed validation 4. error there were errors during task validation 5. error ssis error code dts_e_oldedberror. an ole db error has occurred. error code 0x80040e4d. an olde db record is available. source: microsoft sql server native client 10.0 hresult: 0x80040e4d description login failed for user 'myuser' I'm not sure why this fails. I'm logged onto the server as the local administrator. set myuser as a local sql admin. Any suggestions?

You package is not able to get the connection specified. Try these Modify the connection string to specify a provider that is supported. For more information about supported providers, see the documentation that comes with SQL Server Upgrade Advisor. Verify that you have the correct permissions to use SQL Server Agent to run the package. For information about how to troubleshoot packages that are run from SQL Server Agent jobs, see the Microsoft Knowledge Base article, An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step. Verify that you have access to the specified data source. Verify that another application is not using the specified data source. Modify the configuration file of the package to include the password that SQL Server Authentication requires. To modify the configuration file to include this password, run the Package Configuration Wizard, which will export the PackagePassword property of the package to the configuration file. Ashwani Roy Blog Twitter Please click the Mark as Answer button if a post solves your problem!

Your connection manager is not working in your production machine while it's good in your develop machine. Connection Manager has a property ConnectionString. Please check the ConnectionString is still working in production machine. Suggest you read the document if you haven't: http://technet.microsoft.com/en-us/library/cc966389.aspx#XSLTsection126121120120 It summaries: SSIS enables you to create configurations for packages that allow the packages to flexibly adapt to different run-time conditions. This summary is because many customers meet problems that their develop machine has different setting with production machine. So after deployment, the connection string are not working. They are using "Configuration" to solve the problem.

Have you developed the package with the package protection of EncryptSensitveWithUserKey? If you are deploying with a different username to the one you developed with, the sensitve elements of the package won't be able to decrypted. Try using EncryptSensitiveWithPassword which you will pass when deploying the package. http://msdn.microsoft.com/en-us/library/ms141747.aspxevery day is a school day