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 |
|
sqldba20
Posting Yak Master
183 Posts |
 Posted - 2007-10-24 : 09:34:26
|
| I migrated a few stored procedures from SQL 2000 to SQL 2005. When the packages are run from the box where the SSIS and SQL Server (Windows server) is installed it is running fine without any issues. When run from my local machine (client) where I have installed the SQL Server Client, the same package would not execute and gives me some weird error messages. I am a local admin on the box. Is this a issue with SSIS? Do we have to log onto the box (server) and then execute the packages?Any help is appreciated.Thanks ! |
|
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2007-10-24 : 11:41:41
|
| Do you have SSIS installed on the client? Can you post the error message you're getting? |
 |
|
|
sqldba20
Posting Yak Master
183 Posts |
Posted - 2007-10-24 : 12:41:47
|
| Failed to acquire connection "Microsoft OLD DB Provider for SQL Server". Connection may not be configured correctly or you may not have the right permissions on this connection.As far as SSIS is concerned, on my client I have installed the SQL 2005 Client and has all installed. The SSIS server service will be on the server. |
|
|
|
sqldba20
Posting Yak Master
183 Posts |
Posted - 2007-10-24 : 13:45:09
|
| My Apologies: The Correct Error is:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Connection 1" failed with error code 0xC0202009. There may be error messages posted before this with on why the AcquireConnection method call failed. Error: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. |
|
|
|
|
|
|
SSIS Packages Not getting executed from Client.