We get these seemingly randomly, maybe once or twice a week on a couple datasets. Today, it hit 3 datasets.
Last refresh failed: Tue Jun 07 2022 06:24:44 GMT-0400 (Eastern Daylight Time)
There was an error when processing the data in the dataset.Hide details
Data source error:
DataSource.Error: <pii>Microsoft SQL</pii>: <pii>Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. This failure occurred while attempting to connect to the routing destination. The duration spent while attempting to connect to the original server was - [Pre-Login] initialization=48; handshake=26; [Login] initialization=0; authentication=0; [Post-Login] complete=5; The duration spent while attempting to connect to this server was - [Pre-Login] initialization=30202; handshake=6; </pii>. DataSourceKind = <pii>SQL</pii>. DataSourcePath = <pii>n2y.sql.azuresynapse.net;Production</pii>. Message = <pii>Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. This failure occurred while attempting to connect to the routing destination. The duration spent while attempting to connect to the original server was - [Pre-Login] initialization=48; handshake=26; [Login] initialization=0; authentication=0; [Post-Login] complete=5; The duration spent while attempting to connect to this server was - [Pre-Login] initialization=30202; handshake=6; </pii>. ErrorCode = <pii>-2146232060</pii>. Number = <pii>-2</pii>. Class = <pii>11</pii>. . The exception was raised by the IDbCommand interface.
Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
Activity ID: e1e56592-3fbd-4e81-8429-2a59f69bd434
Request ID: 1d303adc-f943-4bdf-b8ad-c7ca7c15bb6d
Time: 2022-06-07 10:24:44Z
This particular dataset is a Large Dataset with Incremental Refresh. We are PowerBI Premium Per User. The SQL Database in this instance (and all instances for us) are located in Azure SQL Pools. We connect to them using OAuth2.
Looking at my analytics for this server, there were no queued or failed queries. We apparently never even maxed out usage (this server is kept at 500DW units for scaling) and there isnt anything obvious to me yet that says at the various times this morning that something should time out.
Is there a path I should troubleshoot to help avoid these? Is there another way to set this up (Maybe using Basic connection instead of OAuth2? I saw a post 2 years ago about that) that could help avoid this?
