Forum Discussion
[ADGraphGroupOperationFailed] Error while embedding a report
The error is coming from a page that just embeds a report. I saw one item that talked about the error from creating groups or something? We're not doing that. This is a single page embedding a report.
If anything can someone shed light on what [ADGraphGroupOperationFailed] means, we don't even know what to start to look into and are right now just grasping at straws.
Error
Status: InternalServerError (500)
Response: {"error":{"code":"ADGraphGroupOperationFailed","pbi.error":{"code":"ADGraphGroupOperationFailed","parameters":{},"details":[]}}}
RequestId: 67f1563e-e63d-49bc-9c93-ff63b462448a14 Replies
Ok. Got some new info, and this is something that has happened before.
Our PBI designer logged into PBI to pull the reports to check them, and they came up. After that the issue resolved itself within our embedded app.
This actually was happening before, only as soon as we saw the issue.. Our designer would immediately log into PBI desktop, pull the reports to see if there's some issue with the reports. Nope, but then the error would go away immedately.
Today our PBI designer was off-site at a client and wasn't around to hear about the problem. Which persisted for several hours... Until they logged into PBI desktop to 'check the reports again'.
Boom, problem resolved itself.
Wow, this sounds strange. I hope this isn't something that continues to happen.
When you say "pull the report with Power BI Desktop", do you mean that your designer re-published the PBIX file back to the workspace using Power BI Desktop? The reason I ask is that Power BI Desktop cannot directly open a Power BI report inside the Power BI Service. You can only open a PBIX copy of the report in Power BI Desktop and then publish that PBIX on top of the current version of the same report in the Power BI Service inside target app workspace.
Was your experience that as soon as you republished the reports using Power BI Desktop, they begun to work correclty again in a Power BI embedding scenario? Is it possible your PBI designer did extra steps to fix the problem such as reset dataset parameters or datasource credentials?
Just to reiterate our issue:
Our built web application, which embeds pbi reports, will come up to some point (unknown) where we start getting a 500 error [ADGraphGroupOperationFailed]. This issue persists until our PBI Designer logs into their PBI desktop to view a report. (unknown if any user, or it being that user to view a report specifically causes the fix).
Have some more info. The ISV asp.net web application that embeds reports uses a different pbi master account. We setup a service account that is only used for the communication between the ISV web app and the pbi api.
When our designer pulls up a report (to fix the issue), he is using his named account, not the ISV pbi master account.
Ok... this is getting stranger.
So we have had the issue come up a several more times since. The last time I tried using my own account to "pull reports in PBI Desktop" using the method our PBI developer was doing to no avail. It didn't work.
But as soon as he opened up his PBI Desktop and ran a report, it fixed our issue yet again.
We put in a check to pull the usage from the API: We're getting (15) return. So 85% open tokens while this occurred.
Any solutions found? We are facing similar error while installing on premise data gateway for logic apps. Not sure why or how it is related. Any pointers will really help. Thanks
I've not heard a single word from anyone official about it. Digging in further, ADGraph is the schema to Microsoft's implementation of OAuth2 for their AzureAD. So we're assuming at this point that it's some kind of permissions issue. Digging back into the documentation, they say that this master account needs to be an AzureAD Global Admin in the tenet (which is just stupid, I'm sorry, that's a pathetic requirement in today's security landscape). But since we've set it to Global Admin, the error hasn't come back.
We've sent off dozens of emails, and I've left multiple posts on here regarding the global admin non-sense.
Absolutely ZERO response.
We have the global admin privilege, though we are using Azure Gov cloud and may be hitting this issue because of some part being on Azure commercial and some on Gov cloud.
Thanks for the response!
