Forum Discussion
How to remove personal gateway from app.powerbi.com
Helper VThanks Anonymous for the follow up.
Yes, under "manage gateways", I have confirmed that the SQL server hosting the DB that my PBIX queries is listed, with my credentials. The PBIX refreshes fine on the desktop using my credentials. The manage-gateway test-service says: "Online, You are good to go"
I still can't switch my PBIX data source over to the EG.
Yet & still - my personal gateway is still being referenced in the service. Even if I could register this data source w/ the EG, it still seems like a bug that PowerBI is not aware that I've totally removed my Personal Gateway.
Eric.
Evogelpohl Do me a quick favor. What happens when you create a new PBIX to the SQL data source in the same way as the other file (import/direct query) and just add a quick visual, publish to the Service. Does the new report/datasource use the EG? I want to see if the behavior is the same or if it works.
- Evogelpohl
Anonymous Good thoughts. Here's what I tried & the outcomes:
Built brand new PBIX, with same SQL Server & DB, published. Clicked on Sched-Refresh -> YES! I can choose between my (defunct, but still there) Personal GW or the Enterprise Gateway. Works.
So, we know that the gateway is alive & working for me.
Though - odd - it still thinks my PG is registered, but offline.
Opened the original PBIX:
Ensured that the queries reference the exact SQL server name & DB name (even making sure I'm not using FDQN in the PBIX, but just the hostname in the gateway settings), re-publish -> Same error, says my PG is offline, EG grayed out.
Opened the original PBIX:
Saved it as a different file entirely. Publish the duplicate -> Same error, says my PG is offline, EG grayed out.
Opened the original PBIX:
Completely remove all saved data sources - deleted them all from the PBID data source settings. Save. Refresh the PBIX in the PBID, re-connected to the SQL server, Publish -> Same error, says my PG is offline, EG grayed out.
Open a ticket with MS Support -> waiting on call.Evogelpohl Thanks for the detailed response. Yeah, that pretty much exhausts everything I can think of. Be sure to update this thread when/if they figure out what the problem was... I'll be interested in to hearing what it is.
I am also having this problem. I second Anonymous in asking for you to keep us updated.
Thanks!Cris
@cweberits
Cloud Services Architect at @ITS_Partners
Just making ConfigMgr as a Service at https://itsdelivers.com/future
- RonEllisGaut
Advocate I
Did you get this issue resolved? I've had the same issue for months and would love to know what the solution is.
szilardsz+1, the same problem here.... thx!
- Evogelpohl
Anonymous Good thoughts. Here's what I tried & the outcomes:
- Built brand new PBIX, with same SQL Server & DB, published. Clicked on Sched-Refresh -> YES! I can choose between my (defunct, but still there) Personal GW or the Enterprise Gateway. Works.
- So, we know that the gateway is alive & working for me.
- Though - odd - it still thinks my PG is registered, but offline.
- Opened the original PBIX:
- Ensured that the queries reference the exact SQL server name & DB name (even making sure I'm not using FDQN in the PBIX, but just the hostname in the gateway settings), re-publish -> Same error, says my PG is offline, EG grayed out.
- Opened the original PBIX:
- Saved it as a different file entirely. Publish the duplicate -> Same error, says my PG is offline, EG grayed out.
- Opened the original PBIX:
- Completely remove all saved data sources - deleted them all from the PBID data source settings. Save. Refresh the PBIX in the PBID, re-connected to the SQL server, Publish -> Same error, says my PG is offline, EG grayed out.
- Open a ticket with MS Support -> waiting on call.
- Built brand new PBIX, with same SQL Server & DB, published. Clicked on Sched-Refresh -> YES! I can choose between my (defunct, but still there) Personal GW or the Enterprise Gateway. Works.
