Power BI Report Server – Support

Microsoft  plans to release Power BI Report Server “multiple times per year.”
– Initially, they have planned for about 3 releases per year (in other words, on average, every 4 months).
– They support each release for 12 months, which gives customers up to a year to upgrade to a newer version while receiving any necessary security patches for the version they’re using.

Version Availability date Support end date
June 2017 June 12, 2017 June 12, 2018

Support Reference

Advertisements

How to change data source for Power BI report

We started implementing Power BI. We created a Power BI report using Power BI desktop going against development machine.

Now we wanted to change the SSAs server name from Development to Production.

We opened the report in Power BI desktop.

We went into Edit Queries and clicked on Data Source settings and we were able to change the SSAS server name. 

In our case on going to  File -> Options and settings -> Data source settings > there were no data sources, Hence the change source button was greyed out.

How to install Power BI on-premise Report Server nodes across several machines behind a network load balancer (NLB)

On the following Power BI community blog they referred to installing of Power BI Report Server nodes across several machines behind a network load balancer (NLB):

https://community.powerbi.com/t5/Report-Server/Production-Configuration/m-p/198692

For the Power BI Report Server itself it is recommend a scale out deployment with several Power BI Report Server nodes across several machines behind a network load balancer (NLB). This can be read about here https://technet.microsoft.com/en-us/library/ms159114(v=sql.105).aspx

To install the first report server instance

  1. Install the first report server instance that is part of the deployment. When you install Reporting Services, choose the Install but do not configure server option on the Report Server Installation Options page.
  2. Start the Reporting Services Configuration tool.
  3. Configure the Report Server Web service URL, Report Manager URL, and the report server database. For more information, see How to: Configure a Report Server in SQL Server Books Online.
  4. Verify that the report server is operational. For more information, see How to: Verify a Reporting Services Installation in SQL Server Books Online.

To install and configure the second report server instance

  1. Run Setup to install a second instance of Reporting Services on a different computer or as a named instance on the same computer. When you install Reporting Services, choose the Install but do not configure server option on the Report Server Installation Options page.
  2. Start the Reporting Services Configuration tool and connect to the new instance you just installed.
  3. Connect the report server to the same database you used for the first report server instance:
    1. Click Database to open the Database page.
    2. Click Change Database.
    3. Click Choose an existing report server database.
    4. Type the server name of the SQL Server Database Engine instance that hosts the report server database you want to use. This must be the same server that you connected to in the previous set of the instructions.
    5. Click Test Connection, and then click Next.
    6. In Report Server Database, select the database you created for the first report server, and then click Next. The default name is ReportServer. Do not select ReportServerTempDB; it is used only for storing temporary data when processing reports. If the database list is empty, repeat the previous four steps to establish a connection to the server.
    7. In the Credentials page, select the type of account and credentials that the report server will use to connect to the report server database. You can use the same credentials as the first report server instance or different credentials. Click Next.
    8. Click Summary and then click Finish.
  4. Configure the Report Server Web service URL. Do not test the URL yet. It will not resolve until the report server is joined to the scale-out deployment.
  5. Configure the Report Manager URL. Do not test the URL yet or try to verify the deployment. The report server will be unavailable until the report server is joined to the scale-out deployment.

To join the second report server instance to the scale-out deployment

  1. Open the Reporting Services Configuration tool, and reconnect to the first report server instance. The first report server is already initialized for reversible encryption operations, so it can be used to join additional report server instances to the scale-out deployment.
  2. Click Scale-out Deployment to open the Scale-out Deployment page. You should see two entries, one for each report server instance that is connected to the report server database. The first report server instance should be joined. The second report server should display a status of “Waiting to join”. If you do not see similar entries for your deployment, verify you are connected to the first report server that is already configured and initialized to use the report server database.
  3. On the Scale-out Deployment page, select the report server instance that is waiting to join the deployment, and click Add Server.
Note
Issue: When you attempt to join a Reporting Services report server instance to the scale-out deployment, you may experience error messages similar to ‘Access Denied’.

Workaround: Back up the Reporting Services encryption key from the first Reporting Services instance and restore the key to the second Reporting Services report server. Then try to join the second server to the Reporting Services scale-out deployment.

  1. You should now be able to verify that both report server instances are operational. To verify the second instance, you can use the Reporting Services Configuration tool to connect to the report server and click the Web Service URL or the Report Manager URL.

Add entry for the load balance in Report Server Configuration Manager => Web Portal URL

We have two nodes say pbinode1 and pbinode2 and load balancer say pbi. So as per above instructions we have completed installing and configuring Power BI report on pbinode1. Now on pbinode1 open Report Server Configuration Manager => Web Portal URL section. Click on Advanced and add an entry for load balancer pbi.

Power BI – Group Workspace and Content Pack – Dashboards Reports and Datasets

There are three basic types of content or building blocks in Power BI:

Datasets, Reports and Dashboards

Datasets are reporting models with attributes and measures (calculations) that a user can EXPLORE and build different types of visualizations. Datasets can also be RENAMED, DELETED and REFRESHED

Reports are collections of visuals.

Dashboards are a collection of tiles that are pinned from Reports by mouse over the desired chart and clicking on the Push Pin Icon. Tiles can be rearranged and resized.

Where do we store Dashboards, Reports and Datasets?

You will have two options for storing your content:

  • My Workspace
  • Group Workspaces

So how do I organize everything in Power BI?

Any content that will need governance or will potentially reach a large number of users should be stored in a group workspace. Content that does not require much collaboration and governance can be stored in your personal workspace. Another thing to consider is that a personal workspace is limited to 10GB in the Pro version. So is each group workspace. However, every new group gets another 10GB of storage which makes a group concept even more alluring.

OK, now that I have organized everything, how do I share it?

If you have a dashboard stored in your personal workspace, you can use a Share Dashboard feature.

Only dashboards can be shared (reports and datasets cannot).

Share Dashboard option is not available for dashboards created in Group workspaces.

Another way to share content, is by creating an organizational content pack.

We can create an organizational content pack by clicking the gear icon on the top right hand corner of the page

We will then have an option to specify who has access to the content pack, its Title and Description (both are required) and also what dashboards, reports and datasets should be included in it

Then click Publish button at the bottom of the page to complete content pack creation process.

After the content pack has been published, users with required access will have an option to consume it by clicking on Get Data->Get

The Definitive Guide on Collaboration in Power BI Reference

With Connect live Power BI report published to PBI Services online using Enterprise gateway we get error when connecting to SSAS cube but SQL server database works

We created a PBI report with live connection to SSAS cube and it worked on desktop.

We created Organization (Enterprise) level gateway on the cloud app.powerbi.com.

We published the report. When we tried to view the report it gave the generic error: “Couldn’t load the model schema”.

We found out that our UPN was different from user-id (email). Our user-id was “my-user-id@abc.com”, whereas our UPN was “my-user-id@xyz.abc.com”.

So we created User mapping at the datasource in the gateway from “@abc.com” to “@xyz.abc.com”.

Viola!! The report started working on cloud going live against our on-premise SSAS server using on-premise gateway.

To create mapping navigate to Settings=> manage gateways => Data Source => Users and click on button “Map user names”.

Power BI Community Reference and Microsofts Guy In a Cube Solution Reference