PBIRS Sep 2026 Bug? Publisher Role Users Cannot View Reports
Hi everyone, I recently upgraded our Power BI Report Server from the May 2026 release to the September 2026 release, and I encountered a critical change regarding user roles and permissions. The Issue: Prior to this update, users who only had the "Publisher" role on a dashboard or folder could successfully view the reports. However, immediately after upgrading to the Sep 2026 version, these users can no longer view their reports and are getting the following error message when trying to access them: "User permissions error: You do not have permission for this operation. Contact your administrator to obtain the necessary permissions." The Workaround: We found that explicitly adding the "Browser" role alongside the "Publisher" role resolves the issue. Since doing this manually for hundreds of dashboards and users was not feasible, I wrote a custom PowerShell script using the native PBIRS REST API to recursively scan the server and automatically grant the "Browser" role to any user who only had the "Publisher" role. My Questions for the Community: - Has anyone else experienced this exact issue after upgrading to the September 2026 release? - Is this an intentional security architecture change by Microsoft in this release, or is it a bug? Thanks in advance for your insights.
RS 2026 does not connect with sharepoint
Hi all, good afternoon. I am facing a problema. I have a base that's a spreadsheet that's in the sharepoint. I have a link. When I use a PB Desktop RS, the comunication works, but to update I need to click on the update button. Ok. Not a problema. But, when I upload the PBIX to the corporate RS, it doesn't communicate with the sharepoint. Ok. On the Microsoft documentation says that it would be working. But, does anyone have a idea ou a experience and got a solution? I tried to put the file on my computer, but liiks like the RS doesn't get a communication. It's seens to be a communication problem between RS and computer. Thanks
Input Slicer Filtering Rule Stops Working After Publishing to Report Server
Hi everyone, I have a question regarding the "Input slicer" visual in Power BI. I created an input slicer in Power BI Desktop and set the filtering rule to "Does not contain any". It worked perfectly in Desktop during my local tests, filtering data as expected. However, after publishing this report to our on-premises Power BI Report Server, the input slicer's behavior seems to have changed: The operator dropdown button is missing: The dropdown button that allows me to switch between operators (e.g., "contains", "does not contain") in Desktop is no longer visible on the server. Filtering logic appears different: When I enter a value, it seems to apply an exact match logic instead. Only when I type the complete and exact value can it filter the data. The "does not contain any" rule I originally set no longer seems to work. Has anyone else encountered this issue? What could be the possible causes? Is this due to limited support for the input slicer visual in certain Report Server versions, or could it be that I missed some important step before publishing? Just to add more details to this issue: I recently upgraded our Power BI Report Server from the September 2025 version to the May 2026 version (version 15.0.1121.120) I'd really appreciate any insights or suggestions! Thanks in advance.
Dynamic Subscription Sent Default Page instead of Report Page selected
Hi, My Power BI dashboard Dynamic Subscription is not working this month where it sent Default Page instead of Report Page selected. This is a monthly subscription and it is working fine last month. The subscription email received is with correct filter set but not the page selected, for example I set Page 2 but it give me Page 1 (the page I at when I saved and published). I have "Set as landing page" unchecked. Try recreate a new Dynamic subscription - not working. Try recreate a new Standard subscription - working. I google and cannot find a solution. Anyone with the same issue and found a solution? By the way the "Include my changes" is missing for me, I not sure is my admin set that or PBI recent updates removed that. Thanks in advance for any help~
Power BI Desktop Snowflake Refresh Fails: “Cannot Convert Null to Text” While Service Still Works
Hi all, I’m seeing a sudden Power BI Desktop refresh failure with Snowflake-backed Power Query tables. Has anyone else seen this with recent Power BI Desktop / Snowflake connector builds? Is there a known regression or recommended workaround? Power BI Desktop version: 2.155.756.0 Install type: Microsoft Store app Connector: native Snowflake connector Pattern: Snowflake queries fail in Desktop, but the same SQL runs successfully in Snowflake and the dataset/report still refreshes in Power BI Service. Representative M pattern: let Source = Value.NativeQuery( Snowflake.Databases( "<snowflake_account>", "<warehouse>", [Implementation="2.0"] ){[Name="<database>"]}[Data], "<native SQL query against a Snowflake view>", null, [EnableFolding=true] ) in Source Desktop refresh error: cannot convert the value null to type Text. Things already tried: Restarted machine Uninstalled/reinstalled Power BI Desktop Cleared/re-authenticated data source credentials Removed [Implementation="2.0"] Removed [EnableFolding=true] Replaced select * with explicit column casts Tested multiple Snowflake queries/tables
Sequence contains more than one element June update 2.155.756.0 & SAP BW Direct query
Hi we are currently experiencing this issue on June update of Pbi - error message: Sequence contains more than one element. Data source SAP business app server, direct query. All reports are not working. Also unable to create new ones. Any idea what went wrong? On SAP side there were no changes. Feedback Type: Frown (Error) Timestamp: 2026-06-15T13:34:11.4197245Z Local Time: 2026-06-15T15:34:11.4197245+02:00 Session ID: 02a75b59-23ab-4021-b050-d811b24249da Release: June 2026 Product Version: 2.155.756.0 (26.06)+7f1da5803bfe48beff98093405280405ddb467dd (x64) Stack Trace: System.InvalidOperationException at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source) at Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions.GetCubeDataSourceType(INamedExpression namedExpression) at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.BuildQuery(IQueryableObject obj, IModelingQueryBuilder queryBuilder, IEnumerable`1 queryGroups, TwoWayDictionary`2 modelObjectNameToRuntimeIdMap) at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.BuildQueries(IDataModel dataModel, IModelingMashupDocumentBuilder mDocumentBuilder, TwoWayDictionary`2 modelObjectNameToRuntimeIdMap) at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.GenerateQueriesFromModel(IDataModel dataModel, IModelingMashupDocumentBuilder mDocumentBuilder, TwoWayDictionary`2 modelObjectNameToRuntimeIdMap) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.GenerateRestorationInputFromModel(IDataModel dataModel, IMashupDiscoveryService mashupDiscoveryService) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.GenerateAndRestoreQueriesFromModel(Report report, IDataModel dataModel, Boolean restoreQueriesToReport) at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.<SetAnalysisServicesDatabaseToReport>d__1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Services.PowerBIPackagingService.<Open>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Services.BiPackageOperationHandler.<LoadArtifact>d__27.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.<>c__DisplayClass58_0.<<ExecuteAndHandleFileOpenErrors>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBITelemetryServiceExtensions.<EmitStandardizedClientReportingEventWithDebugEvent>d__7`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.<ExecuteAndHandleFileOpenErrors>d__58.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.<>c__DisplayClass37_0.<<OpenArtifactAndSetAsCurrent>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.<>c__DisplayClass19_0`1.<<BlockUIAndRun>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion[T](Task`1 task) at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod, PowerBIProgress progress, String activityId) at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.OpenArtifactAndSetAsCurrent(IPowerBIWindowService windowService, IPowerBIArtifact artifactToOpen, IExceptionHandler exceptionHandler, Nullable`1 entryPoint, ReloadFileOptions reloadFileOptions) at Microsoft.PowerBI.Client.CommandLineFileService.TryOpenOrCreateReport(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, Boolean forceCreate) at Microsoft.PowerBI.Client.AppReportFlow.<OpenExistingReport>d__50.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Client.AppReportFlow.<OpenExistingReport>d__50.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.AppReportFlow.<ContinueLoadWithMainWindow>d__43.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.AppModule.<>c__DisplayClass4_2.<<Run>b__4>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.MainWindow.<<ActivateMainWindow>b__41_1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext() PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.155.756.0","ModuleName":"Microsoft.PowerBI.Modeling.Engine.dll","Component":"Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions","Error":"System.InvalidOperationException","MethodDef":"GetCubeDataSourceType","ErrorOffset":"32","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.26200.0 (x64 cs-CZ) CLR Version: 4.8 or later [Release Number = 533509] Peak Virtual Memory: 85.8 GB Private Memory: 296 MB Peak Working Set: 425 MB IE Version: 11.1882.26100.0 User ID: 8076080c-4640-48db-9342-e6360ebde53c Workbook Package Info: 1* - cs-CZ, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Empty Model Version: PowerBI_V3 Disabled Preview Features: PBI_DatabricksAdbcVersionEnabled PBI_googleBigQueryAdbcVersionEnabled PBI_UseRedshiftODBCV2 PQ_UseBaseViewXmlForSharePoint PBI_snowflakeLegacyOdbcVersionEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_scorecardVisual PBI_onObject PBI_setLabelOnExportPdf PBI_oneDriveSave PBI_oneDriveShare PBI_useModernPublishDialogs PBI_publishDialogsSupportSubfolders PBI_gitIntegration PBI_tmdlInDataset PBI_enhancedReportFormat PBI_enhancedReportFormatPBIX PBI_advancedSlicerTypeList PBI_useModernMashupEditor PBI_aiNarrativesVisual PBI_customCalendars PBI_copilotUnifiedTooling MashupFlight_EnableOracleBundledOdacProviderV2 PBI_enableOracleBundledOdacProviderForDQ PBI_sqlDbNativeArtifactsOnDesktop PBI_warehouseSnapshotArtifactsOnDesktop PBI_dynamicCalcColumn PBI_newVisualDefaults2026 PBI_enableExportQueries PBI_DesktopNamedPipeBridge PBI_dateSlicerPreselectionAuthoring Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud DPI Scale: 150% Supported Services: Power BI WebView2 Runtime Version: 149.0.4022.69 WebView2 SDK Version: 1.0.2365.46Issue: Oracle Cloud Connection created without centralized On-Premesis Gateway and can't delete it.
Hello, this problem recently happened on Friday, and I think I am up a creek without a paddle. I have a Power BI Pro license using the On-Premises Gateway (Personal mode) for refreshes. The company does not have a standard On-Premises Gateway installed and configured. We use Oracle database for alot of our backend data. I just recently upgraded to the June 2026 update of Power BI Desktop with all preview features enabled. All of my reports that use Oracle are connected with the native Oracle database connector that utilize the personal gateway. Somehow, a Cloud version of the Oracle connector got created on the service, and nothing will connect because we do not have a standard gateway. I have tried deleting the Oracle cloud connections and trying to rebind it with a new file, but, it just keeps coming back. This article states if this happens, this is irreversible: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-connect-oracle-database. However, I don't understand how it could be created without an installed centralized gateway? How can I fix this? I'm open to extreme steps at this point, minus getting the centralized On-Premises installed, because that is not going to happen this year. If I have to get our vendor to reset my entire workspace and license to start from scratch, I'm willing to do that, assuming it will actually work. Any suggestions would be helpful. I really need to be able to use the native Oracle connector with the personal gateway.
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
