ODBC to Access Database no longer works after update to On-Prem gateway

[agneum]

I've updated the On-Prem gateway to the april version. And now my connection to MS Access DB says this:

Received error payload from gateway service with ID 33332: ODBC: <ccon>ERROR [HY000] [Microsoft][ODBC Microsoft Access Driver] Your network access was interrupted. To continue, close the database, and then open it again. ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [01S00] [Microsoft][ODBC Microsoft Access Driver]Invalid connection string attribute Trusted_Connection ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed ERROR [01S0...</ccon>.

[agneum]

It works if I connect to Power BI desktop, but as soon as I try to publish the report and create a conection on the On-Premises data gateway, it does not work, even though the connections seem fine.

I read this might be some issues related to access to registry keys, but not sure which permissions are needed for the Power BI service/gateway

[agneum]

The Microsoft Access database is in a fileserver that the on-prem gateway has access to. What exactly constitutes the a connection as trusted?

[Pragati11]

Hi @agneum ,

Have you checked your connection details that you are using to access the database?

The error seems to mention that the connection can't be identified as a trusted one.

Please check if something has changed on the database side recently for connecting to it.

You can also try connecting to this database directly but not from PBI Desktop, to make sure you have access to it.