Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Error
Data source error: {
"error": {
"code": "DM_GWPipeline_Gateway_MashupDataAccessError",
"pbi.error": {
"code": "DM_GWPipeline_Gateway_MashupDataAccessError",
"parameters": {},
"details": [
{
"code": "DM_ErrorDetailNameCode_UnderlyingErrorCode",
"detail": { "type": 1, "value": "-2147467259" }
},
{
"code": "DM_ErrorDetailNameCode_UnderlyingErrorMessage",
"detail": { "type": 1, "value": "ODBC: ERROR [08001] SCRAM authentication requires libpq version 10 or above\n" }
},
{
"code": "DM_ErrorDetailNameCode_UnderlyingHResult",
"detail": { "type": 1, "value": "-2147467259" }
},
{
"code": "Microsoft.Data.Mashup.ErrorCode",
"detail": { "type": 1, "value": "10478" }
},
{
"code": "Microsoft.Data.Mashup.ValueError.DataSourceKind",
"detail": { "type": 1, "value": "Odbc" }
},
{
"code": "Microsoft.Data.Mashup.ValueError.DataSourcePath",
"detail": { "type": 1, "value": "dsn=DB_01" }
},
{
"code": "Microsoft.Data.Mashup.ValueError.NativeError",
"detail": { "type": 1, "value": "101" }
},
{
"code": "Microsoft.Data.Mashup.ValueError.OdbcErrors",
"detail": {
"type": 1,
"value": "#table((\"SQLState\", \"NativeError\", \"Message\"), {})"
}
},
{
"code": "Microsoft.Data.Mashup.ValueError.Reason",
"detail": { "type": 1, "value": "DataSource.Error" }
},
{
"code": "Microsoft.Data.Mashup.ValueError.SQLState",
"detail": { "type": 1, "value": "08001" }
}
],
"exceptionCulprit": 1
}
}
}
Here is the error. This issue has been occurring since around Nov ’25. My reports have been live since May ’25 with only occasional failures earlier. Over time the refresh failures have increased and are now frequent and random across eight scheduled refreshes.
Relevant Details:
So the PBI admin team is leaning toward this being a SCRAM issue, but I want to confirm whether it is actually SCRAM or if there is another underlying error that we are overlooking. Any guidance or help in identifying the real cause would be appreciated.
Hey @damit230183 ,
You’re getting this specific error from the gateway layer:
ODBC: ERROR [08001] SCRAM authentication requires libpq version 10 or above
DataSourceKind = Odbc
DSN = DB_01
This is not a generic network error. It is explicitly an authentication library version mismatch coming from the PostgreSQL client library (libpq) used by the ODBC driver on the gateway machine.
Since this only happens in Power BI Service and never in Desktop, the problem is almost certainly on the On-Premises Data Gateway cluster, not your report or the database itself.
The error means:
The ODBC driver on at least one gateway node is loading a libpq version older than v10, which does not support SCRAM-SHA-256 authentication.
Hi @abhijit_mohanty ,
I would also take a moment to thank @MohdZaid_, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hi @abhijit_mohanty ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hello @v-sshirivolu & @MohdZaid_ ,
So, the final workaround that was suggested to me - update the source to PostgreSQL connector from the ODBC.
As of now 8 refreshes have been processed and 0 fails.
Hey, thanks for the suggestion. I have asked the admin team to follow through your instructions. Will update this thread once they revert.
@abhijit_mohanty Maybe the issue is due to Postgres and not in Power BI. Please check the below post
https://stackoverflow.com/questions/62807717/how-can-i-solve-postgresql-scram-authentication-problem
Proud to be a Super User! | |
Thank you for the reply. My admin team is looking into this. Will keep you posted if this worked.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.