Forum Discussion

MelissaSnell's avatar
MelissaSnell
Helper I
10 years ago

Possible BUG? Power BI Personal Gateway Does not close Database connections to PostGreSQL

We have about 6 datasets that are set to refresh on a schedule. This works as expected. However periodically the source PostgreSql database starts to deny connections because the number of connection...
Need Help
brendan_w's avatar
brendan_w
Advocate I
10 years ago

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_w's avatar
brendan_w
Advocate I
10 years ago

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"
Exit

 

 

As 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.

  • MelissaSnell's avatar
    MelissaSnell
    Helper I
    10 years ago

    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?

    • timrwilliams's avatar
      timrwilliams
      New Member
      9 years ago

      We're also seeing this issue.

       

      The poor handling of connections also results in a failed refresh if you do a database restore of the source Postgres database. Personal Gateway has to be restarted in order to flush out its connections and reconnect successfully.

       

      We're currently having to periodically run a variation of the suggested script (updated for Personal Gateway 2.0) to restart our gateway. 

       

       

      Taskkill /IM GWConfig.exe /F
timeout /t 5
& "C:\Users\Administrator\AppData\Local\Power BI Gateway - Personal\2.0\Configurator\GWConfig.exe"
Exit

       

       

      • chuarkai's avatar
        chuarkai
        New Member
        8 years ago

        Any permanent solution for this bug ? I see that it has been discussed since 2015.