cancel
Showing results for 
Search instead for 
Did you mean: 

How to Connect MS Access DataBase in Blueprism

KarthikGanesh
Level 3
Hi All,

I tried to connect MS Access DB with Blueprism but it throw an error for your reference I listed the error's below

I tried with Provider ="Microsoft.Jet.OLEDB.4.0" it throw an Error:- Internal : Could not execute code stage because exception thrown by code stage: Unrecognized database format 'C:\ABI Automation\MICS Reporting Automation\Input\MICS_Input.accdb'.

for the Provider="Microsoft.ACE.OLEDB.12.0" it throw an Error:- Internal : Could not execute code stage because exception thrown by code stage: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.

for the Provider= "MSDASQL.1"  and Connection String ="Provider=MSDASQL.1;Persist Security Info=False;Extended Properties="DSN=MS Access Database;DBQ=C:\ABI AUTOMATION\MICS REPORTING AUTOMATION\INPUT\MICS_Input.accdb;DefaultDir=C:\ABI AUTOMATION\MICS REPORTING AUTOMATION\INPUT;DriverId=25;FIL=MS Access;MaxBufferSize=2048;PageTimeout=5;UID=admin;" it throw an Error;-  Internal : Could not execute code stage because exception thrown by code stage: 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).

Kindly help me with this to resolve the issue.

Thanks in advance.


------------------------------
Karthik Ganesh
------------------------------
13 REPLIES 13

Hi,

Be sure that you have correctly install the AccessDatabaseEngine. Find the official installation here.

The connector of Blue Prism is using the library "System.Data" and "System.Data.OLEDB", so... the real problem here is that the System is not recognize the Provider. Try it installing the correct version


Bye :)

------------------------------
Pablo Sarabia
Architect
Altamira Assets Management
Madrid
634726270
------------------------------

ewilson
Staff
Staff
@KarthikGanesh,

There's lots of suggestions here. Hopefully this will clarify some of it:
  • ​There is no standard Blue Prism VBO specifically for MS Access that I'm aware of. I'm guessing the Data - MS Access VBO shown above is something they developed themselves or found at another location.
  • There are two VBOs available on the DX, and included in the standard BP install, that could be used to connect to MS Access. They are the Data - OLEDB VBO and the Data - ODBC VBO. The one you use governs which support files you'll need to install from Microsoft.
    • For Data - OLEDB, you want to use the Microsoft Access Database Engine 2010 Redistributable  (NOTE: There are 32-bit and 64-bit versions of the driver installer in this download. You probably want to install the 32-bit version since Blue Prism is a 32-bit client).
    • For Data - ODBC, you've probably already got the necessary driver installed. You can check this by going to Start -> Run and typing ODBC. You should see options for the 32-bit and 64-bit ODBC Data Source Administrator utility. You want the 32-bit version. When that comes up, you should see an entry under the User DSN tab for MS Access Database. Now, if you want to use ODBC you'll have to configure either A User DSN or File DSN.
  • Beyond the above, you have to have the correct Connection String defined. The Connection String you show in your screenshot suggests you're trying to use the ODBC provider to connect to your Access database. If that is the case, you need to use the Data - ODBC VBO. If you want to use the Data - OLEDB VBO, you need to change your Connection String to reflect that. It will look something like this:

"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=[YOUR DATABASE FILENAME AND PATH];"

There could be more properties depending on how your database file is configured (ex. username and password).

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

Hi Eric and Pablo, thank you for your answers.
This helped me to understand the problem, I still have to find my way to the solution, but the first step is done.
I explain: I can't install any packet on my machine, nor on the ones that runs the robots.
Since some days ago all worked well, probably - as all machines are remotely administered - a system update drops the 32 bit libraries leaving only the 64 ones. 
I still have an environment where the OLEDB is found (and all production machines are working), but I think I have to address the issue.

Thank you,
     marco

------------------------------
Marco Oreste Pogliaghi
------------------------------

Hi,

This is not the first time that any windows update ruins the Access connector. I don't know the KB code of the update that may cause this, but, if you can, try to go back this update just to test.


Bye :)

------------------------------
Pablo Sarabia
Architect
Altamira Assets Management
Madrid
634726270
------------------------------