v7.3 error - "Microsoft.OLEDB.12.0 not registered on machine" when getting CSV text as collection

[MelissaNail]

Upgraded from 7.1.2 to 7.3; 32-bit to 64-bit. Was originally getting error for Microsoft.Jet.OLEDB.4.0 but updated current VBOs with actions from Digital Exchange VBO's. We are using installed versions of 2015 Office and they are 32-bit. Access data base engine is on the server and all other aspects of office are working during regression testing. Do we need to install 64-bit versions of office to make this work or am I missing a step? Any help is greatly appreciated! 

[harish.m]

HI Melisa Nail,

Did you get chance to check below thread

https://community.blueprism.com/t5/Product-Forum/Blue-Prism-v7-2-1-v7-3-New-64bit-VBOs-OLEDB-and-File-Management/m-p/93151#M42784

[MelissaNail]

I did but the referenced post has to do with the vbo’s and Office 365. Unfortunately, updating our file maintenance and OLEDB vbo’s did not resolve the error.

[LeonardoSQueiroz · Accepted solution]

Hello Melissa,

Check this topic in the knowledge base, the problem is not exactly the same but it is similar, it may be related:

https://support.blueprism.com/en/support/solutions/articles/7000085047-bpe-error-the-microsoft-jet-oledb-4-0-provider-is-not-registered-on-the-local- machine-when-using

Regards,

[MelissaNail]

Your link led to our resolution. I had tried to install the 64-bit but got an error since my Office is 32-bit. There was actually another article listed under related that told me to install the 32-bit before the 64. That did the trick. Thank you so much for your help!!

https://support.blueprism.com/en/support/solutions/articles/7000085434-bpe-error-the-microsoft-jet-oledb-4-0-provider-is-not-registered-on-the-local-machine-when-using-the-utility-file-management-vbo-...