We are facing an issue with the Microsoft Text Driver connection after the Windows migration.
In the legacy environment, the Microsoft Text Driver was working fine. However, after migrating to the Windows code the connection is failing due to a 64-bit compatibility issue.
We have already installed the 64-bit Microsoft Access Text Driver, but the connection to the database is still failing. The error message we are receiving is: “Value cannot be null. At least one connection must be used.”
Requesting your support to help resolve this issue.
Can you please specify the activity you are using?
Generally this error comes when some required value is left empty so please check on the same usingb debug mode..during conversion some variables might be lost or recreating the activity or variable can help
Try to Install the 64-bit Microsoft Access Database Engine, use the 64-bit ODBC Data Source Administrator, and update the connection string to use - Microsoft.ACE.OLEDB.12.0. Ensure UiPath is running in 64-bit mode. The error “Value cannot be null. At least one connection must be used.” indicates a missing or misconfigured connection string.
I’m using the Connect activity to configure the connection string and provider name. However, the Connect activity is failing to connect with the driver, which is why the Execute Query activity is throwing a ‘Value cannot be null’ error.
The first thing I would suggest is an update to Database 1.10.0 (just to rule out any bugs that might have been fixed in the meantime).
Then, I would double-check the connection string and the provided set in the Connect activity. Are you maybe using a pre-configured DNS in your connection string, and that DNS is referring to the 32-bit driver?
If possible, it would help if you could share your connection string without the sensitive information (please mock up any sensitive info).