Forum Discussion
OData issue using Power BI API
- 6 years ago
Final managed to solve this issue.
I had to delete and re-add the SPNs for the ReportServer Service account. The OData connectivity now works.
Why? Don't know but it works.
Hmm, when I use an OData data source with Windows auth and domain\user the test button (and scheduled refresh) works for me. If I remove the "domain\" prefix it does not work, but I'm assuming that the server was trying to authenticate the user as a local account instead of a domain one.
CDavies wrote:
Curiously though if I copy the OData url directly into the browser address bar, it correctly gives me the .json file to download.
When you paste the URL in the browser are you logged in as the same user which you are trying to test? Or are you running the browser under your account? To test this properly you would either need to log in as the user you are trying to save against the data source or use "runas" to run the browser as this user.
If this fails it probably means this users has no rights to the folders in the PBIRS portal and you would need to go into the manage folder options and then into the Security tab and make sure this user has at least "Browser" rights.
Yeah, it's a puzzle...
I get the same error using my domain/user login credentials in the test connection box, which is why it's confusing that the .json file downloads from the browser.
My user account is in an AD Group with Content Manager rights on the whole PBIReport Server.
May have to get the SQL team to SSIS these queries into a db rather than using the api... which would be a shame.