Re: SSIS, Excel & Package Configurations.
- From: adolf garlic <adolfgarlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Apr 2007 08:22:01 -0700
I'm getting the 0xC020801C (cannot aquire connection) error when trying to
open an xls too.
I've got the 64bit thing set to false (even though we aren't using 64bit)
I'm not using any passwords or encryption.
Did you find a solution?
You mention a configuration file, when I inherited this package, the config
file had gone awol (as in dtsconfig), could this be causing my problem and if
so how do i create a new file?
"Simon Sabin" wrote:
Hello Garrett.
Has the setting in the configuration file been set correctly?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
Hi Garrett
I have just built a package with the exact same details as your post
and I do not get the error. The error suggests it cannot get a
aconnection to your XL File. This however would be true regardless of
whether or not you used Configurations.
--
Allan Mitchell
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com
"garrett.fitzsimons@xxxxxxxxx" <garrett.fitzsimons@xxxxxxxxx> wrote in
message news:1173184708.658114.102370@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:
I have a SSIS package that loads the contents of a work*** in an
Excel document into a table.
Simple process;
1) Extract from Excel using Excel Connection Manager 2) Insert into
SQL2005 Database Table using OLEDB Connection Manager.
I am using ExcryptSensitiveWithPassword and have set a password on
the package.
The Package works fine until I enable Package-Configuration for the
Connection Managers.
If I check the checkbox for Excel-Connection-Manager and save the
package-configuration-file then I get an error message;
Error: The AcquireConnection method call to the connection manager
"Excel Connnection Manager" failed with error code 0xC0202009"
I can reproduce this at will by switching the checkbox on/off and
saving the configuration file.
This is all done on a standalone Notebook running SQL2005.
Can anyone explain the levels of security/configuration at play here
?
It would seem that there is a complex relationship between the
'Protection Level' and the 'Package Configuration' - one I cannot
find a sufficient explanation for.
Can anyone add to this ?
My goal is to have a package that can be easily ported from server to
server, and will allow an admin person to modify the path to the
excel file.
Many Thanks.
- Prev by Date: sleep function in DTS
- Next by Date: How to export from SQL Server to multi-record text file
- Previous by thread: sleep function in DTS
- Next by thread: How to export from SQL Server to multi-record text file
- Index(es):
Loading