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

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
ashleylinkewich
Advocate II
Advocate II

Personal Mode Gateway - Key Error

Hi everyone,

 

Last week I was having absolutely no problems with both my personal and enterprise gateway until IT had me reset my computer password which changed everything. 

 

I am now getting this error when I try and sign into the personal gateway. I was previously running all of my connections through the enterprise gateway, but now that won't allow me to connect to my ODBC datasource. 

 

Does anybody know why this is happening or how to resolve? personalgatewayerror.PNG

PBI Error - Trying to connect to enterprise gatewayPBI Error - Trying to connect to enterprise gateway

 

2 REPLIES 2
v-yingjl
Community Support
Community Support

Hi @ashleylinkewich ,

 

If you've fixed the issue on your own please kindly share your solution. If the above posts help, please kindly mark it as a solution to help others find it more quickly. Thanks!


Best Regards,
Yingjie Li

v-yingjl
Community Support
Community Support

Hi @ashleylinkewich ,

  1. About personal gateway error:
    • Please uninstall on-premises data gateway, delete related folder here: C:\Users <username>\AppData\Local\Microsoft\On-premises data gateway (personal mode). 
    • Reinstall .Net Framework 4.7.2 or greater then reboot machine. (Download link: .net framework )
    • Install the latest on-premises data gateway (personal mode) version April 2020 (Download link: On-premises data gateway (personal mode) )
  2. About enterprise gateway error: The 400 ERROR means a bad http request. Please updata on-premise gateway to the lastest version. (Download link: On-premises data gateway ) If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.
    •  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.
    • 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.
    • 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 '''

    • You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page. Reference: Troubleshoot gateways - Power BI.

Best Regards,
Yingjie Li

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

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.