Tuesday, March 20, 2012

Data Reader Source cannot be configured

Hi,

I am using a Ado Connection Manager to connect to a M S Access source.

But when I use this connection Manager in Data Reader Source, I am Not able to Configure Data reader Source. It gives exception "Cannot Acquire Managed Connection From Run Time Connection Manager".

Can anyone help on this.

Thanks

Dharmbir

Wenyang,

The .mdb Does not matter, If I create a ADO Connection Manager, Data Reader Does Not Support.

Thanks

Dharmbir

|||I have new Integration Services Project in Microsoft Visual Studio version 8.0.50727.42, under .NET framework version 2.0.50727. I'm trying to set up a simple replication from an ODBC data source to a new MSSQL 2005 database. I created two entries in the Connection Managers list and successfully tested the connection for each one.

I see the same "Cannot acquire a managed connection from the run-time connection manager." error after setting the Connection Manager in a DataReader Source object's Advanced Editor dialog box to either entry in Connection Managers. The DataReader Source appears to be the only Data Flow Source that will allow me to connect to an ODBC datasource.

Is there a log somewhere or a list of possible reasons for this inability to connect? Does Visual Studio allow for the creation of a package that uses a non-managed connection?

Also, I made a data source for each of my connection managers in the Data Sources folder of my project. Are they necessary?

Thanks for any help you can give us.|||

It works for me fine. There are a couple things to check

1) You used ".Net Provider for OleDb/Microsoft Jet 4.0 OLEDB Provider", correct?

2) When you created your ADO.Net connection, did you set username/passwd correctly - did "Test Connection" return success?

Thanks

Wenyang

|||

Hi Wenyang,

1.) I used ADO\Microsoft Jet 4.0 OLEDB Provider

2.) Test connection shows its passed.

Thanks

Dharmbir

|||

If picking which .mdb file does not matter the repro, please pass me a small sample mdb which failed for you and I'll try to see why we saw different results. Pls send to Wenyang.Hu at Microsoft.com

Thanks

Wenyang

No comments:

Post a Comment