Forum Discussion

Peter_23's avatar
Peter_23
Advocate V
1 year ago
Solved

Live connection error

Hi community, I have a issue with a SM in the service and reports.

 

The SM (master) have two reports (slave) e.g live connection to master. The user rename the SM in the service, and now the reports downloads  from service when I open in the desktop, it shows a message as it:  We couldn't connect to your Analysis Services database. Double-check that your server and database names are correct, and that you have permission to access them.

 

Any idea, whats happening?

 

Tip, If you return the original name (SM), It's works fine .

 

thanks in advance.

 

Tips and Tricks
Tutorial Requests
  • jaineshp's avatar
    jaineshp
    1 year ago

    Hey Peter_23,

    Yeah, I've run into this exact same headache before. Super frustrating when you rename something and everything breaks, right?

    So basically what's happening is your reports are still looking for the old SM name. Even though you renamed it in the service, the reports themselves still have the old connection info baked in.


    |Quick fix:

    • Download those reports to Desktop
    • Open them up and go to Transform Data > Data Source Settings
    • You'll see it's still pointing to the old name - just update it to the new SM name
    • Save and republish

    Or if you don't want to mess with Desktop, sometimes you can fix it right in the service by going to the report settings and updating the dataset connection there.

    Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

    Best regards,
    Jainesh Poojara / Power BI Developer

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi Peter_23,

    Thanks for reaching out to the Microsoft fabric community forum. Also it's a common scenario when renaming semantic models in Power BI Service. The problem happens because when a report uses a live connection to a semantic model, the connection string is stored with the original name of the model. So when the SM is renamed in the service, any reports pointing to the old name won’t automatically update especially when they're in a different workspace from the model. As TomMartens and jaineshp both responded to your query, kindly go through their responses and check if your issue can be resolved.

     

    I would also take a moment to thank TomMartens and jaineshp , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

     

    If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

    Best Regards,
    Hammad.

    • jaineshp's avatar
      jaineshp
      Memorable Member
      1 year ago

      Hey Anonymous,

      Thank you so much for the kind words! I'm glad I could help and really enjoy being part of this community.

  • jaineshp's avatar
    jaineshp
    Memorable Member
    1 year ago

    Hey Peter_23,

    Yeah, I've run into this exact same headache before. Super frustrating when you rename something and everything breaks, right?

    So basically what's happening is your reports are still looking for the old SM name. Even though you renamed it in the service, the reports themselves still have the old connection info baked in.


    |Quick fix:

    • Download those reports to Desktop
    • Open them up and go to Transform Data > Data Source Settings
    • You'll see it's still pointing to the old name - just update it to the new SM name
    • Save and republish

    Or if you don't want to mess with Desktop, sometimes you can fix it right in the service by going to the report settings and updating the dataset connection there.

    Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

    Best regards,
    Jainesh Poojara / Power BI Developer

  • TomMartens's avatar
    TomMartens
    Super User
    1 year ago

    Hey Peter_23 ,

     

    This suggests that the master and slave reports are not part of the same workspace; essentially, this is a good idea.
    This is because when both items are in the same workspace, the lineage of the slave report is redirected to the new semantic model.

    However, you can change the datasource after downloading the slave report.
    Navigate to and select the renamed semantic model: Transform data -> Data source settings

    Hopefully, this helps to tackle your challenge.

    Regards,
    Tom