Forum Discussion

smpa01's avatar
smpa01
Community Champion
5 years ago

dataflow refresh error -Error: AnalysisServices: The connection either timed out or was lost

Hi,

I have a dataflow for SSAS table and I keep on getting the following refresh error

 

Error: Data Source Error : DataSource.Error: AnalysisServices: The connection either timed out or was lost. DataSourceKind = AnalysisServices DataSourcePath = powerbi://api.powerbi.com/v1.0/myorg/workspace;Ledger

 

Sample DF

 

let
  X = AnalysisServices.Database("powerbi://api.powerbi.com/v1.0/myorg/Workspace", "Ledger", [Query="EVALUATE .....", Implementation="2.0"])
in 
 X

 

Does anyone know why it keeps on happening and how to prevent this?

Thank you in advance

Need Help

6 Replies

  • GilbertQ's avatar
    GilbertQ
    Super User
    5 years ago

    Hi smpa01 

     

    I am not sure if it is currently supported to access a Power BI Workspace via a dataflow.

     

    Can you confirm if your above App Workspace is on Power BI Premium or Premium Per User?

     

    If it is not Premium or PPU, then you will not be able to connect to it.

    • smpa01's avatar
      smpa01
      Community Champion
      5 years ago

      Hi GilbertQ  I am on premium capacity and I can confirm that I have created several DFs where I have accessed the same power bi workspace inside those DFs.

  • Jellbrae's avatar
    Jellbrae
    Frequent Visitor
    1 year ago

    Hi, smpa01  have you ever found a solution for this or found what was eventually the problem? 

    Thanks

    • smpa01's avatar
      smpa01
      Community Champion
      1 year ago

      Jellbrae this error occured few times. I felt helpless when it happeed. But it eventually went away with enough praying 👃and refreshing the dataflow agian and again.

       

      On a serious note, I could not find a concrete way to deal with it.

       

      I am not sure if it is anything to do with with balancing the load of the analysis sever.

      • Jellbrae's avatar
        Jellbrae
        Frequent Visitor
        1 year ago

        Thanks for the info smpa01 . I had some merges in the Applied Steps that came after the initial data load, which resulted in about +- 100mln rows. When I removed the merges, the problem was solved. From my side, it probably had to do with the amount of rows.