Power BI API Errors

Van Tam Ho · August 15

Hi All,

Has anyone or does anyone seem to have the same error issue when connecting to Blackbauds API for power bi, this only happens when the refresh is setup for overnight runs?

{“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”:"<ccon>The credentials provided for the Blackbaud source are invalid. (Source at Blackbaud.)</ccon>"}},{“code”:“DM_ErrorDetailNameCode_UnderlyingHResult”,“detail”:{“type”:1,“value”:"-2147467259"}},{“code”:“Microsoft.Data.Mashup.CredentialError.DataSourceKind”,“detail”:{“type”:1,“value”:“Blackbaud”}},{“code”:“Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind”,“detail”:{“type”:1,“value”:“Blackbaud”}},{“code”:“Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath”,“detail”:{“type”:1,“value”:"<ccon>Blackbaud</ccon>"}},{“code”:“Microsoft.Data.Mashup.CredentialError.DataSourcePath”,“detail”:{“type”:1,“value”:"<ccon>Blackbaud</ccon>"}},{“code”:“Microsoft.Data.Mashup.CredentialError.Reason”,“detail”:{“type”:1,“value”:“AccessUnauthorized”}},{“code”:“Microsoft.Data.Mashup.MashupSecurityException.DataSources”,“detail”:{“type”:1,“value”:"<ccon>[{"kind":"Blackbaud","path":"Blackbaud"}]</ccon>"}},{“code”:“Microsoft.Data.Mashup.MashupSecurityException.Reason”,“detail”:{“type”:1,“value”:“AccessUnauthorized”}}],“exceptionCulprit”:1}}} Table: Appeal packages - Unique.

TIA

Alex Wong · August 15

Looks like you are using the unofficial Blackbaud custom connector. When you say "refresh setup for overnight run". Do you mean you are refreshing on Power BI service through the Gateway you setup?

Assuming you are not creating power bi report on the Gateway machine, it looks like the Gatway machine's connector may not have been setup exactly the same as your local computer's power bi .mez file. May want to check that.

Van Tam Ho · August 20

Thanks for coming back to me.

Yes I do mean I am refreshing on Power BI service through the gateway.

I have copied the powerbi.mez file exactly from my local machine to the gateway machine setup and everything in the file is exactly the same. The setup originally was correct and it was all working for over 2 years then when we moved the gateway to a newer machine, it has since messed everything up and the error above happens.

Van Tam Ho · August 20

There is no official Blackbaud custom connector for power BI, there is only one unofficial custom connector unless I am mistaken as the connector I have got and setup was working for over 2 years with no problems

Alex Wong · August 20

"moved the gateway to a newer machine" then is the culprit. Try the following:

login to the gateway's machine and run a refresh directly there
on your local machine, run a refresh to make sure it is working, and then if it is, re-copy the same mez file from your local machine to the newer machine
lastly if still not working, redo the mez file.

Van Tam Ho · August 21

So on my local machine I have refreshed and re-published the reports and everything goes through fine so I know its not on my local machine.

I have re-copied the .mez file back onto the machine in exactly the correct place and can see that the gateway recognises the connector

Im out of ideas of what the credentials error can be from this point as in the power bi service in the gateway options, it is all connected up, everything is online for it to work, but for some reason it is always failing the refresh overnight.

Gateway.png

Van Tam Ho · August 21

so the error has now changed I now get the following 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":"[ccon]Web.Contents failed to get contents from 'https://api.sky.blackbaud.com/gift/v1/gifts?limit=5000&offset=525000' (500): Internal Server Error[/ccon]"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10117"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.Url","detail":{"type":1,"value":"https://api.sky.blackbaud.com/gift/v1/gifts?limit=5000&offset=525000"}}],"exceptionCulprit":1}}} Table: Gift (Blackbaud Model).

This is only I after I re-sign into the credentials of PBI service.

With this error I have checked all of the permission sets of both desktop and PBI service, they are all the same, I have checked the data load to ensure thats set correctly.

Alex Wong · August 21

Good step forward, as least it's not complaining about your credential.

The error "failed to get contents from 'https://api.sky.blackbaud.com/gift/v1/gifts?limit=5000&offset=525000' (500): Internal Server Error"

Means it's a Blackbaud server error. Try to do the refresh on the power bi gateway machine again later and see if the issue resolves.

Van Tam Ho · August 22

no it is still persistant.

One of my reports now goes through and we now know why the credential error happens, its due to Power BI gateway not being able to handle Blackbaud refresh tokens.

It requires manual refresh after 24 hours for the connection to to be reconnected before it can do the schedule refresh which defies the whole point of having schedule refresh in this instance.

Van Tam Ho · August 26

https://community.blackbaud.com/discussion/comment/306036#Comment_306036

The error im now having is the one you responded too (in the quote) and it just will not refresh.

Van Tam Ho · August 26

Now even refreshing in power bi desktop is pinging up the same error

Alex Wong · August 26

https://community.blackbaud.com/discussion/comment/306067#Comment_306067

can you provide detail on how you determine Blackbaud cannot handle refresh token?

There are many who uses Power BI unofficial custom connector through Gateway for refresh and I haven't heard others having a refresh issue, so I'm going to assume it is only your instance right now. (while I have utilized the power bi connector in this way, I personally do not use this method in production, so I only goes by what has been said in Power BI User Group and here in the Community).

To know for sure if it is the "setup" issue, I suggest you create a new Power BI dashboard that ONLY brings in little data (i.e. Campaign table or Fund table), in the dashboard, you can just show a table of campaign/fund. Save and publish. Then try to do the refresh. Part of debugging is to reduce the number of variables that can cause error and boil down to the actual issue you have.

Van Tam Ho · August 27

Thanks for the response, I will try and do a mini dashboard to check if it its a setup issue and go table by table to check.

I will come back to you on the "cannot handle refresh token" question.

Van Tam Ho · August 28

https://community.blackbaud.com/discussion/comment/306159#Comment_306159

I have now a run table setup to see if the refresh runs through and it doesnt, it fails the overnight refresh with the same errors as before:

Diagnosis File has failed to refresh.Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

{"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":"<ccon>The credentials provided for the Blackbaud source are invalid. (Source at Blackbaud.)</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath","detail":{"type":1,"value":"<ccon>Blackbaud</ccon>"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"<ccon>Blackbaud</ccon>"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"<ccon>[{\"kind\":\"Blackbaud\",\"path\":\"Blackbaud\"}]</ccon>"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}} Table: Appeal.

Next refresh for Diagnosis File is scheduled for August 29, 2025 1:30 UTC.

Van Tam Ho · September 1

I take it that this is not just an issue that I am facing when currently using the API?

Alex Wong · September 3

This error is back to "credentials provided for the Blackbaud source are invalid".

Looks like you are trying to get the Appeal table and is getting AccessUnauthroized.

Did you try to refresh on your own local computer that has the same Blackbaud.mez file?

If successful, did you try to refresh on the Gateway computer (manually by clicking on the Refresh button in Power BI Desktop, OPEN on the Gateway computer)?

Van Tam Ho · September 17

Yes, it goes through fine when on m local computer and running it in powerbi desktop, as soon as it goes onto the power bi service it then just thows out the credential error or the error 500.

Our IT team have looked into it and have found that this issue relates to a token issue, but its not on our side, our side connects everything up fine and the connection always shows as "online", the gateway finds the API connector fine and is shown.

I dont know what else is the problem and am now having to resort to using csv files which defies the whole point of having the api connector.

Van Tam Ho · September 17

If I go onto our power BI machine and try and refresh it through the power bi service it fails every time.

Alex Wong · September 17

IT department's diagnosis is not correct, it is not on Blackbaud side, it is on your end.

If you can refresh on Power BI Desktop on your local machine, but you cannot refresh on Power IB Desktop on the gateway machine, then the gateway machine is faulty, not Power BI Service. With this setup, what Power BI Service really is doing is essentially auto-run a refresh on Power BI Desktop on your Gateway machine. If your Gateway machine Power BI Desktop cannot refresh, your Power BI Service will fail b/c of that.

Delete the Blackbaud.mez file from your Gateway machine's folder location, and copy the Blackbaud.mez file from your local computer that CAN refresh to the Gateway machine. Then run a refresh from Gateway machine and see if it works or error out, if error, post the error given when manually refresh from Gateway machine's Power BI Desktop

Van Tam Ho · September 18

I still get the same error even when I have removed the blackbaud.mez file from our gateway machine and replaced it with the one on my local machine

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 Blackbaud source are invalid. (Source at Blackbaud.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"Blackbaud"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{"kind":"Blackbaud","path":"Blackbaud"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}} Table: Appeal.
Cluster URI: WABI-UK-SOUTH-redirect.analysis.windows.net
Activity ID: 8f623846-77b6-486f-8b1a-fafad8aab290
Request ID: 99339380-b800-4284-a9b6-37a8e050fa2c
Time: 2025-09-18 06:28:07Z

Once it published it went through the refresh stage in the power bi service and that is the error that came up.

Van Tam Ho · September 18

I have seen this through a google search which talks about power bi gateway issues and blackbaud refresh tokens, which looks similar to an issue we have even though all of our connections are correctly setup.

"The issue you're encountering, where the Power BI gateway seems unable to handle Blackbaud refresh tokens, suggests a need to re-authenticate your Blackbaud data source within the Power BI Service. While the gateway itself doesn't store or manage tokens, the OAuth2 authentication method used by cloud sources like Blackbaud can have token expiration issues, leading to failed refreshes. To fix this, go to your dataset's settings in the Power BI Service, select Edit Credentials for the Blackbaud data source, and sign in again to refresh the token. Here's a step-by-step solution:

Access Power BI Service: Navigate to the Power BI Service at app.powerbi.com.
Go to Dataset Settings: Locate the dataset that is failing to refresh.
Edit Data Source Credentials:
- Go to the dataset's Settings.
- Under the Data Source Credentials section, find the Blackbaud data source.
- Select Edit credentials.
Re-authenticate:
- You will be prompted to sign in to Blackbaud again.
- Ensure you are using the correct authentication method, which is typically OAuth2 for cloud sources like Blackbaud.
Save and Test:
- Save your changes and re-attempt the data refresh to see if the issue is resolved. "

Van Tam Ho · September 18

I didnt realise until I did a quick google search that someone else had the exact same issue that I am experiencing and it doesnt seem like there is a resolution on that one either, so there does seem to be abit of an issue here.

https://community.blackbaud.com/discussion/73098/power-bi-connector-not-refreshing

Alex Wong · September 18

From your reply. I still do not see you attempted what I ask you to.

run a refresh from Gateway machine and see if it works or error out, if error, post the error given when manually refresh from Gateway machine's Power BI Desktop

Unless I miss read your replies, please login to your gateway machine, open Power BI Desktop and open the report file

and click refresh from Power BI Desktop. Do nothing with Power BI Service.

Van Tam Ho · September 19

I have done that and I posted the error above. I mentioned that it still gives me the same error

Please see initial response from your response (above)

I changed the blackbaud.mez file as you requested, no such luck, I opened up the PBI report on the gateway machine and did both a schedule refresh and a manual refresh on that machine and no luck, same credential error.

I posted the error above.

Thanks

Power BI API Errors

Answers

Categories