Hi, Ever since the June 2026 update (gateway standard mode, v3000.322.4), our dataset refreshes keep failing intermittently with DM_GWPipeline_Gateway_DataSourceAccessError. It's an on-prem SQL source, import mode, West Europe. Smaller queries are fine, but the big/long-running ones fail fairly often. It worked fine on the previous build. Digging into the gateway logs, the real error isn't the data source — it's an internal cast exception: InvalidCastException: Unable to cast object of type '...Communication.OperationExecutingAsynchronouslyResult' to type '...Communication.ExecuteQueryResult' After that it cascades into "The spooled operation id ... does not exist. Evict code: -1", "The data reader has been closed", "The command has been canceled", and the refresh dies. Looks like an async query result is being cast to the synchronous result type and blowing up. Things I've already ruled out: renewed the credentials (auth succeeds in the logs, the connection opens fine and it only fails mid-stream), scaled the host to 8 vCores / 12 GB (no change), and the port test passes 33/33. So it's not creds, resources or network. Is this a known regression in 3000.322.4? And if so, is there a fixed build out, or a build you'd recommend rolling back to in the meantime? Happy to share full logs privately. Thanks ... View more

Hello, In the June 2026 release, the option to set the key column seems to be missing ? Previously, the option was available below the Row label dropdown but is now gone.   However, the columns that were set as key column in a table, still have the key (passport) icon in front of them.     With the option to set the key column gone, it is not possible to add a new key column or to choose a different column as a key column. Please bring back the option in Power BI desktop. Setting the option in the TDML view is less user friendly.  ... View more

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 ... View more

TL;DR: Since ~2026-06-30, any Lakehouse Delta table with a non-ASCII character (æ/ø/å) in its name fails on the SQL analytics endpoint with "underlying location does not exist". The files exist in OneLake and read fine via Direct Lake/Spark/raw OneLake. Looks like a regression in how the endpoint encodes non-ASCII characters in the OneLake file path at read time. Worked the day before with no changes on our side.   Summary Starting around 2026-06-30, querying any Lakehouse Delta table whose name contains non-ASCII characters (e.g. Norwegian æ, ø, å) through the SQL analytics endpoint fails with "underlying location does not exist". The same tables were queryable the day before with no changes on our side. The underlying data is intact and fully readable through other paths (Direct Lake, Spark, raw OneLake). This appears to be a regression in how the SQL analytics endpoint URL-encodes non-ASCII characters when building the OneLake file path at read time.   Impact All tables with æ/ø/å in the name are unreadable via the SQL analytics endpoint (T-SQL, DirectQuery, and the Fabric portal table preview, which runs a SELECT under the hood). Reproduced across multiple independent lakehouses and workspaces in the same tenant. ASCII-named tables are unaffected. Direct Lake models and Spark are unaffected.   Environment Fabric Lakehouse SQL analytics endpoint. Reproduced in more than one lakehouse/workspace on the same tenant. Capacity ID and region can be provided privately if a repro is needed.   Exact error Failed to complete the command because the underlying location does not exist. Underlying data description: table 'dbo.Ødegård', file 'https://onelake.dfs.fabric.microsoft.com///Tables/Ødegård/part-00000-...snappy.parquet'.   Reproduction Create a Delta table with a non-ASCII character in its name, e.g. Spørreskjema.  Query it via the SQL analytics endpoint: SELECT COUNT(*) FROM dbo.[Spørreskjema]. Result: the error above. An equivalent ASCII-named table in the same lakehouse returns rows normally.   Diagnostic evidence: The physical parquet files exist in OneLake and are byte-addressable only at the correct UTF-8 path. We requested the exact same file via the OneLake DFS API using different encodings of the ø in the folder name, and got: %C3%B8 (UTF-8, the correct encoding): 200 OK, the file exists. %F8 (Latin-1): 404 Not Found. %C3%83%C2%B8 (double-encoded UTF-8): 404 Not Found. Raw / unencoded ø: 404 Not Found. In other words, OneLake stores and serves the folder name as UTF-8 (NFC) and is byte-exact about it. Only the correct UTF-8 encoding resolves; every other encoding returns not-found. The SQL analytics endpoint is evidently requesting the file with a non-UTF-8 encoding of the non-ASCII character, so OneLake returns not-found even though the file is present. The catalog table name itself is correct clean UTF-8; the fault is in the path construction at read time.   Corroborating signals: Direct Lake (VertiPaq) reads the same æ/ø/å tables correctly, verified via DAX COUNTROWS. This is because Direct Lake uses a different read path than the SQL endpoint and encodes the OneLake path correctly. refreshMetadata on the SQL endpoint does not help. It returns NotRun for existing tables, reporting them as already synced. And a brand new shortcut or table with a non-ASCII name syncs with status Success but still fails to read. So this is not a stale-metadata or sync issue.   Timeline 2026-06-29 ~08:00: tables with æ/ø/å queried successfully via the SQL endpoint. 2026-06-30 (early): the same que change, no rename, no redeploy onour side. Delta commits before and after are identical WRITE/Overwrite operations. 2026-07-01: still failing.   Current workaround For consumer-facing tables we added ASCII-named OneLake shortcuts pointing to the same data, plus SQL views that keep the original table names. Consumers can then read again using the exact same names as before. This is a temporary bridge, not a fix. ... View more

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.46 ... View more

Hi all, I’m seeing recently a recurring issue in Power BI Desktop where a brief CMD window appears during report load and sometimes during semantic model-related changes. After digging into it, I found that the CMD window is actually SQLDUMPER.EXE. From what I understand, SQLDUMPER.EXE is a Microsoft diagnostic utility that gets triggered when an internal Microsoft component crashes or throws an exception. In this case, the actions seem to be tied to msmdsrv.exe, which is the backend model/query engine used by Power BI Desktop. What the issue looks like The black CMD window appears briefly. It first happens while the report is opening, specifically during “Preparing report”. It can also happen later when making changes that affect the semantic model, for example renaming a field or making other model-related modifications. The issue does not seem to be a simple visual/UI problem. It looks more like the backend model engine is hitting an exception and SQLDUMPER is collecting a dump. My troubleshooting so far Confirmed the CMD window is SQLDUMPER.EXE Using process monitoring, I confirmed that the CMD window is SQLDUMPER.EXE. Looking deeper, the process triggering it appears to be msmdsrv.exe, which is the Analysis Services/model engine running behind Power BI Desktop. No issue with a PBIX that has no external file connection In my tests, the issue does not appear when the PBIX contains only embedded data and no external data source connection to a file. You can simulate it just entering a dummy data using "Enter Data" in power bi. Issue will not happen on those reports. Happens in both Store version and downloaded version I tested both: the Microsoft Store/App version the downloaded installer version The issue happens in both. Preview features do not seem to be the root cause Turning off some preview features, such as On-object interaction, seemed to reduce the frequency somewhat, possibly because they trigger semantic model changes more often. However, this did not solve the issue completely, so I do not think this is purely a preview feature problem. Cache clearing and fresh install did not fix it I tried: clearing cache fresh installation switching to the downloaded version None of these resolved the problem. Running Power BI as Administrator prevents the issue While investigating logs, I noticed some apparent file access-related problems involving msmdsrv.exe. That led me to try Run as administrator. When I ran Power BI Desktop as Administrator, the issue did not appear. I even turned all preview features back on and tested again as Administrator, and it still did not happen. Moving the PBIX to a simple local folder did not help I also moved the report to a simple folder path such as: C:\test. This did not solve the issue. Current conclusion So far, on my machine, the only thing that prevents the issue is running Power BI Desktop as Administrator, which is obviously not a real solution. At this point, I suspect this may be one of the following: a Power BI Desktop bug a permissions / file access / credential issue something related to external data source connections possibly some interaction between the local Analysis Services engine (msmdsrv.exe) and file-based external sources Main questions Is anyone else seeing SQLDUMPER.exe appear during “Preparing report” or during semantic model changes? Has anyone identified the exact trigger? Has Microsoft acknowledged this anywhere? Is there any proper fix besides running Power BI as Administrator? Thanks in advance. I’m sharing this in case it helps others narrow down the issue. ... View more

This morning, several of my Power BI dataflows are failing with the following message:   "We encountered an error during evaluation. Details: An error occurred while communicating with another service, please try again later. If this problem recurs, please contact support with this message."   Is anybody else experiencing the same? I'm not aware of anything changing in our setup overnight, so can only asssume a service issue? ... View more

The 'Microsoft 365 Usage Analytics' template app has been failing since the 8th of May giving "DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (500) Internal Server Error.. Microsoft.Data.Mashup.ErrorCode = 10122. Microsoft.Data.Mashup.ValueError.DataSourceKind = OData. DataSourcePath = https://reports.office.com/pbi/v1.0/556f4662-c7de-4312-9a81-dd4e68521c32. . The exception was raised by the IDbCommand interface."   When trying to authenticate I get: "Failed to update data source credentials: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 3 and 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (404) Not Found. (Not Found)"   This suggests to me that something has changed on the Microsoft side.  The template app itself feels a little out of date already but our business does find some of its output very useful.  The template app did receive some updates back in Feb, so not abandoned by Microsoft.     ... View more

Since updating to the March 2026 version of Power BI Desktop, I am unable to connect to a specific Tabular model on Azure Analysis Services (AAS). Error Message: "The connection failed. An error occurred while trying to connect. Details: Could not connect to the Analysis Services server because the connection timed out or the server name is incorrect.". Key Findings: Regression: The connection works perfectly with the November 2025 version of Power BI Desktop on the same machine and with the same credentials/network. Specific Context: The issue occurs only with one specific Tabular model, while others remain accessible. Community Feedback: Other users and clients have reported similar connectivity issues specifically with the latest March 2026 update. Steps to Reproduce: Open Power BI Desktop (March 2026 version). Select "Get Data" > "Azure Analysis Services database". Enter Server and Database name (Connect Live). Error appears after a short attempt. Environment Details: Current PBI Desktop Version: 2.151.1182.0 Previous Working Version: November 2025 Data Source: Azure Analysis Services (Tabular) Authentication: Azure Active Directory - Universal with MFA ... View more

Microsoft Fabric down?   Localization: Europe   Can anyone confirm ? ... View more

Issue Summary I found a reproducible issue in Microsoft Fabric Dataflow Gen2 when using SAP BW Application Server as the source and Lakehouse table as the destination. The Dataflow Gen2 can refresh successfully if the Lakehouse destination was already configured. However, when I try to open the destination settings and rebind the query to an existing Lakehouse table, the destination wizard fails with the error: Value should be defined This happens during the destination selection / binding step, not during data preview or refresh. Source Type SAP BW Application Server through Power Query / Dataflow Gen2. The query uses SAP BW cube functions such as: SapBusinessWarehouse.Cubes Cube.Transform Cube.ApplyParameter Cube.AddAndExpandDimensionColumn Cube.AttributeMemberProperty Cube.AddMeasureColumn Destination Microsoft Fabric Lakehouse table. The original load was created using the default Lakehouse destination and completed successfully. The Lakehouse table was created and refresh worked. Later, I tried to change/rebind the destination manually to the same existing Lakehouse table and change the loading method from Replace to Append. At that point, the destination wizard failed with: Value should be defined Important Finding I tested the same destination behavior with other sources: Source Rebind to existing Lakehouse table SharePoint Excel Works Table from another Dataflow Works SAP BW source Fails This suggests the problem is not caused by Lakehouse permission, workspace permission, table existence, or the destination wizard in general. The issue appears to be specific to SAP BW source metadata / Cube.Transform schema validation during Dataflow Gen2 destination binding. Reproduction Steps Create a Dataflow Gen2 in Microsoft Fabric. Use SAP BW Application Server as the source. Build a query using SAP BW cube functions such as SapBusinessWarehouse.Cubes and Cube.Transform. Configure a Lakehouse table as the destination. Run the dataflow. The first refresh completes successfully. Reopen the Dataflow Gen2. Open the Data destination settings. Select manual/custom destination. Choose an existing Lakehouse table. The wizard fails with: Value should be defined Expected Result The destination wizard should allow selecting an existing Lakehouse table and saving the destination mapping. It should support normal destination configuration such as Replace or Append, the same way it works for SharePoint Excel or another Dataflow table source. Actual Result The destination wizard fails before the mapping can be saved. The dataflow itself can still refresh if the previous destination configuration already exists, but I cannot safely rebind or modify the destination settings. Business Impact This blocks production setup for SAP BW ingestion into Fabric Lakehouse. We need to load SAP BW data incrementally into Lakehouse, but cannot reliably configure an existing Lakehouse table destination with Append mode using Dataflow Gen2 when the source is SAP BW. Current Workaround Use Dataflow Gen2 only to extract SAP BW data into a staging Lakehouse table with Replace mode. Then use a Fabric Notebook or SQL process to load data into the final table, for example: SAP BW ↓ Dataflow Gen2 ↓ Lakehouse staging table - Replace ↓ Notebook / SQL delete-insert or merge ↓ Final Lakehouse Delta table This avoids relying on Dataflow Gen2 existing-table destination rebinding for SAP BW queries. Request Please investigate whether this is a known Dataflow Gen2 issue with SAP BW source queries and Lakehouse destination binding. Specifically, please check whether Dataflow Gen2 has a bug or limitation when resolving schema metadata from SAP BW / Cube.Transform queries during existing Lakehouse table selection. Error Details Error message: Value should be defined Session ID from error dialog: ee47c976-888c-408f-ab30-60d3245b00f6 Environment Product: Microsoft Fabric Feature: Dataflow Gen2 Source: SAP BW Application Server Destination: Fabric Lakehouse table Issue area: Data destination / existing Lakehouse table binding ... View more

Issue Summary The On-premises Data Gateway version 3000.314.5 (released April 27, 2026) fails to install on Virtual Machines without GPU acceleration. The previous version 3000.310.1 installs correctly on the same environment with a workaround.   Environment OS: Windows Server 2019 Standard (Build 17763.8644) Machine type: Virtual Machine (no GPU acceleration) .NET Framework: 4.8 (Release 528049) WebView2 Runtime: 147.0.3912.86 Visual C++ Redistributable: 14.44.35211 Gateway version failing: 3000.314.5 Gateway version working: 3000.306   Steps to Reproduce Provision a Windows Server 2019 VM without GPU acceleration Download and run the Gateway installer version 3000.314.5 Observe the installation failing at the service start step   Error Details From Windows Event Log: Application: Microsoft.Mashup.Container.NetFX45.exe Framework Version: v4.0.30319 Description: The application requested process termination via System.Environment.FailFast Message: Unexpected exception in background thread of Mashup container (error code -2146233088) Exception: CLR20r3 — FatalError   From MSI log: Product: GatewayComponents -- Error 1920. Service 'On-premises data gateway service' (PBIEgwService) failed to start. Return value 3.   Additional log evidence: Even with all workarounds applied simultaneously (--disable-gpu, --no-sandbox, --use-gl=swiftshader, WEBVIEW2_USER_DATA_FOLDER), the MSI log confirms the installer returns 1603 with Return value 3 at the INSTALL action, consistent across all attempts on this environment.     Workarounds Attempted — None resolved on 3000.314.5 Workaround Result --disable-gpu --no-sandbox --disable-software-rasterizer ❌Crash persists --use-gl=swiftshader added ❌Crash persists WEBVIEW2_USER_DATA_FOLDER set with full permissions ❌Crash persists Visual C++ updated to 14.44.35211 ❌Crash persists Windows Defender exclusions added ❌Crash persists Performance counters rebuilt (lodctr /R) ❌Crash persists Service account changed to Local System ❌New error: "service is marked as interactive" Working Workaround Version 3000.306 installs successfully on the same VM with the following environment variables: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = --disable-gpu --no-sandbox --disable-software-rasterizer --use-gl=swiftshader WEBVIEW2_USER_DATA_FOLDER = C:\GatewayWebView2Data   Expected Behavior The Gateway should install successfully on Virtual Machines without GPU acceleration, as it did in version 3000.306. Actual Behavior Microsoft.Mashup.Container.NetFX45.exe crashes with a fatal error during service initialization, causing the installer to roll back. This appears to be a regression introduced in version 3000.314.5. Additional Context The crash occurs because Microsoft.Mashup.Container.NetFX45.exe requires an interactive desktop session that is not available in VM service context The --use-gl=swiftshader flag (SwiftShader CPU fallback) does not resolve the issue in this version Community thread with full investigation details: [Re: On-premises Data Gateway 3000.314.5 - Microsof... - Microsoft Fabric Community] ... View more

Starting yesterday, many people in our organization are receiving this error when trying to refresh the Azure Analysis Services model in Excel.    Internal error: An unexpected error occurred (file 'Error.cpp', line 215, function 'err::BaseError::   We use Okta SSO to connect. We've never had this issue.    Note, initially we were receiving this error:   Errors in the OLE DB provider. The connection string includes explicit user identity and additional authentication options, such as 'Interactive Login' or 'Identity Mode', which is not supported. Either remove the user identity or omit the additional authentication options.   We removed User ID from the connection definition but then started receiving the other error.    It seems to work after clicking ok but not always.      Microsoft® Excel® for Microsoft 365 MSO (Version 2605 Build 16.0.20026.20168) 64-bit     ... View more

Good Day,   Occassionally I filter tables using a Table View to copy filtered results to use outside of Power BI - I.E. in Excel.   As of today it appears that when copying the Table View that has been filtered, it ignores the filters and copies the whole table. This is an issue for me as when I have a table in excess of 700,000 rows it makes this process extremely slow to copy from Power BI, and near impossible to paste it into Excel.   I have already tried uninstalling and reinstalling the program.   Is anyone else experiencing this issue?   As an example, we are a service company and we have a geographic alignment for our field service team. Simply, filtering a table by the "East" Region and trying to copy the table when filtered to the East is not working. Instead, the entire table is copied.   ... View more

To connect to our IBM DB2 database, we need to set a custom "packageCollection" value as an additional connection property in a copy activity.   However, when inspecting the pipeline's JSON, we noticed that "packageCollection" is added with a trailing space ("packageCollection "). This causes issues, as the DB2 database doesn’t recognize the property correctly.   Manually removing the space in the JSON makes the pipeline work again, so for anyone facing the same issue, that’s a temporary fix. But ideally, this bug should be resolved at the source.   As it stands, fixing it manually means the property can’t be configured through the UI anymore.   ... View more

Hi, Note: Issue noticed in unreleased July 2025 edition of PBI Desktop.   I m using Field Parameters on Rows of the Matrix and trying to provide dynamic selection for the users. However, the functionality stops after making slicer selection a couple of times and expand/ drill down buttons no longer works.   For the selection as shown in snapshot below, I would expect the user to expand and see Col2 and Col3 in the matrix visual. However.  no matter how many times you click, its not possible to expand. It is not dependent on the order of selection of columns or layout configuration in use. Request you to address the issue ASAP.     Sample PBIX is available at the below link: Test/Test Matrix.pbix at main · modi123p/Test   Thanks & Regards, Madan Prabhakara ... View more

The copilot narrative is not able to produce a percentage with more than two decimals when connecting to a "composite model" data set measure.   For example, if the number format in the base (parent) semantic model is 36.53% then Copilot Narrative will ALWAYS produce .36 (without the proper percentage format) in a composite model vs 36.53% when connecting to the parent data set directly.    Similarly it will not pick up on currency formatting in a composite model.    Steps to reproduce: Build a power BI data set with a measure that produces 36.53% Publish and create a copilot narrative  Create a second PBIX with composite model based on the first semantic model Publish and create a copilot narrative  Compare the result The first narrative will show 36.53% and the second will show .36   This does not seem to be an LLM issue. The narrative output is consistently missing the decimals and percentage sign via a composite model.  ... View more

Hi, Since the update July 2025, Matrix visuals with fields parameter hierarchies show a confusing behavior when one field is on different hierarchy levels. To illustrate the issue I created a test report with the following field parameter:   FP_Test = { // Group1 ("Category", NAMEOF('Product'[Category]), 0, "Group1"), ("Business Type", NAMEOF('Reseller'[Business Type]), 1, "Group1"), // Group2 ("Country", NAMEOF('Sales Territory'[Country]), 10, "Group2"), ("Category", NAMEOF('Product'[Category]), 11, "Group2"), // Group3 ("Business Type", NAMEOF('Reseller'[Business Type]), 20, "Group3"), ("Color", NAMEOF('Product'[Color]), 21, "Group3") }   The fields "Category" and "Business Type" are part of 2 hierarchies but on different levels. The visual looks like this:   If I now switch to Group2, I get the following display:   For the users, it looks as if the button did not work, as the category is still displayed. They can't even recognize that they are at a drilled down level because no +/- signs and no elements of the next higher hierarchy are displayed.  Switching now to Group3 it gets completely weired because only the lowes level ("Color") is visible whereas the user would expect to start with "Business Type". The users have to be very experienced to notice that they are looking at a drilled down level and need to drill up  to see the full hierarchy for this group:   Starting with an expanded hierarchy in Group1, it is not apparent in which case the hierarchy remains expanded, when it is collapsed and when a drill down takes place without a top level hierarchy. Anyway, a hierarchy that is expanded by default is not recommended or possible for a large number of hierarchy elements.   The same behavior applies to bar charts and column charts, where it is even more difficult to recognize that it is a next lower level and you have to drill up.   Please add a formatting option to all visuals that works with the drill-up/drill-down functionality, where the developer can choose whether the matrix/chart should collapse when switching the dimensions or retains its expanded state.   And if a matrix/chart retain the expanded state, please add the upper levels as well! I'm working as BI Consultant for customers and they complain about this new behavoir, because it appears as if the dynamic doesn't work anymore. I don't want to go back to bookmarks switching between various matrix visuals.   Thanks and best regards! ... View more