Would someone try the following and post your result?

I have a simple SSIS Package with a Source Excel Connection Manager and a Flat File Destination Connection Manager. The package executes successfully until I add a Package Configuration of type XML File. When configuring the package configuration file, I chose the two connection managers (all properties) and left everything else (variables, properties, log providers and executables) unchecked.

After adding this package configuration of type XML file the package fails with the error message "The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.:"

I went back into the package configuration and unchecked the "Initial Catalog" property of the Excel Connection Manager and re-ran the package and it succeeded. I went back into the package configuration and checked the "Initial Catalog" property and it failed with the "AcquireConnection method" error mentioned above.

Does this occur for anyone else out there Thanks in advance for trying it out.

Answer this question

Would someone try the following and post your result?

Wayne Sepega
Thanks Doug. I did post this to BetaPlace on 8/15/2005. No reponse as yet. If and when I do get a response (or better yet a solution!) I will update this thread.

-Steve
tyron

Steve Wenck wrote:
FYI. Microsoft BetaPlace responded with this "resolution":

"This is currently expected behavior".

!@#$%^&*

Well that's true. it simply isn't relevant.

Why not just uncheck it so it isn't in your config file

-Jamie
MarcioJAS
There isn't a valid value for Initial Catalog with Excel, where a Data Source (workbook) does not contain multiple Catalogs (databases) but represents a single catalog in which the worksheets and ranges represent tables.

I assume that this item is showing because the Excel connection is, underneath, really an OLE DB connection where we're preconfiguring certain properties for you to connect to Excel. Initial Catalog is, as you know, a standard OLE DB connection string item that's simply not applicable to Excel or, for that matter, to Access or other data sources for which the Jet database engine and Jet OLE DB Provider are used.

It may be that there's no way to hide this unneeded connection string property, or it may be that no one has noticed this before.

As I mentioned in another posting, your options for reporting bugs or requests are sqlwish@microsoft.com and the BetaPlace bug filing process http://msdn.microsoft.com/sql/bugs/default.aspx.

Best regards,

-Doug
Joshua07
FYI. Microsoft BetaPlace responded with this "resolution":

"This is currently expected behavior".

!@#$%^&*
vatsug
Steve

I did follow your instructions end to end and managed to replicate the error. As you mentioned, if I uncheck Initial Catalog the package works fine. I have noticed the value for Initial Catalog is empty. Is that something to do with this

Thanks

Sutha
Julian Ladbury
Thanks for verifying this for me, Sutha. Yes, I noticed that this property is empty as well. I haven't been able to determine what might be a valid value for the Initial Catalog property of an Excel Connection Manager
Shaan Rathi
Deep breath...

I have done so, Jamie. My feeling though is if it is not relevant why is it even configurable not to mention why would it cause a package to fail A lot of time was wasted on finally figuring out what was causing these packages to fail.

Ah well...all in all a minor issue....back to SSIS - an unbelievably awesome tool.
Would someone try the following and post your result?

Answer this question