Error: "No eligible workspace found from PowerBI Service." on Desktop

[TimoRiikonen]

Hello,

We have made a Fabric Direct Lake report to one of our customers and it was working fine at least on May 27.

Now today is not working in Desktop anymore, so I am not able to modify the report.

It is still working in the service and the version is the same (checked with GIT).

1) File --> Sign out

2) File --> Sign in using timo.riikonen@innofactor.com

    Accept MFA authentication

3) File --> Open report

Result:

4) File --> Sign out

5) File --> Sign in using ext-timo.riikonen@customer.onmicrosoft.com 

    Accept MFA authentication

6) File --> Open report

Same result.

Report is in PBIP format.

I didn't find anything useful (or secret) in the details. Should I include the content?

When I go with chrome to the workspace it works fine with ext-timo.riikonen@customer.onmicrosoft.com id.

timo.riikonen@innofactor.com has also admin permissions to the workspace, but I can only see what workspaces it should have access to. Their content is always empty:

Results in Chrome may have been the same a month ago.

I am not aware that anyone would have made any changes during this month.

[TimoRiikonen]

Update:
Still getting these issues every now and then, but now I am able to fix the issue with ext account on the customer.
GDAP account doesn't work still (= my own account).

[TimoRiikonen]

Same problem, but new error

Error: Expected 'artifacts' array containing 'report' artifact with valid 'path' property.

[Lieuwe123]

I have the same error today. 

In my case:

- I have report (pbix) connected to direct lake semantic model

- published to workspace, working all fine. The semantic model is in the same workspace. I have admin rights on the workspace.

I want to start using GIT with a local repository/clone, so I:

- created a local clone

- open definition.pbir in power bi desktop and get the error "No eligible workspace found from PowerBI Service."

[TimoRiikonen]

@Lieuwe123 ,

I never figured out the reason for this.

Luckily I had another oler copy of the report in test system.

I started to use it and so far I haven't got this error again.

[SaiTejaTalasila]

Hi @TimoRiikonen ,

Please check on your workspace whether you have filtered the workspace items(dataflow etc,..).If that is not the reason in that case the issue with deployment or those workspace items are deleted .

Thanks,

Sai Teja 

Thanks,

Sai Teja 

[TimoRiikonen]

This is not the case.

I was able to get over this error by taking an old version from testing and restarting with that.

But now I got the error again.

This time development had a functional version in dev service and I downloaded that. When I open it I got error 

Let's write it down here, so someone can google for it: "Details: Looks like we're unable to access the dataset. Please contact the owner of the dataset."

I have admin access to the workspace and to the dataset. 

When I press Edit, I get dataset list of our company and not the company the report was made to. So problem has to do something with that the Desktop is trying to connect using wrong user id. On both cases the account is same, my Innofactor email id. But it should use GDAP when connecting and it is not using it.

I can't fix this afterwards as the data source is gone after the failure:

I tried next:

1) Close Power BI (and all reports)

2) File > Sign out

3) File > Sign in

4) GDAP sign in with same email address

5) Open original dev version of the report. No error, nothing happens, so opening fails. This file is in pbip format.

6) Open the report I downloaded from DEV service. This one works. This file is in pbix format.

7) I save the pbix file.

😎I immediately and without doing anything else open the PBIX file. This time I get again "Please contact the owner of the dataset", so the format is not a solution.

9) We had some issues with GDAP accounts earlier, so luckily I have also external accounts to the customer. Let's restart Desktop and use that account. Result from PBIB version: failed.

10) Result from PBIX version. Success.

11) Close the report (and Desktop) and reopen it. Success.

12) Saved the file as pbib version, closed and reopened it. Success.

13) Closed Desktop and opened it again. Still success.

I can't think of any other reason than a defect in Desktop. 

Here is my Desktop version (= August 2024):