Forum Discussion
How to remove personal gateway from app.powerbi.com
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.
- cweberITS10 years agoNew Member
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
- jmdh9 years ago
Advocate IV
I am experiencing the same issue (Gateway uninstalled but message saying that is is offline) and have contacted support two weeks ago and still waiting (but hoping) to get a resolution...
Have installed successfully gateway on Machine 2 and it works but when i uninstall i have agian the same problem.
- Anonymous9 years agoNot applicable
Sorry to hear that you are having this problem too.
Definately seems that addressing this is a low priority for MS which is very annoying.