Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago

500 Error Publishing to PowerBI Service

I have a report which was working fine in PowerBI Service. 

 

As of this morning it is failing. When I try republish I get a 500 error, looking at the error it says "We don't support the option 'HierarchicalNavigation'". I have no preview features turned on, and the refresh / dataset works in Desktop.

 

Screen shots and http trace of the publish below. 

 

 

 

 

HTTP/1.1 500 Internal Server Error
Content-Length: 443
Content-Type: application/json; charset=utf-8
X-PowerBI-Error-Info: ModelRefresh_ShortMessage_ProcessingError
X-PowerBI-Error-Details: {"error":{"code":"ModelRefresh_ShortMessage_ProcessingError","pbi.error":{"code":"ModelRefresh_ShortMessage_ProcessingError","parameters":[],"details":[{"code":"ModelRefresh_ProcessingErrorLabel","detail":{"type":1,"value":"COM error: Microsoft.Data.Mashup, We cannot generate a query for the given data source reference. Failure reason: We don't support the option 'HierarchicalNavigation'.\u000d\u000aParameter name: HierarchicalNavigation.. "}}]}}}
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Frame-Options: deny
X-Content-Type-Options: nosniff
Access-Control-Expose-Headers: RequestId,X-PowerBI-Error-Info,X-PowerBI-Error-Details
RequestId: 825a548f-1b27-492c-a5f7-accd650fe41f
Date: Wed, 24 Jun 2020 09:07:57 GMT

{"error":{"code":"ModelRefresh_ShortMessage_ProcessingError","pbi.error":{"code":"ModelRefresh_ShortMessage_ProcessingError","parameters":{},"details":[{"code":"ModelRefresh_ProcessingErrorLabel","detail":{"type":1,"value":"COM error: Microsoft.Data.Mashup, We cannot generate a query for the given data source reference. Failure reason: We don't support the option 'HierarchicalNavigation'.\r\nParameter name: HierarchicalNavigation.. "}}]}}}

 

 

 

 

 

 

Need Help

15 Replies

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

    Hi Anonymous ,

     

    Are you using the gateway?  If so, do you have the latest version and the latest version of Desktop installed?  Have you shared this with a person (or yourself) that does not have a PRO license?  Do you have any proxy servers in the environment?  Are all of the ports/firewall/permissions allowing everything to get through?  Has the dataset moved?  Has the dataset, particularly the area with the Hierarchy been modified in some way that might be affecting this?  Has any of the report(s) or datasets been deleted from the workspace?  Or, renamed in the workspace?  Is your data file at a location that has been changed or renamed in some way?

     

    I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      No gateway in play. Everything is up to date. 

  • v-deddai1-msft's avatar
    v-deddai1-msft
    Icon for Community Support rankCommunity Support
    6 years ago

    Hi Anonymous ,

     

    How about "Get data" from the Service?

     

    Best Regards,

    Dedmon Dai

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      That works, it seems the HierarchicalNavigation attribute has been deprecated/broken, a breaking change. 

      Its this M source that fails. 

       

      let
      Source =
      AzureStorage.DataLake(
      #"_ Data Lake Root",
      [HierarchicalNavigation=true]
      )
      in
      Source

      • nickyvv's avatar
        nickyvv
        Icon for Most Valuable Professional rankMost Valuable Professional
        6 years ago

        Hi Anonymous,

         

        according to the documentation on AzureStorage.DataLake it should still be supported.

        In September of last year, Chris Webb wrote an extensive post about the HierarchicalNavigation property, but also mentions this connector was still in beta. 

        If I look at the Connector page, it doesn't seem to be in beta anymore.

        If I look in Power Query, the documentation there also says it is still supported, so that's strange.

         

        One clarifying question, are you sure you're connecting to an Azure Data Lake Store Gen2 storage account, not a Gen1?

        And did you also set the Hierarchical namespace property to Enabled, listed under point 8?

        Last, there are a few more prerequisites, but I think you've got them covered.