Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago

DataSet connection to Dataflows

Hi 

We have been using the dataflows in PowerBI which they are connected to Data Gen2 and been working fine for some time

and Nothing has changed from our side.

However today I'm getting the following message when trying to connect to the dataflows and the datasets that are connected to dataflows are failing 

 

Error msg from the Desktop when trying to connect to dataflows:

DataflowsStorageAccountKeyRetrievalForbidden: DataflowsStorageAccountKeyRetrievalForbidden
Details:
Error=DataflowsStorageAccountKeyRetrievalForbidden
RequestId=1a192170-9717-4abe-8a98-2240e6dfc674

 

Error msg from the dataset when trying to refresh from the Portal

 

There was an error when processing the data in the dataset.

Please try again later or contact support. If you contact support, please provide these details.

Data source errorDataflowsStorageAccountKeyRetrievalForbidden. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. 

Cluster URIWABI-NORTH-EUROPE-redirect.analysis.windows.net

Activity ID71086bec-c93f-4ba9-9433-f2dbded36584

Request ID4550f0ae-eaf8-b401-1fe3-8bb1fc046bc9

Time2020-04-29 10:48:09Z

 

 

Not sure if theere is a service issue, your help will be appreciated.

JF

Need Help

2 Replies

  • v-alq-msft's avatar
    v-alq-msft
    Community Support
    6 years ago

    Hi, Anonymous 

     

    I failed to reproduce your scenario. You may check if the credentials are updated and you have permissions to the data. I'd like to suggest you double-check on correspond Datasource credentials at power bi service 'setting ->datasets'. If it doesn't work, you may create a support ticket here for the issue.

     

    Best Regards

    Allan

     

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      Hi Allan,

      Thanks for you reply, I did raise the issue with Microsoft and looks like it was a Microsoft changed has caused the issue, they are preparing a fix now.

      Thanks

      JF