Forum Discussion

AtulsDream's avatar
AtulsDream
Frequent Visitor
3 years ago
Solved

Schedule Refresh failed outside the office premises

Hello All,

 

I am working on interal project in my organisation. We need to create Power BI report, which having SQL server used as data source. The SQL server installed on remote desktop, and we have installed the PBI desktop in RD only and created the report and published it on services. 

I have installed the Personal gateway outside the RD connection(on my company laptop), While trying to refresh the dataset on services, it refresh successfully when I will be in office, but when I worked from home even connected to VPN and RD, the refresh is getting failed every time.

 

Please suggest the solution to solve my issue.

Following are my concerns:

1. I need to install Gateway in Remote desktop connection?

2. I need to install On premise gateway instead of personal gateway??

 

Or please suggest any other solution.

 

Thanks.

Need Help
  • collinq's avatar
    collinq
    3 years ago

    Hey AtulsDream ,

     

    A personal gateway will run when you are signed into the machine that has the gateway.  So, if you are not actively signed on, nothing will happen.  This is the design of the personal gateway.  If you want the gateway to run on its own and refreshing automatically without issues, the standard (enterprise) gateway is the way to go.  

    The gateway should be installed on a server that doesn't have capacity issues or network issues and is normally "on".  I would not put a gateway on a SQL server as SQL is known for being a high RAM user and because the gateway itself can spike pretty high during peak times.

     

1 Reply

  • collinq's avatar
    collinq
    Icon for Super User rankSuper User
    3 years ago

    Hey AtulsDream ,

     

    A personal gateway will run when you are signed into the machine that has the gateway.  So, if you are not actively signed on, nothing will happen.  This is the design of the personal gateway.  If you want the gateway to run on its own and refreshing automatically without issues, the standard (enterprise) gateway is the way to go.  

    The gateway should be installed on a server that doesn't have capacity issues or network issues and is normally "on".  I would not put a gateway on a SQL server as SQL is known for being a high RAM user and because the gateway itself can spike pretty high during peak times.