Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dmaxj
Posting Yak Master
174 Posts |
 Posted - 2010-05-19 : 21:20:48
|
| I am perplexed as to why my package runs perfectly from Visual Studio, but it fails to execute from the SQL Server. The first error that shows up during Package Execution Process dialog box is:Error: SSIS Error Code DTS_E_CANNOT ACQUIRE CONNECTION FROM CONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.Regards |
|
|
iansdigby
Starting Member
1 Post |
Posted - 2010-06-15 : 06:21:28
|
| Hello fellow perplexed person. I have a similar problem when importing from MS Access, with the database protected with an mdw file. Can run perfectly from VS 2008 BDS, but when installed as an SSIS package it will not run as a job from SQL Server Agent. I get the same error message."Let the religions agree and make the nations one..." |
 |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-06-15 : 06:34:06
|
Visual Studio is running on your client.A job is running on your server.Maybe there are different versions regarding Connection Manager?
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
|
|
|
package works from VS but not on SQL Server