Skip to content

A couple of things to watch out for if deploying Power BI Report Server

Reading Time: 2 minutes

In this post I want to cover a couple of things to watch out for if deploying Power BI Report Server. So that it helps others who may encounter issues.

A while back I wrote about how SQL Server DBA’s can make use of Power BI Report Server here.

Therefore, I thought I better write this follow up. Because there’s a couple of things you may need to watch out for if you are deploying Power BI Report Server. Especially if you are automating deployments.

You can read the official guide for installing Power BI Report Server here.

Just to recap, Power BI Report Server is a version of Power BI that you can install on a server for use. In fact, you can think of it as SQL Server Reporting Services with extra functionality to work with Power BI dashboards.

Database collations

To automate your Power BI Report Server deployments, you may have written a PowerShell script or downloaded a PowerShell module.

If you have done either of the above, I do recommend checking the database collations before going further. Otherwise, you can end up with an unexpected database collation that can cause issues.

Unable to add Data Sources

Occasionally when you try to add a Data Source in the Power BI Report Portal you might get an error. To resolve this, simply recreate your Virtual Directory in the Power BI Report Manager

If you’re anything like me, you’ll probably want to rename it to anything else. Afterwards, you can recreate it again using its original name.

Final word

Anyway, that’s it from me in this brief post about a couple of things to watch out for if deploying Power BI Report Server.

If you have any comments or queries about this post feel free to reach out to me.

A couple of things to watch out for if deploying Power BI Report Server
Published inBusiness Intelligence & analytics

One Comment

Leave a Reply

Your email address will not be published.