Showing results for 
Search instead for 
Did you mean: 

Error when refreshing dataset despite gateway status showing online, OAuth2 not working

I have 2 issues:


1) OAuth2 authetication no longer works (both Service and Desktop), coming up with the error "Unable to update this data source's credentials. Unable to connect to the data source."


2) Dataset refresh comes up with this error even when all gateway status shows "online"



Data source error: {"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The credentials provided for the VSTS source are invalid. (Source at sita-pse.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"VSTS"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind","detail":{"type":1,"value":"VSTS"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath","detail":{"type":1,"value":"sita-pse"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"sita-pse"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessForbidden"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"VSTS\",\"path\":\"sita-pse\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessForbidden"}}],"exceptionCulprit":1}}} Table: defect by sprint.
Cluster URI:
Activity ID: d702d841-7cdc-45b3-8ef2-e194561b5cf5
Request ID: 212fdc9d-4ea3-c251-e107-2b5a53966f33
Time: 2022-05-17 11:59:38Z



Status: Accepted

Hi All,


We get inform from the product group said it’s a known issue. Power BI customers using Azure DevOps Server connector may experience issues connecting from desktop and users who already have connection established and report published to service might experience credentials errors when refreshing the dataset. They are working on the fix for it. If this issue still happen in your region, please be patient for the fix. Thanks for your understanding!


Best Regards,

Community Support Team _ Caiyun

Regular Visitor

Having a similar issue, except refreshing with Azure DevOPS/VSTS works on desktop with oauth.  Only started happening Monday, 5/16 - and no changes were made to any of our 3 Azure DevOPS/VSTS environments.


In the service, getting the following error (unable to paste the entire thing as it exceeds character limit) and unable to use key or oauth, even though desktop refreshes (so I know credentials are valid):

: <!DOCTYPE html > <html> <head> <title>This operation is not supported for a relative URI.</title> <style type="text/css">html { height: 100%; } body { font-family: "-apple-system", BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Helvetica, Ubuntu, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; font-size: 14px; height: 100%; margin: 0; background-color: #fff; } .container { height: 100%; display: flex; flex-grow: 1; flex-direction: column; } .header { font-size: 14px; line-height: 20px; padding-right: 40px; display: flex; box-shadow: 0px 1px 0px rgba(0, 0, 0, 0.08); } .header > div, .header > a { margin: 14px 0px 14px 32px; text-decoration: none; color: rgba(0, 0, 0, 0.55); } .header > div:first-child { flex-grow: 1; margin-left: 14px; color: #0078d4; display: flex; } .header > div:first-child > div { margin-left: 14px; } .content-container { display: flex; flex-direction: column; justify-content: center; margin-top: 126px; } .content { display: flex; justify-content: center; align-items: center; } .error-info { display: flex; flex-direction: column; width: 500px; } .title { font-size: 28px; font-weight: bold; line-height: 40px; letter-spacing: -0.04em; color: #212121; margin-bottom: 16px; } .details { font-size: 14px; line-height: 20px; color: #212121; margin-bottom: 16px; } .details a { text-decoration: none; color: #0078d4; } .reference-data { font-size: 12px; line-height: 16px; color: rgba(0, 0, 0, 0.55); margin-bottom: 32px; } .logo { height: 500px; width: 500px; } .action-container { display: flex; } .action { background-color: #0078d4; color: #ffffff; align-items: center; border-radius: 2px; border: 1px solid transparent; cursor: pointer; display: inline-flex; flex-direction: row; flex-shrink: 0; font-family: inherit; font-size: inherit; font-weight: 600; justify-content: center; outline: none; overflow: visible; padding: 6px 12px; position: relative; transition: background 80ms linear; text-decoration: none; } .action:focus { box-shadow: 0 0 0 3px rgba(0, 120, 212, 0.35); } .action:hover { background-color: rgb(0, 103, 181) } .action:active { background-color: rgb(0, 91, 161) } .secondary-action { text-decoration: none; color: #0078d4; margin-top: 16px; } .more-info { margin: auto; display: flex; flex-direction: column; padding: 0 40px; } .more-info > div:first-child { font-size: 15px; font-weight: 700; } </style> </head> <body> <div class="container"> <div class="header"> <div> <span> <img class="header-logo" src="data&colon;image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAACXBIWXMAA

Community Support
Status changed to: Investigating

Hi @an_clla,


Please make sure the credential you are using is valid and have sufficient permissions to retrieve data from the data source. In Desktop, please go to Transform>Data source settings and Clear Permissions of your data source. After that, reconnect to the data source with your credential to check whether this credential can be used to complete the connection.



If the credential  is valid, please check the version of your Gateway and upgrade it to the latest version and restart it. After that, update your credential in Power BI service.


Best Regards,

Community Support Team _ Caiyun

Frequent Visitor



I cleared all permissions and reconnected on power BI desktop as suggested, and no error came up during that. However, when I try to refresh the report, the pop-up for authenticating for the Azure DevOps data came up, and trying to connect using OAuth2 there comes up with the error : "We couldn't authenticate with the credentials provided. Please try again.". These credentials have always worked in the past and only stopped working on the 16th May. 


I also tried upgrading the Gateway to the latest version, restarting it, but I still can't connect via OAuth2 in Power BI Service. I tried using a personal access token instead, and that connects and the datasource shows as "online", but the dataset still does not refresh.

Regular Visitor

Also followed the same directions - desktop runs with no issues connecting using OAUTH to VSTS data source, but in the PowerBI service does not work with OAUTH or a token. How can you help us get to the owner of the DevOPS/VSTS data connector? @v-cazheng-msft 


I'm also seeing this problem with the Azure DevOps data connector. Works in PowerBI Desktop, but fails to update credentials. I have the exact same error "This operation is not supported for a relative URI". I've reported this over on the Azure DevOps community to see if they can help, but wanted to post this here too since it could be something going wrong on the side of the connection. Since I am internal to MSFT I'm happy to help supply logs or whatever is needed to help diagnose this problem.



Allen Denver

Visual Studio for Mac

Regular Visitor

I'm alsoi facing the same issue where dataset doesn't refresh in Power BI service. I tried with and without gateway (latest version), but issue is still there.


Can you please have a look urgently as this's impacting our work and reports can't be used due to stale data?



New Member

Same Problem here


Seems fixed now. I think the problem was introduced in a recent change in AzDO which the team addressed last night.

New Member

Not fixed. Same issue here with relative URI error after reconnecting to the data source.

Regular Visitor

Yes I still see the issue. Can we expedite the fix please? Thanks.