SSIS package wont run

Hello there,

I have a SSIS 2008 project with  2 packages and everything is working perfect on my machine. Now I want to take these packages and deploy them on another server(production). I right click on the Control Flow tab of the package and select Package Configuration and in there I select the 2 Connection Manager(I have 2 db hence 2 connection managers) checkbox. Now when I try to run the package on my machine again after going through this Package Configuration, I am not able to run my pacakge again. The error I get is

TITLE: Package Validation Error

Package Validation Error


Error at Data Flow Task [OLE DB Source [1]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "LocalHost.pooyeshtest.test" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Error at Data Flow Task [SSIS.Pipeline]: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.

Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

Error at FDOAvailPkg [Connection manager "LocalHost.pooyeshtest.test"]: 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 'test'.".




Open in new window

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vikas GargAssociate Principal EngineerCommented:

In your configuration which one you are using

If you are using XML configuration that at the production server you have to modify the value of both connection managers as per the production connection strings.

Currently the configurations will be having your database connection strings which will not work on production.

Here is the Sample Url on configuration usage..

Hope this will guide you.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
zolfAuthor Commented:
Thanks for your comments.

In your configuration which one you are using

I am using my machines configuration. I did not edit any of those parameters.

Currently the configurations will be having your database connection strings which will not work on production.
But I did not change any values there, but when i try to run my pacakge on my machien I get this error. But when i delete that configuration file then I am able to run the package again. What is going on...what am i missing.please help!!
zolfAuthor Commented:
Why I cannot delete these packages ??

zolfAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.