Forum Discussion
Possible BUG? Power BI Personal Gateway Does not close Database connections to PostGreSQL
I was hoping to be able to use Task Scheduler to stop and re-start the Gateway as a service, to save me from having to re-boot the workstation once or twice a week, but can't seem to see it listed, even though I installed it as an Administrator.
In addition I have just installed the October 22 release of the Personal Gateway, that seems to hold some promise of solving other issues that I was getting, so am hopeful that it might address this one as well
As a workaround I managed to get the Data Management Service installed during the Gateway installation process and now I am running a batch file using Windows Task Scheduler with a NET STOP SLEEP 120 NET START kind of thing.
I am awaitng feedback from the DBA to see if this is a viable work around
- brendan_w10 years agoAdvocate I
Melissa did you have any luck with this workaround in the end? The Gateway is still leaking connections for me, so clearly this bug has not been fixed.
I've tried setting the task scheduler to do a reboot but this doesn't work as Power BI doesn't recognise that the Gateway is active upon the reboot. It would be very interesting to hear about your experiences with this issue.
- brendan_w10 years agoAdvocate I
For anyone that encounters this in the future. This is the batch file i've used over the last few days to prevent the connection leaks from occuring.
net stop PBIEgwService
Taskkill /IM GWConfig.exe /F
timeout /t 30
net start PBIEgwService
"C:\Users\Administrator\AppData\Local\Power BI Personal Gateway\1.0\Configurator\GWConfig.exe"
ExitAs well as rebooting the service it's necessary to restart GWConfig. Without this the web client doesn't recognise that a Gateway is online. It's also necessary to have a taskkill on the GWConfig to prevent multiple instances being active.
- MelissaSnell10 years agoHelper I
This is still an issue for us.
I can't find anything in the Gateway updates that suggestst that this problem is even recognised.
The workaround does drop the connections, but the number of concurrent connections is building up now prior to the closing of the connections to levels that are starting to cause issues with other systems that require connections.
Does anyone know if this is going to be dealt with?