Anonymous's avatar
Anonymous
Not applicable
6 years ago
Status:
New

Azure Analysis Services Perspectives not Returning Data

When we connect to our Azure Analysis Services instance in Power BI Desktop and PowerBI.com, everything works if you are going through the default perspective, but if any perspective is chosen, no data is returned and an "Unexpected Error" is given. This is breaking every report we have, because they are all using AAS.

 

Example:

Couldn't retrieve the data for this visual. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.

5 Comments

  • v-yuta-msft's avatar
    v-yuta-msft
    Icon for Community Support rankCommunity Support

    Anonymous ,

     

    Please check if any data column type or name has been changed in ssas model.

     

    Regards,

    Jimmy Tao

  • narloo71's avatar
    narloo71
    Regular Visitor

    We are also experiencing this problem. No change on the AS model. Can connect to the default model but can't connect to any perspective.

    Anonymous Microsoft are suggesting that this may be caused by a service upgrade late last week.

  • Anonymous's avatar
    Anonymous
    Not applicable

    v-yuta-msft 

     

    This is not SSAS. We are using Azure Analysis Services which had an update released the night before we started seeing issues.

     

    I've recreated this issue on 2 servers for 5 different models for 5 different people. Nothing has changed to any of the models.

  • Meagan's avatar
    Meagan
    Icon for Most Valuable Professional rankMost Valuable Professional

    Anonymous This is a legit bug. A client of ours ran into the issue and submitted a support request. MS support and the product team are aware of the issue, but it sounds like a fix may be a few days or more away. 

  • Anonymous's avatar
    Anonymous
    Not applicable

    Thanks for the comment Meagan 

     

    We have a ticket open with Microsoft support.  Took 4 or 5 days for a confirmation of what we thought was happening, but they do appear to be working on it now.  Hopping for a quick(ish) resolution. This has taken down the majority of our company's reports, unless we redeploy every single report individually, which we'd have to change back once it is fixed. Not really feasabile when we have hundereds of reports relying on AAS models.