pbirs data source
8 Topicsafter jan PBIRS 2021 we get the "We couldn't connect to the Analysis Services server" error
HI! After we upgraded our on premises powerBI server to the jan 2021 version, upgraded our PBIDesktopRS as well. We have multiple PBIX files published to our on premises server all of them connected to our SQL server 2016 using DirectQuery mode. After the upgrade, whenever we are executing any of them we get the following error. "We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly." on all our reports. weird that on PowerBi Desktop RS they work, but when i publish them, we get that error on the server. honestly im a newbie in this stuff and im trying to figure it out. Any help will be appreciated!3.3KViews0likes10CommentsReportingServicesTools Set-RsRestItemDataSource - BAD REQUEST how to diagnose?
I am attempting to write a script to update Datasource connect strings for power bi reports on PBIRS(on prem, no service) - Trying to add a port to the ( sharepoint ) url in the connect string. Forgive me as I am new to this and unsure how to move forward. Script is below and it does return the connectstring with the port to screen prior to setting it. Can anyone help with possible next steps or what might be wrong? Thanks in advance The last line Set-RsRestItemDataSource -RsItem $dataSourcePath -RsItemType 'PowerBIReport' -DataSources $ds -ReportPortalUri $ReportServerURI returns Failed to update data sources for '/AP/CSECR/Action%20Items': The remote server returned an error: (400) Bad Request. $ReportServerURI = "https://<svr>/Reports/" $ReportPortalUri = "https://<svr>//PBIReports" $dataSourcePath = "/MyReportPath" cls #Get-RsRestItemDataSource -RsItem $dataSourcePath -ReportPortalUri $ReportPortalUri $dataSources = Get-RsRestItemDataSource -RsItem $dataSourcePath -ReportPortalUri $ReportServerUri foreach($ds in $dataSources) { Write-Host $ds.ConnectionString $ds.ConnectionString = $ds.ConnectionString.Replace("mydomain.com", "mydomain.com.999") $ds.DataModelDataSource.AuthType = "Integrated" $ds.DataModelDataSource.Username = "Adomain\user" $ds.DataModelDataSource.Secret = "mypw" Write-Host $ds.ConnectionString Set-RsRestItemDataSource -RsItem $dataSourcePath -RsItemType 'PowerBIReport' -DataSources $ds -ReportPortalUri $ReportServerURI }3.4KViews0likes5CommentsWhy end user cannot see visualizations on Power BI Report Server with data from Excel
Hi, I created a dashbaord with data imported from Excel, (Excel file is stored on my local machine The dashboard is available on PBIRS but the end user got the error message "this site can't be reached". What should I change, update? Thanks,582Views0likes2Commentson-prem (PBIRS) APIs to use for datasources (Paginated, PBI, and shared )
Hi all We are using PBIRS (latest release). I am a report developer and I am being asked to compile a list of username and connect strings, and eventually I'd like to be able to modify the username as well. It seems as if using an API is the best approach and I don't have much experience but I have created 2 scripts (below) and looking for general feedback. My requirements are to Retrieve a list of ALL Datasources ( of all 3 types ) with Connectstring and userID I have built 2 powershell scripts as follows (REST, I believe) $ReportServerURI = "<Reportserverserver>/Reports/" $session = New-RsRestSession -ReportPortalUri $ReportServerURI; $rsItems = Get-RsFolderContent -RsFolder $startingFolder -ReportServerUri $ReportServerURI -Recurse | Where-Object -Property "TypeName" -In "PowerBIReport", "Report"; foreach ($rsitem In $rsItems ) $rds = Get-RsRestItemDataSource -WebSession $session -RsItem $rsitem.Path; foreach ($d in $rds) { $DataSourceUser = $d.DataModelDataSource.Username $datasourceConnectString = $d.DataModelDataSource # I notice the connectstring is in here, so I think I can parse it out. This returns most of the fields for Power BI reports, but I was unable to find the values for paginated (Old SOAP API?) $uri = "Reportserver//ReportServer/ReportService2010.asmx?WSDL" } $reporting = New-WebServiceProxy -uri $uri -UseDefaultCredential -namespace "ReportingWebService" $reports = $reporting.ListChildren($startingFolder, $True) | Where-Object {$_.TypeName -eq "Report"} foreach($report in $reports) { $reportpath = $report.Path $dataSources = $reporting.GetItemDataSources($report.Path) foreach($dataSource in $dataSources) $DataSourceUser = $dataSource.Item.UserName $datasourceConnectString = $dataSource.Item.ConnectString This one seems to get most of the Paginated but not much on the PBI side.. I have read quite a few posts with code samples etc. regarding datasource information but wondering if anyone can explain whether one or the other API should be used for both (noteven sure about shared connections) or if it's possible to get Connectstring/username for both types of report (preferably shared also) Any information or links are appreciated.623Views0likes1CommentUnable to connect to Synapse Lake DB from Power BI report in PBIRS
This seems like it may be a limitation in the current version of Power BI Report Server (PBIRS), though I'm hoping we're just doing something wrong. If it is a limitation, I would love to see if we could get this on the product roadmap (product team!). In short, we have a Dataverse environment for which we have enabled Synapse Link, which creates a Lake DB database on synapse. In this style of database, SQL user authentication is not supported (the DB is exposed as a readonly replica, and thus we cannot "create user" on the DB). As a consequence, the only supported way to connect to the Synapse database is using organization/microsoft accounts. Using the PBIRS version of Power BI desktop, we are able to author such reports, work with datasources, etc. just fine. However, when it comes time to deploy to PBIRS, the only authentication methods that are available when configuring the data source are Windows Auth (i.e., on-prem windows/active directory) and Basic Auth (SQL users). Long story short, even though you could create a SQL user and grant the sysadmin role, which would allow the user to access the lakedb database, that user does not have permission to access the underlying resources in the Azure Storage Acccount (the data lake), and thus you cannot run queries or interact with the data. It seems that either the PBRIS platform needs to add support in data source configuration for data model data sources for Microsoft/Organizational autentication (see the screenshot below), or the Synapse team needs to figure out how to support SQL authentication on Lake DBs. Has anyone encountered and gotten past this problem? Are we maybe missing something? Separately, any chance the product team is interested in picking this up and supporting MS auth? thanks!!Solved1.6KViews0likes2CommentsSharepoint excel refresh in Power BI Report server
HI I have an excel file is in my sharepoint site. i can add it via web source and authentication i used is org account in Power BI desktop. Schedule refresh works fine in Power BI service. Where as same report schedule refresh is not working in Power BI Report server. I have tried, anonymus, windows and basic authentication none of them are not working. Power bi report server not supports sharepoint excel source for schedule refersh? mwegener Pragati113.9KViews0likes9CommentsJan 2019 PBIRS Cannot edit data sources
We upgraded from the Aug 2018 to Jan 2019 version of Power BI Report server. I am receiving complaints from some users that they cannot edit data sources or change the current data source of a report. The users have all of the rights available: Browser, Content Manager, My Reports, Publisher and Report Builder. Additionally, I added them as a System User. I uninstalled, rebooted, restored the database from a backup taken prior to upgrade and reinstalled PBIRS as a new install and we still have with the same issue. I also restored the encryption key from a backup taken before the upgrade. I appreciate your assistance.Solved4.9KViews0likes6Comments