Forum Discussion
Gateway 3000.310.1 crash loop: ArgumentOutOfRangeException + MSessions missing
Environment
- Gateway version: 3000.310.1 (March 2026)
- Server OS: Windows Server (Hyper-V VM)
- Services affected: Power BI scheduled refresh, Power Automate
Symptoms Since the auto-update to version 3000.310.1, the gateway service (PBIEgwService) is crashing repeatedly throughout the day. Power BI reports the error DM_GWPipeline_Gateway_SpooledOperationMissing on scheduled refreshes. The Windows System event log shows ID=7034 and ID=7031 (unexpected service termination with auto-restart), and ID=26 with exception code 0xe0434352 (unhandled .NET CLR exception).
Bug 1 - Missing MSessions directory The following error appears in GatewayErrors every ~65 seconds continuously:
[DM.Pipeline.DiagnosticsUploader] Failed to enumerate uploadable files.System.IO.DirectoryNotFoundException: Could not find a part of the path'C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\MSessions'
The MSessions directory does not exist and the gateway does not create it. This appears to be a regression in this version.
Bug 2 - ArgumentOutOfRangeException crashing the service This exception appears repeatedly in GatewayInfo logs and is the direct cause of the crash (confirmed via the 0xe0434352 event in System log):
System.ArgumentOutOfRangeException: The UTC time represented when theoffset is applied must be between year 0 and 10,000.Parameter name: offset at System.DateTimeOffset.ValidateDate(DateTime dateTime, TimeSpan offset) at System.DateTimeOffset..ctor(DateTime dateTime) at AdoNetMonitoredDbConnectionPool.CheckConnections(...)
The connection pool checker receives an invalid DateTime value (likely DateTime.MinValue from a stale connection entry) and the unhandled exception brings down the entire process.
Bug 3 - GatewayUpdateHost invalid version after crash After every crash, the following appears in GatewayErrors:
[DM.GatewayUpdateHost] Either current or target version 0.0.0.0 value is invalid.Timeline (UTC)
- 12/Apr 22:24 - First crash (ID=7034), immediately followed by auto-update to 3000.310.1
- 12/Apr 22:29 - Gateway back online on new version
- 12/Apr 23:38 - Second crash (ID=7031), preceded by Resource Exhaustion Detector warning (ID=2004) 20 seconds earlier
- 13/Apr 06:25 - Third restart
- 13/Apr 09:12 - Fourth crash (ID=26, exception 0xe0434352), gateway did not auto-recover
Workaround attempted Creating the MSessions directory manually reduces the DiagnosticsUploader noise but does not prevent the ArgumentOutOfRangeException crash in the connection pool.
Request Is there a known hotfix or a safe rollback path to the previous version? Has anyone else seen this on 3000.310.1?
3 Replies
- GilbertQ
Super User
What I would recommend doing is to rollback to the previous version and then see if the issue still persists. One thing to be aware of just to make sure is that you have got the recovery key before you uninstall. And reinstall to ensure that you do not lose all of your existing connections going through your Power API gateway. Here are the previous gateway installation files. https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-monthly-updates
- lbendlin
There is no rollback for gateway versions. Your only remedy is to uninstall the offending version, install a known good version, and reapply the configurations.
3000.298.10 seems to be reasonably stable (unless you use Azure Databricks).
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues . 
v-priyankataCommunity Support
