The recent 2021.1.91 update to ArcGIS for Power BI caused a login issue for me. The visual would prompt to "login below", but there was no login form to fill. I authenticate to my Enterprise server. I saw this post regarding CORS settings, ArcGIS for Power BI Maps not loading - Esri Community. I didn't have CORS settings on my Enterprise server, but I tried adding the recommended entries. That didn't change the behavior. I removed them and the ArcGIS for Power BI visual began presenting the login form and authenticating properly.
Thank you for sharing that with us and we will explore this when we do some additional testing in the future. The CORS policy would allow or block access, so toggling it is a bit of a mystery and makes me wonder if something was cached somewhere along the line.
If you run into any issues, please reach back out and post so we can help!
Interesting @MarkWestergaard
So toggling the CORS policy fixed the issue?
Andrew
I believe so. I had tried a couple of things prior to that (saving-closing-restarting, creating a new map visual), but toggling the CORS policy seemed to clear things up. I haven't experienced the issue since.
I was thinking the same, or perhaps a coincidence. Thanks.
I am experiencing the issue again. I can no longer initiate a new connection from the ArcGIS Maps for Power BI visual to my ArcGIS Enterprise. The CORS Policy doesn't seem to be the culprit. Existing Enterprise connections seem to be behaving and I can connect to ArcGIS Online on new reports. The only recent change of which I am aware is I updated my Power BI desktop to the recent October release (2.98.882.0). I will compare to a coworker with an older release or I will try dropping back to an earlier release.
Can you help me figure out how to toggle the CORS policy? I have been having this same problem on Power BI even after I downloaded the new version yesterday
I followed the instructions in this link from the original post:
https://community.esri.com/t5/arcgis-for-power-bi-questions/arcgis-for-power-bi-maps-not-loading/m-p/1098402#M775
I'm less inclined to think it was the solution now that I'm seeing the problem again and it hasn't helped this time around.
I'm still experiencing the issue after updating to recent Power BI 2.98.1004.0 release. I have not had a chance to drop back to a prior release, but I have tried a number of combinations in an attempt to eliminate other factors (other visuals, removing themes, etc.). This is by no means a definitive result, but I am seeing this pattern in my tests:
I've been able to repeat this at least three times. Of course, the behavior could simply be specific to my desktop or configuration. One thing I forgot to mention is I am using Power BI with a "Premium per User" license, in case that is a factor.
I started to wonder if this might be related to cache or cookies. I found this post and followed the steps:
ArcGIS Power BI Issues from latest release - Esri Community
It seems to have helped. I was able to open an existing report, add the ArcGIS Maps visual, and connect with my Enterprise server.
Hi all,
I have exactly the same issue as above. But toggling the cors policy didn't fix it. We use an enterprise portal with IWA, and we don't have any value in the Allow Origins, i.e. we don't block any url.
Are there any updates on this?
Thanks!
Take a look at this thread regarding clearing of cache and possible double installation of Power BI:
Power-Bi can't sign in to ArcGIS Online - Esri Community
Thanks for the reply!
I will definetely update my desktop PowerBI to the latest version but my issue is still occuring for the powerBI web application. I tried to connect to our ArcGIS Enterprise (IWA activated), not connecting via the webadaptor thus bypassing the SSO and... it works. So the CORS issue in the powerbi web app is somehow related with the IWA configuration. I remember that with older versions, this was not a problem.
I am going to check with the latest version of PowerBI desktop.
IWA may work with the Power BI service at app.powerbi.com but it is not supported in Power BI desktop. We have an enhancement request in with Microsoft to support this, and hope they will look at this later next year.
@MarkWestergaard There was a PowerBI bug that was preventing all custom visuals from logging in. We were impacted by that and an update was pushed on the 7th or so to resolve this. Our visual was also updated on the 8th with many quality improvements.
Please let us know if you continue to experience issues.
@MichailMarinakis1 IWA will not work with Power BI desktop. This is an enhancement request we have made to Microsoft on behalf of our users and we hope they will have a resolution for it this year. IWA 'may' work if you use the Power BI service, since it changes the browser component used to authenticate with Enterprise.
If IWA is required, a potential workaround... that might not be awesome, is to use Power BI Desktop to build the report with everything BUT the map. Upload to the Power BI service, then edit the report in the browser, add the map visual, then authenticate with your Enterprise.
@Anonymous User Hi Andrew, We're struggling with the same CORS issue on our browsers.We want to use IWA with the Power BI service, but get the mentioned "blocked by CORS policy" error.
Can you tell us how you configured your portal webadaptor on IIS? Did you use the "IIS CORS module" (https://www.iis.net/downloads/microsoft/iis-cors-module)
I am having the same issue I believe. Same issue across PowerBI in Chrome, Edge and the desktop app. Using the Portal URL, then selecting builtin account works fine, but using Enterprise login (AWS SSO) has a window open up but hangs. In DevTools I can see an invalid token error.
What do you mean to 'Toggling CORS' exactly? How do I try this out?
Hi LHo, Andrew,
We're struggling with the same CORS issue on our browsers. We want to use IWA with the Power BI service, but get the mentioned "blocked by CORS policy" error. (see also our previous post)
We're using IIS IWA with the ArcGIS portal webadaptor.
We're eager to the get this issue fixed, as it is the last obtacle to roll out the ArcGIS for Power BI addon in our organisation.
Should be great to share any progress on this IWA problem.
Benny
Someone reported that changing the CORS setting on their web server fixed the issue. Its unclear why, but it worked for a few users. Do you see a CORS error in DevTools? I would recommend starting a new thread on this one.
@BennyMeyns Did you follow the instructions here?
https://doc.arcgis.com/en/power-bi/get-started/enable-cors.htm
When you say changing the CORS setting, would an example of this be removing all URLs from Allow Origins and re adding them in etc?
I see a token error in DevTools. In portal.sso.ap-southeast-2.amazonaws.com/token/whoAmI response (Fiddler) I see
The URLs have been added in Portal Allow Origins section as per https://doc.arcgis.com/en/power-bi/get-started/enable-cors.htm
Hi @Anonymous User , we double checked this. Our config has been set up as defined in the instructions https://doc.arcgis.com/en/power-bi/get-started/enable-cors.htm
Do you have any hint how we could investigate this further?
Hi @Anonymous User , we did some in-depth analysis on the IWA behaviour of the ArcGIS for Power BI plugin.
Our conclusion: fixing 5 lines of code in the init.js file on js.arcgis.com should fix the problem (https://js.arcgis.com/4.20/init.js).
I'm attaching some small report together with the fixed init.js file.Could this please be picked-up by the ESRI development team, as it really needs only a minor fix.
Of course we are availble to give you further explanation of the detected problem (by e-mail, video call, etc..)
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
