Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

Web Service URL not working and returns error

Hi everyone,   I am attempting to get the developer version of the Power BI Report Server up and running for testing and evaluation for my team. I am having issues with getting the Web Service URL ...
powerbi
PowerBIReportServer
webserviceurl
  • d_gosbell's avatar
    d_gosbell
    6 years ago
    Anonymous wrote:
      •  
      • Database tab
        • No current report server database configured. I do not have a separate SQL server running that I can connect the report server to. I assume that the Power BI Report Server will take care of storing the data. Please let me know if this assumption is wrong.

    This assumption is not correct. You must configure the database tab otherwise PBIRS will not work - this is how Report Server stores it's information about the reports it has available and all the other associated metadata. If you are using a local developer instance of PBIRS you could also use a local developer instance of SQL Server. 

d_gosbell's avatar
d_gosbell
Super User
6 years ago
Anonymous wrote:
    •  
    • Database tab
      • No current report server database configured. I do not have a separate SQL server running that I can connect the report server to. I assume that the Power BI Report Server will take care of storing the data. Please let me know if this assumption is wrong.

This assumption is not correct. You must configure the database tab otherwise PBIRS will not work - this is how Report Server stores it's information about the reports it has available and all the other associated metadata. If you are using a local developer instance of PBIRS you could also use a local developer instance of SQL Server. 

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Thanks d_gosbell! Your advice was spot on. 🙂

     

    I came to that conclusion yesterday after reading through a lot of documentation and very slowly putting the puzzle together. It was a little unintended misdirection from a colleague that set me off on this path.

     

    Much appreciated!