Forum Discussion

DeepEureka's avatar
DeepEureka
Frequent Visitor
1 year ago
Solved

Power BI Report Server: Web portal shows an error when opening any report

Hi,   We can browse through the folders inside our PBIRS Web Portal, but when we try to open a report. A pop-up message appears saying that "An error has occured. Something went wrong. Please try ...
PBIRS September 2024
  • DeepEureka's avatar
    DeepEureka
    1 year ago

    I finally could solve it deleting all bindings from Report Server Configuration Manager, then creating them again.

    Steps:

    1. Remove all urls from Web Portal URL Section
    2. Remove all urls from Web Services URL Section (one could not be deleted). I added a new one, and then deleted the "old" one.
    3. Add url again to Web Services URL 
    4. Add url again to Web Portal URL

    This recreated again the bindings to urls (correctly). I guess there was a conflict between bindings/ports and denied acces to the service running the report server service that was raising the mentioned error.

    It can be useful to run cmd (as admin) netsh http show urlacl to detect these kind of conflicts between urls and users with autorization to listen to this url/ports.

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi, DeepEureka 

I wish you all the best. Previously we have provided a solution to help you solve the problem. Since we haven't heard back from you yet, I'd like to confirm if you've successfully resolved this issue or if you need further help?
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

 

 

Best Regards

Jianpeng Li

DeepEureka's avatar
DeepEureka
Frequent Visitor
1 year ago

I finally could solve it deleting all bindings from Report Server Configuration Manager, then creating them again.

Steps:

  1. Remove all urls from Web Portal URL Section
  2. Remove all urls from Web Services URL Section (one could not be deleted). I added a new one, and then deleted the "old" one.
  3. Add url again to Web Services URL 
  4. Add url again to Web Portal URL

This recreated again the bindings to urls (correctly). I guess there was a conflict between bindings/ports and denied acces to the service running the report server service that was raising the mentioned error.

It can be useful to run cmd (as admin) netsh http show urlacl to detect these kind of conflicts between urls and users with autorization to listen to this url/ports.