Forum Discussion

dniedrauer's avatar
dniedrauer
Resolver I
8 years ago
Solved

Schedule Refresh Greyed Out

 

The sources are: (1) an Oracle database and (2) a SharePoint API and (3) it has always worked correctly until today and (4) I updated the on premises - personal data gateway to the latest version, but it didn't fix the issue and (5) refresh in the desktop version of the same dataset works fine. 

 

Previously, I was also getting the error: "The gateway operation has been cancelled explicitly by the user or from a timeout" when trying to refresh on demand. 

  • dniedrauer's avatar
    dniedrauer
    8 years ago

    Yes, that wasn't the issue. I am still having trouble only with that one dashboard even though the others update fine and have the same credentials....

     

    I found out that republishing it to the cloud fixed the problem. 

5 Replies

  • v-jiascu-msft's avatar
    v-jiascu-msft
    Microsoft Employee

    Hi dniedrauer,

     

    1. Maybe you need to update the credentials.

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    2. Why not try the On-premises Gateway? (not the personal mode).

     

     

    Best Regards!

    Dale

    • dniedrauer's avatar
      dniedrauer
      Resolver I

      I'm not the one who makes purchasing decisions. 

       

      The other one requires a Power BI Premium subscription I believe. Or something that cost money which we don't currently have. I forget whether it's premium or something else, but it's not something we have at this time. 

      • v-jiascu-msft's avatar
        v-jiascu-msft
        Microsoft Employee

        Hi dniedrauer,

         

        Did you update the credentials?

         

        As far as I know, all the versions of Gateway are free to use. Give it a try anyway.

         

        Best Regards!

        Dale

  • JimJim's avatar
    JimJim
    Responsive Resident

    Old post I know but updating the data source credentials worked for me