ODBC Connect string Problem (Oracle)

(0) Share

Report

Posted on by Yongmin

Hi. First I'm sorry to my english 😞

I made ODBC Original Data. and Testing was successed.

zxcvn;lxzcjv;lxzcjv;xzcvj.PNG

so, I try Open SQL CONNECTTION in PAD. but i can't

I Choose 'Microsoft OLE DB Provider for ODBC Drivers' and my connect test is success.

Here is my pad connect state

Language is Korean, but that means 'connect test success'

anyway , next i Clicked confirm button and

i get the connection string this.

Provider=MSDASQL;Password=hr;Persist Security Info=True;User ID=hr;Data Source=Test_Conn_2

and I Run PAD but Error was occurred.

Here is my pad error message.

The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).: Robin.SDK.ActionException: Connection string isn't valid ---> System.ArgumentException: The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).
at System.Data.OleDb.OleDbConnectionString.ValidateProvider(String progid)
at System.Data.OleDb.OleDbConnectionString.ValidateConnectionString(String connectionString)
at System.Data.OleDb.OleDbConnectionString..ctor(String connectionString, Boolean validate)
at System.Data.OleDb.OleDbConnectionStringBuilder.GetProviderInfo(String provider)
at System.Data.OleDb.OleDbConnectionStringBuilder.TryGetValue(String keyword, Object& value)
at Robin.Modules.Database.Actions.DatabaseActions.OpenConnection(Variant connectionString, SqlConnectionVariant& connection)
--- End of inner exception stack trace ---
at Robin.Modules.Database.Actions.OpenConnection.Execute(ActionContext context)
at Robin.Engine.ActionRunner.RunAction(String action, Dictionary`2 inputArguments, Dictionary`2 outputArguments, IActionStatement statement)

I think provider is problem but i dont know well.

my pc state

Win10

Oracle 12C 12.2.0

oracle 12c client.

So...What should i do?

please help me...

Categories:

Power Automate Desktop

I have the same question (0)

All responses (6)

Answers (0)

NikosMoutzou Microsoft Employee on at

Like (0)

Report

Hello @Yongmin !
The issue seems to be related to the connection string that you are using. The action uses the ADO .NET database component , which does not support the MSDASQL provider. In order to handle this, you have to alter your connection string.

Was this reply helpful? Yes No
r96359 228 on at

Like (0)

Report

What is the recommended connection string for Oracle when you have a successfull 64bit ODBC driver set up as a System DSN but you get this error?

Was this reply helpful? Yes No
swoods87 4 on at

Like (0)

Report

I'm having the same problem on version 2.18.146.22083. Test connection is successful, but I get the same failure message when attempting to run the flow. What should the connection string be altered to?

Database.Connect ConnectionString: $'''Provider=MSDASQL.1;Password=password;Persist Security Info=True;User ID=user;Data Source=src''' Connection=> CONN

Was this reply helpful? Yes No
VJR 7,635 on at

Like (0)

Report

You can check out and try connection strings for Oracle here.

Was this reply helpful? Yes No
swoods87 4 on at

Like (0)

Report
Thanks for that. I did try multiple variations of the connection strings to no avail. I believe the issue is when I open the Data Link Properties dialog box, I only have OLE DB Providers (see screenshot below). The failure message returned by Power Automate indicates that:

The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).

So I'm assuming my problem is either:

I need to install an ODBC DB Provider and have it visible/selectable in the Data Link Properties dialog box.
Power Automate is selecting the incorrect .Net Framework when Microsoft OLE DB Provider for ODBC Drivers is selected and the connection is being built at run time.
To me, this error seems most likely given that I get a Test connection succeeded response in the Connection tab using this same provider.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi all,

Does anyone find a way to fix this problem? I don't know how to Use the .Net Framework Data Provider for ODBC to get rid of this problem

Was this reply helpful? Yes No