User Profile
pfarias
Advocate II
Joined 4 years ago
User Widgets
Contributions
Re: Gateway 3000.314.5 - Microsoft.Mashup.Container.NetFX45.exe crashes on Virtual Machines (GPU-les
Update: Tested version 3000.318.9 (May 28, 2026) A new Gateway version (3000.318.9) was released today and we tested it on the same VM environment. Result: Installation failed with the same error. Microsoft.Mashup.Container.NetFX45.exe continues to crash during service initialization with the same FatalError -2146233088 pattern, even with all previously documented workarounds applied: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = --disable-gpu --no-sandbox --disable-software-rasterizer --use-gl=swiftshader WEBVIEW2_USER_DATA_FOLDER = C:\GatewayWebView2Data with full permissions for NT SERVICE\PBIEgwService Current status: Staying on version 3000.310.1 (March 2026) which continues to work correctly. The Gateway is online and operational on this version. This confirms the issue is a persistent regression present in versions 3000.314.5 and 3000.318.9. The fix has not been included in the latest release. We will continue monitoring future releases and update this thread when a fix is confirmed.Re: On-premises Data Gateway 3000.314.5 - Microsoft.Mashup.Container.NetFX45.exe crashes on Virtual Mach
Update: Tested version 3000.318.9 (May 28, 2026) A new Gateway version (3000.318.9) was released today and we tested it on the same VM environment. Result: Installation failed with the same error. Microsoft.Mashup.Container.NetFX45.exe continues to crash during service initialization with the same FatalError -2146233088 pattern, even with all previously documented workarounds applied: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = --disable-gpu --no-sandbox --disable-software-rasterizer --use-gl=swiftshader WEBVIEW2_USER_DATA_FOLDER = C:\GatewayWebView2Data with full permissions for NT SERVICE\PBIEgwService Current status: Staying on version 3000.310.1 (March 2026) which continues to work correctly. The Gateway is online and operational on this version. This confirms the issue is a persistent regression present in versions 3000.314.5 and 3000.318.9. The fix has not been included in the latest release. We will continue monitoring future releases and update this thread when a fix is confirmed.Re: On-premises Data Gateway 3000.314.5 - Microsoft.Mashup.Container.NetFX45.exe crashes on Virtual Mach
Update — Additional tests performed based on your recommendations Thank you for the suggestions! Here is what happened after testing each one: 1. --use-gl=swiftshader flag Added to the existing WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS variable. The Gateway Updater installed successfully, but Microsoft.Mashup.Container.NetFX45.exe still crashes during the GatewayComponents installation step. 2. WEBVIEW2_USER_DATA_FOLDER environment variable Created C:\GatewayWebView2Data, granted full control to NT SERVICE\PBIEgwService, and set the variable. No change in behavior, crash persists. 3. Error 1920 workaround (clearing password on Log On tab) Windows does not allow saving the service properties without a password when using a service account, so this workaround could not be applied as described. 4. Switching to Local System account Changed PBIEgwService to run as Local System during installation. A new error appeared: "The service is marked as an interactive service. However, the system is configured to not allow interactive services." The crash continued regardless. Current status: Version 3000.314.5 remains uninstallable on this VM environment. The crash pattern suggests the Microsoft.Mashup.Container.NetFX45.exe requires an interactive desktop session that is not available in this virtual machine configuration. We are staying on version 3000.310.1 for now. If Microsoft releases a fix or a new version addresses this, we will test again and update this thread. Thanks again for the support, this is clearly a bug introduced in 3000.314.5 on GPU-less virtual machines.Gateway 3000.314.5 - Microsoft.Mashup.Container.NetFX45.exe crashes on Virtual Machines (GPU-less)
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]On-premises Data Gateway 3000.314.5 - Microsoft.Mashup.Container.NetFX45.exe crashes on Virtual Mach
Environment OS: Windows Server 2019 (Build 17763) Gateway version with issue: 3000.314.5 (April 2026) Gateway version working: 3000.306 (February 2026) Problem During installation, the service PBIEgwService fails to start with Error 1920. The root cause is that Microsoft.Mashup.Container.NetFX45.exe crashes repeatedly with the following error: Exception: System.Environment.FailFast Message: Unexpected exception in background thread of Mashup container (error code -2146233088) Event: CLR20r3 — FatalError The process crashes within seconds of being launched, preventing the service from starting and causing the installer to roll back. What was already checked .NET Framework 4.8 installed Windows Defender exclusions added for gateway folder and process Visual C++ Redistributable updated to 14.44.35211 WebView2 Runtime installed (147.0.3912.86) FIPS disabled Performance counters rebuilt with lodctr /R Windows fully updated (latest patch: KB5082414, April 2026) Partial workaround Setting the following system environment variable before installation resolves the crash on version 3000.306 but does NOT fix version 3000.314.5: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = --disable-gpu --no-sandbox --disable-software-rasterizer Conclusion Version 3000.314.5 introduced a breaking change in Microsoft.Mashup.Container.NetFX45.exe that causes it to crash on virtual machines without GPU acceleration, even with the WebView2 GPU workaround applied. Version 3000.306 works correctly with the same workaround. Has anyone else experienced this issue with the latest Gateway version on a VM environment? Is there a known fix or configuration to make 3000.314.5 work?Re: Power BI connection in Excel - Unable to sign into data connection
Not yet. I'm still using version 17928.20156. It seems to me that it was from version 18025.20096. It may be a coincidence, but they made some changes to the PivotTable TollTips for connected tables in OLAP. Tha version 18025.20160 and 18129.20116 doesn't either. The problem is that the last update, 18129.20158, had many security updates. In my case, if I update my users, they will not be able to use the functionality.Re: Converting Document display name from Y2020 è¡ä¸åºç¨æ¡ä¾å页æ±æ».pdf to normal character
If this is expected result, the erro is before the 'Y2020 行业应用案例å•é¡µæ±‡æ€».pdf'. Because these characters I'll not be convert to Y2020 行业应用案例单页汇总.pdf. Can you talk more about how is generated this encoding char?
