Forum Discussion

oduc78's avatar
oduc78
Advocate I
2 years ago
Solved

"PowerBINotAuthorizedException" error when using public Url EVEN after removing imported tables

Hello,

I've seen here a few similar posts on the topic but they don't really match my problem so I thought I'd make a new post.

I'll try to be as clear as possible:

  • I have a "regular" report published on Power BI Service with tables populated by queries getting data from Databricks once a day
  • I provide access to this report 1) through a public URL for customers, and 2) through Power BI Service for colleagues
  • In Desktop I added more 2 tables by creating a connection to the semantic model of another report and then published the update on Service (I did a back-up of the report + semantic model with the latest data before)
  • after the publication, anyone who tried to use a public URL started getting this "ServerError_PowerBINotAuthorizedException" error message, but the access through Service works fine and the data is up-to-date:

 

From reading a few posts here (post 1, post 2), I'm guessing that connected tables (is it considered a Direct Query?) from another semantic model is considered pretty much like Direct Query, and so it is not usable through a public URL. Fine. So I "just" have to go back to fix it, right?

 

So in order to fix this error I tried to:

  1. remove the extra connected tables in Desktop + re-publish/overwrite => same error message with the public URL
  2. remove the connection in the Data Source Settings menu in Desktop + re-publish/overwrite => same error message with the public URL
  3. remove the connection (that I found by chance) on the Manage connections and gateways page on Service => same error message with the public URL
  4. even re-upload the backup copy I had made just before the update! => the error message is still showing to anyone using the public URL!

Same thing on any other public report using data from the same semantic model. Adding connections to tables from another model seems to have "corrupted" the semantic model even after removing every trace of the connection and even if I try to overwrite it. 😥

I don't want to publish a new "import-free" report with a brand new semantic model because I would have to re-route and re-publish >450 customers reports that are fed today by my old model.

Any idea or suggestion would be greatly appreciated! Thanks. 🙂

 

Olivier.

Need Help

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi oduc78 ,

     

    According to your description, in Desktop I added more tables by importing them from another semantic model and then published them to Service.

     

    The error you are experiencing is reproduced, so it means that it is not possible to publish to the web in this way.


    So please check your report to make sure it is not an unsupported type. For example:
    - Reports that use row-level security.
    - Reports that use DirectQuery to connect to data. Reports that use DirectQuery to connect to data. connect in composite or import mode instead.
    - Reports in a workspace where you are not an editor member.
    - Single sign-on data query model.
    - Protect confidential or proprietary information.
    - ...

     

    More detailed information can be found in the documentation:

    Publish to web from Power BI - Power BI | Microsoft Learn

     

     

    Best Regards,

    Clara Gong

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

    • oduc78's avatar
      oduc78
      Advocate I
      2 years ago

      Thanks a lot Clara Anonymous for your reply! 👍

      As I wrote, I am aware that live connected tables from another semantic model prevents from publishing on the web with a public URL, that's why I'm just trying to revert all my changes and remove any live connected data or anything that causes this blockage.

      I tried to start from scratch again today with just a hand-typed, 4 rows table, no connection whatsoever, and when I publish this report with the name of my original report and overwrite it, I'm still not allowed to publish on the web. 😥

      It's like all the reports using my semantic model are been "flagged" as "not eligible" regardless of the name or content of the semantic model.

      Any idea?

  • oduc78's avatar
    oduc78
    Advocate I
    2 years ago

    Hello. I'm so desperate that I just created a brand new tiny 258 KB Power BI report from scratch with just 1 small table queried from Databricks, with NO other live/direct/stream connection whatsoever, and published it to Power BI Service with the same name as my original report in order to overwrite it: I'm still getting the same error message!!!

    And when I try to recreate a new public URL for that almost-empty report I get the other error message about this report being "not eligible for use with Publish on web":

    This semantic model is cursed!

    Does anybody have an idea? I really don't want to have to republish my report with a new name and send 450 new URLs to my customers!

    Olivier.

  • oduc78's avatar
    oduc78
    Advocate I
    2 years ago

    Hi all, I seem to have found a solution by using Windows PowerShell in order to use Power BI REST API commands. I was able to "rebind" (official term) an existing report to another "non-corrupted" source / semantic model. The whole thing took 3 command lines and only 1 minute!

    Finally a solution after wasting a week working between Power BI Service, Desktop, unzipped PBIX files... 🙂

    Here are:

    Let me know if anyone else has also fixed this kind of problem by using the Power BI API.

    Regards, Olivier.