Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

Report published to web shows "This content isn't available." (401 Unauthorized)

Hello,

 

I published to web some reports in iframes and they worked fine. But after some time, none of my reports works.

 

I don't know why, but every report shows:

This content isn't available.
Learn more about Power BI.

 

When I inspect that page i can see:

Failed to load resource: the server responded with a status of 401 (Unauthorized)

My example page:

https://iotwebapplication.azurewebsites.net/Correlations/IndoorFull

 

My published to web report page:

https://app.powerbi.com/view?r=eyJrIjoiN2NhYTY4OTYtNzBkNS00YzU0LTg5MjktYWY2YmU1OTYyM2UzIiwidCI6IjI1NzMzNTM4LTZiMTYtNGFhMy04ZWQ2LTI5N2ViNzliOGUwNiIsImMiOjh9

 

Can someone please help me?

Thank you

401
Publish
unauthorized
Web

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Hi,

     

    Anonymous 

    I had the same issue.

    It seems like there might be a bug with the new workspace.

     

    Try to create a new workspace and chose "revert to classic". This should work for the time being.

     

    Thanks

    • Ruivo's avatar
      Ruivo
      New Member
      6 years ago

      That is it! I had the same issue as OP, and this is what solved it for me - creating a new workspace and reverting it to classic. Thank you very much Anonymous!

      • Anonymous's avatar
        Anonymous
        Not applicable
        6 years ago

        Is there any more details on how to revert to classic?

         

        I have "new look" set to off.

         

        Created a new workspace and loaded a sample, but the publish to web still gets the same issue.

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    I tried to create simple report with entered manually very simple data and after publishing it shows me the same error as above. I don't know what can be wrong. Can someone help me please?

  • charlie23's avatar
    charlie23
    New Member
    7 years ago

    Hi,

     

    If the question is still actual, i faced the same problem and found out that clearing browser cache was the solution.