Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
hi .. this is my first post and i didnt see any issue simliar to mine.. so here it goes
I was hoping i could get some help with an issue we having which may have started after a PBI client upgrade.
Current version is the May 2022 PBI Client. We use STS for client auth and PBI uses Windows Auth. Sharepoint is 2019 Nov CU (16.0.10392.20000).
We have reports written in an (ccoincidentally?) older version of PBI client and those older reports all (via the IIS logs) hit SharePoint via the /_vti_bin/client.svc (oData) (everyone one of them return a 200) but seemingly since the upgrade any new or edited reports then start pointing to /sitename/listname/_api/web/Lists(guid'000') (REST). Those using the rest end points all fail with a 401. in doing so it generates a lot of IIS logging with no headers at all. Just the returned "401 text/plain;+charset=uft-8".
If someone could please give me a pointer, gotchas, hint, or things to check or any possible culprit, or even any indication of know differences in PBI in the end point usage between versions. I'd greatly appreciate it.
i am not sure what other info you may need. Ill try to answer any and all questions. and thank you.
Solved! Go to Solution.
@TerryRemsik ,refer if one of these can help
https://auth0.com/blog/forbidden-unauthorized-http-status-codes/
HI @TerryRemsik,
It seems like you are working with old version power bi desktop, it may have some difference with the last version. What type of power bi desktop are you used? The common power bi desktop or report server optimized version? Can you please share some more detail information about these?
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
@TerryRemsik ,refer if one of these can help
https://auth0.com/blog/forbidden-unauthorized-http-status-codes/
User | Count |
---|---|
94 | |
86 | |
78 | |
70 | |
63 |
User | Count |
---|---|
114 | |
101 | |
97 | |
66 | |
59 |