Power BI Gateway Refresh Failure - Unable to connect to the data source undefined

[Anonymous]

I am getting the error "Unable to connect to the data source undefined" when my Power BI dahboard is trying to refresh using the Gateway. I am connecting to only 1 data source and the data is also not much. All of a sudden facing this issue and tried all sorts of changes and nothing is working.

I can see that there are solutions that was provided in 2019 and since there were lot of upgrades i dont know if the same thing works or not. I hope that microsoft can take notice of this request and help and if anyone else faced this issue recently and tell us ho exactly they resolved this issue.

Also i am getting the below error from the Gateway logs:

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_MashupDataAccessError
GatewayVersion=
Reason= --->
[1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: MashupValueException:<pi>Microsoft.Data.Mashup.MashupValueException (0x80004005): Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The received certificate has expired.)

I dont know whether this error is relevent or not as we checked and the credential is able to work in the Gateway server.

Earlier issues & solutions:

PowerBI intermittent Refresh Failure - Unable to c... - Microsoft Power BI Community

'Unable to connect to data source undefined' - Microsoft Power BI Community

[v-angzheng-msft]

Thanks for sharing😀

[amitchandak]

@Anonymous , if your data source is one that needs SSL certificate then this is the error

The received certificate has expired.

refer if these settings are needed -https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-2017

[Anonymous · Accepted solution]

Issue was due to the Certificate being Expired in the Server for the Database we were connecting to.

Once the Certificate was updated the issue got resolved.