Unable to upload PBIX files
Hi there, We are getting the following error when trying to upload reports to our report server. It was at the January 2026 version and we tried to update it to May 2026 version to see if that resolved the issue, but we get the same message with the May version as well. We had previously been able to create reports in the January 2026 desktop version and upload them to the server okay and have also tried to create reports in May 2026 desktop version and upload but nothing seems to work. Our live server (January 2026 still) still works okay. We can upload PDFs or text files to the server okay. It just seems to throw the error when you try to upload a PBIX file. If i check the console when I try to upload any reports we get the following error: and have checked the server logs and get the follwoing polyfills-KEOJFKRO.js:1 POST https://XXXXXXXXX/Reports/api/v2.0/catalogitems 422 (Unprocessable Entity) (server address removed) We have tried googling those to see if there is a fix or known issue for that but can't really find any information on those 2 errors. We have checked the certificates on the server and they seem to be okay and have the correct binding. We are at a bit of a loss on how to resolve this - does anyone have any ideas? Thanks Denise
Can't export full .pbix + can't publish after live connection workaround
Can't export full .pbix + can't publish after live connection workaround Hi community, I've been running into a frustrating chain of issues over the past few days and wanted to see if anyone else is experiencing the same. Issue 1: Can no longer export .pbix with data I have reports that I've successfully downloaded as .pbix (full copy with data) many times before. Suddenly, I'm getting the error: "We couldn't export to .pbix format." The only download mode that works now is "A copy of the report with a live connection to the data online" — the full data export fails every time. For context: - The report was originally published from Power BI Desktop (not created in the Service) - Large dataset storage format is OFF - No incremental refresh configured - The tables are not large at all, so dataset size shouldn't be a factor - No deployment pipeline involved Issue 2: Can't publish after editing the live connection .pbix After making report edits in Desktop using the live connection file, I tried to publish back to the service and got this error: "An error occurred while attempting to publish 'Report Name.pbix': The remote server returned an error: (404) Not Found." My questions 1. Is anyone else suddenly unable to export full .pbix files from reports they previously could download without issues? 2. Is there a known issue with the UK South region affecting exports and publishing? 3. Any workaround to publish a live connection .pbix back to the service? Thanks in advance, any help or confirmation that others are seeing this would be really useful!not getting updated dataset when downloading data from powerbi reporting server
I have a dashboard that is updated as of yesterday but when i download the dashboard pbix file the data in that pbix file is old not updated as of yesterday. does anyone know how to get the updated pbix file directly from the reporting server. here is a snapshot
Unable to upload PBIX file to PBI Report server
Hi everyone I have problem with uploading PBIX file to report server May 2021. I have a fresh installation of PBI Report Server and old one on with I have made upgrade Januarry 2020 to May 2021. In both cases I'm not able to upload PBIX file. I can upload RDL and Excel file with no problems, but not PBI. I have created simple PBI file in May 2021 Desktop application. Software version PBI Reports Server Version1.11.7815.26414(May 2021) PBI Desktop Version: 2.93.1681.0 64-bit (maj 2021) Windows Serwer 2019 [Version 10.0.17763.2061] The error I'm getting is An error has occurred. There was an error uploading your .pbix file. Verify that the file has not been corrupted and that the file extension matches the format of the file. I have checked log files and I see HTTP 422 error When I track web browser communication I also get error 422. Please help to resolve this.Is there a way to auto extract a template PBIT from a PBIX file or get a PBIT from the PBIRS API?
We are trying to use the Power BI on-prem API to Get all the reports and download them to a folder (we were able to POC this). Then we would like to extract the template file -or- remove all data from the files so we could check them into source control. Because these reports can be very large and contain very sensitive data, we need the data scrubbed from the files. Is there a way to do this?
PowerShell - deploy and Update PBIX on Report Server
Hello Community, I have used theses lines in order to deploy a pbix file on Report Server : $session = New-RsRestSession -ReportPortalUri http://lservername/Reports Write-RsRestCatalogItem -WebSession $session -Path "C:\2019\mypbix.pbix" -RsFolder "/MyFolder" It is working fine. Now, when I need to update the bix with another version , I used the same command bellow but I am getting this error : Write-RsRestCatalogItem : System.Exception: Failed to create catalog item: The remote server returned an error: (409) Conflict. ---> System.Net.WebException: The remote server returned an error: (409) Conflict. at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request) at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord() --- End of inner exception stack trace --- At line:1 char:1 + Write-RsRestCatalogItem -WebSession $session -Path "C:\2019\PwC Acade ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-RsRestCatalogItem Does any one please have an idea about hte command PowerShell that could update apbix previously on the Server please by a new version ? Many thanks Best Regards, AsmaIssue with Gateway with only one report
Hello everyone, Has anyone ever run into an issue where a specific Power BI pbix file seemed to have adverse affects on your on prem gateway? I had a specific report that was connecting to an AWS Redshift data source and every time I would refresh the report in app.powerbi, I would get an error message saying that the gateway ran into an issue and the gateway may have been restarting (common error it seems like). But it would only happen with that report. It also appeared, although I can't confirm, that the gateway was crashing when I would try to refresh this report and then would restore itself some time later. I ended up rebuilding it completely from scratch with a new pbix file. Additional details, all of our reports use AWS Redshift as a data source. They all connect to the same cluster.Enterprise reporting artefact deployment strategies with PBIRS
We have a problem currently with the fact that .pbix files are very different from any other SSRS reporting artefact in terms of enterprise readiness for deployments. We have a full-featured deployment system that can deploy entire trees of reporting artefacts along with replacing datasource definitions at deploy time depending on the target environment (DEV/TRAIN/PROD) etc. This has been working nicely for years but now we are moving to PBIRS and away from SSRS native mode, users want to be able to deploy .pbix artefacts in the same way. This seems to be basically impossible because: The file format of .pbix is not editable programatically (unlike every SSRS artefact) and so data sources cannot be changed directly which means they have to be uploaded to PBIRS and then changed with the REST API .... but ... Datasources inside a .pbix file have no name and even the ids change every time the file is deployed to a PBIRS server. So, there is no way of matching datasources to the database of connections we use to determine datasources for a target environment during deployment. These issues make .pbix files really poor in terms of enterprise deployments. If anyone knows any way around these issues, I would be interested ... It really is a basic part of any enterprise grade managed reporting solution to be able to change reports (datasources, parameters, cacheing etc). during deployment depending on the target enviromnent.
