Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when opening any Power BI XMLA endpoint: "The following error has occurred while updating the connection: An item with the same key has already been added" #1200

Closed
HymieHo opened this issue Nov 16, 2023 · 5 comments

Comments

@HymieHo
Copy link

HymieHo commented Nov 16, 2023

Describe the bug
Opening any powerbi:// endpoint fails with "The following error has occurred while updating the connection: An item with the same key has already been added."

To Reproduce

  1. Open DAX Studio v3.0.10
  2. Connect.Tabular Server.enter endpoint
  • Log shows: Establishing connection
  • Sign in
  • After 60s or so:
    The following error has occurred while updating the connection: An item with the same key has already been added.
    Error selecting database: one or more errors occurred.
    Error setting selected database: The connection either timed out or was lost.
    Error connecting to server: xmla endpoint 

If I repeat these steps, I still get the "same key" error and the model browser is blank, but I can write and execute queries against the model. Advanced.View metrics does not work: "Error viewing metrics: the database ' ' could not be found"

Additional context
The endpoints are in the msit environment

@github-actions github-actions bot added the triage issues that need to be classified label Nov 16, 2023
@dgosbell dgosbell added bug fix-checked-in and removed triage issues that need to be classified labels Nov 21, 2023
@dgosbell
Copy link
Contributor

Thanks for logging this. There is has been a change deployed to the semantic models in Power BI which has exposed a bug in DAX Studio. I will be releasing v3.11 soon with a fix for this.

@dgosbell
Copy link
Contributor

I've just released v3.0.11 with a fix for this issue

@fedelmfede
Copy link

Thank you, was having the same issue until I've updated DAX studio and now it is resolved.

@sunkai-cai
Copy link

Thank you

@FireFighter1017
Copy link

Just resolved my current issue by updating DAX Studio to 3.0.11 from 3.0.9
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants