Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Scale-Out Power BI report Server using F5 Load Balancer.

I am scaling out Two Nodes of Power BI Report Servers installed at both nodes. To configure F5 Load Balancer I needs to enter MachineKey entry into to Web.config file. Accroding to different Blogs I ...
  • pbx's avatar
    pbx
    8 years ago

    Sorry for the link, I corrected it in the post and added here as well.

     

    https://docs.microsoft.com/en-us/sql/reporting-services/extensions/security-extension/how-to-install-custom-security-extensions

     

    The point of that URL wasn't about custom authentication per se, but more to show that the location you need to put the machine key is changed with PBIRS. Unfortunatley that's the only place such information is documented correctly on MS site.

    And yes, putting the machine key in rsReportserver.config, while is the right place, may not solve your poblem, so you may need to put it in the machine.config of the dotnet.

     

    In any case, my understanding is that using the machine key will solve the view state validation issue. However the MS documentation is not really clear if that is a requirement for PBI type of reports or only applicable to paginated (traditional SSRS) reports. In case of paginated reports, I don't think setting affinity at the load balancer will provide you a fault free solution for view state, so your best bet still would be setting the machine key.

     

    In certain scnearios, you'd need to put an entry on each server host file to point the virtual host name to the IP of that server for PBIRS scale out to work properly. 

  • Anonymous's avatar
    Anonymous
    8 years ago

    Issue is resolved.

    Isuse was in F5 Load Balancer. Wrong port was configured. We just Change the port to 80 and Its works fine for me.

    I did followng Steps.

    1. add MachineKey inside rsReportServer.config under <configuration> section.
    2. add <Hostname> reporting.company. com</Hostname> under <Service> section.
    3. add Root URL <UrlRoot>http:// reporting.company. com/reportserver</UrlRoot>

     

    I appreciate the your support.

pbx's avatar
pbx
Helper V
8 years ago

 

If the virtual host name (the one registered at F5) is reporting.mycompany.com, then by default you should go to http://reporting.mycompany.com/reports for the portal, http://reporting.mycompany.com wouldn't work for SSRS. Not sure if this is the problem. If not, it's important to know your URL reservations for Report Server Web Service and the application before one can tell what's going on. Also, did you make sure a single server implementation works before attempting scale out.

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Issue is resolved.

Isuse was in F5 Load Balancer. Wrong port was configured. We just Change the port to 80 and Its works fine for me.

I did followng Steps.

  1. add MachineKey inside rsReportServer.config under <configuration> section.
  2. add <Hostname> reporting.company. com</Hostname> under <Service> section.
  3. add Root URL <UrlRoot>http:// reporting.company. com/reportserver</UrlRoot>

 

I appreciate the your support.