Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
rsangeetha
Frequent Visitor

Password protected Access Database - Gateway error

Hi all,

 

I am fairly new to Power BI. I have an access database which is password protected. From my Power BI Desktop, I am able to successfully connect to it through OLE DB driver (Thanks to reference). Now, I have published the report online and trying to schedule a refresh for this database through an on-premises gateway (reference) located in the server.

 

I tried choosing couple of Authentication Methods and still hitting the following roadblocks.

  1. Windows - OLEDB driver does not support this authentication methodrsangeetha_1-1630463219252.png
  2. Anonymous rsangeetha_0-1630459381061.png

 

Any leads would be appreciated, thanks in advance.

1 ACCEPTED SOLUTION

Thanks for your reply. The issue was because the database had an unconventional file extension. OLE DB connection was successful to the database in Desktop but not in PowerBI Service. To resolve this issue, I copied the database and stored as .mdb to establish an ODBC connection. Now, I am able to schedule data refresh in PowerBI Service using ODBC.

View solution in original post

3 REPLIES 3
v-yetao1-msft
Community Support
Community Support

Hi @rsangeetha 

After doing this, can you refresh normally now ? If it has been solved, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards

Community Support Team _ Ailsa Tao

v-yetao1-msft
Community Support
Community Support

Hi @rsangeetha 

The 400 ERROR means a bad http request. Please update on-premise gateway to the lastest version. If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.

 

  1. Check if the server is using a proxy and the proxy. Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on ports other than 443.
  2. You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect to Https. This file is located, by default, at C:\Program Files\On-premises data gateway.
  3. Restart the gateway and check if the issue persists. 
  • To stop the service, run this command:

''' net stop PBIEgwService '''

  • To start the service, run this command:

''' net start PBIEgwService '''

  1. You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page.

Reference: https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#tools-for-troubleshooting.

 

Best Regards

Community Support Team _ Ailsa Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks for your reply. The issue was because the database had an unconventional file extension. OLE DB connection was successful to the database in Desktop but not in PowerBI Service. To resolve this issue, I copied the database and stored as .mdb to establish an ODBC connection. Now, I am able to schedule data refresh in PowerBI Service using ODBC.

Helpful resources

Announcements
Sept PBI Carousel

Power BI Monthly Update - September 2024

Check out the September 2024 Power BI update to learn about new features.

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

Sept NL Carousel

Fabric Community Update - September 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors