Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Unexpected Error Power BI report Server With Desktop While Connecting/Save As

I have configured the Power BI report server with custom authentication and I am able to browser reports and upload reports from Desktop version and optimised dektop version from the web url.
But when I try to connect or save as to report server from the optimised desktop version (Jan 2019), I always the error "Unexpected error encountered". I have seen the log files and below is the error message(s).
 
I am also getting the same error when I am trying to edit the report from browser and opening it in the optimised desktop version for power bi server.
 
I am using the latest version of Power BI report server, desktop version and optimised desktop version.
 
Can somebody please help me on this as I am really struggling to understand, why it is unathorised.
 
2019-05-22 00:11:35.4527|INFO|40|Sending response. Response code 401, Elapsed time 0:00:00.0001283| RequestID = s_6a077791-e4b6-4df6-b500-43388022ec3f
2019-05-22 00:11:51.3842|INFO|39|Received request GET | RequestID = s_bd226fee-61d0-4053-8cc6-57c312b2f743
2019-05-22 00:11:57.0293|INFO|40|Received request GET /api/v2.0/ServiceState| RequestID = s_dd68be34-263b-4cfa-990f-b02ccfc1814d
2019-05-22 00:11:57.0293|INFO|40|Sending response. Response code 401, Elapsed time 0:00:00.0001742| RequestID = s_dd68be34-263b-4cfa-990f-b02ccfc1814d
2019-05-22 00:11:57.2474|INFO|40|Received request GET /api/v2.0/ServiceState| RequestID = s_be9aeee1-19b2-4411-84e8-457d8f0e38fb
2019-05-22 00:11:57.2474|INFO|40|Sending response. Response code 401, Elapsed time 0:00:00.0001366| RequestID = s_be9aeee1-19b2-4411-84e8-457d8f0e38fb
2019-05-22 00:18:16.8672|INFO|42|Received request GET /api/v2.0/ServiceState| RequestID = s_0ef6cbe1-2aaa-4eef-bb5b-09d6e690b82c
2019-05-22 00:18:16.8672|INFO|42|Sending response. Response code 401, Elapsed time 0:00:00.0002326| RequestID = s_0ef6cbe1-2aaa-4eef-bb5b-09d6e690b82c
  • Anonymous's avatar
    Anonymous
    7 years ago

    The problem was in the code itself in the logon page of the custom authentication. Thank you for the suggestions, it helped me on my solution.

7 Replies

  • It's probably something in your custom authentication.

     

    How does your custom authentication work?

     

    What happens when you attempt to hit one of the urls PBI desktop is attempting to connect to like http://<servername>/reports/api/v2.0/ServiceState Does it return a json response or a 401 error or does it prompt for a username and password?

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi,

       

      Thank you for the reply. After using the API service state url I am getting a pop up window to enter user id and password. Once I enetered the credentials I get the below error message.

      This page isn’t working

      If the problem continues, contact the site owner.

      HTTP ERROR 401
      • d_gosbell's avatar
        d_gosbell
        Super User

        Anonymous wrote:

        Hi,

         

        Thank you for the reply. After using the API service state url I am getting a pop up window to enter user id and password. Once I enetered the credentials I get the below error message.

        This page isn’t working

        If the problem continues, contact the site owner.

        HTTP ERROR 401

        So I can think of 2 possible issues here. One is that I'm not sure if Power BI Desktop will have the facility to be able to trigger an authentication pop up. The second is that there seems to be some other issue even when you do enter the credentials.

         

        Can try temporarily switching back to Windows auth? This will allow you to confirm that this API is working properly in your environment. If you can confirm that this api call works without your custom authentication then we know definitively that this is the issue and then you'll need to debug the code for the custom auth to figure out the issue. 

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi, 

        Just wondering if you managed to find a solution to this issue?