Forum Discussion

gayatrisr's avatar
gayatrisr
Regular Visitor
2 years ago
Solved

SSAS Tabular Model has been changed to AtScale model automatically

I'm unable to use Power BI reports in service. I get the error - This report couldn't access the data source. Contact the author to have it fixed. I verified the data source and found out that the mo...
Need Help
  • Greg_Deckler's avatar
    Greg_Deckler
    2 years ago

    Posting the root cause and fix here. Please refer to this Issue. The fix has been confirmed with a customer.

    SSAS Tabular Models converted to AtScale Automatic... - Microsoft Fabric Community

     

    Root Cause

    This issue was identified and fixed last year. We realized we were incorrectly classifying SSAS models as AtScale. The bug was in production for 1-2 months before being fixed and any live connected reports created during that time were being classified as AtScale. Up until AtScale integration was finished ~1-2mo ago, we were treating AtScale virtually the same as SSAS with no parameters added to the connection string - so no change in report behavior. Some of these reports could have been holding onto the AtScaleDatabaseLive connection type for the last year, and now after republishing, they're unfortunately catching the new WSID connection string parameter. This lines up with the the inability to reproduce the issue today and why new reports are working as normal, but the customer republishing existing reports causes the WSID property to appear and failure in gateway.

    Fix

    Saving the file as a .pbip (PBI Project) file, exposing the metadata for the connection and change it there (something you can't do in the PBI Desktop UI.)  Saving as a zip file, changing the Connection file there, and then resaving as PBIX just ends up as a corrupted file so that is not an available fix.

     

    Update per dato_Niall : When saving the PBIP file type, this exposes an extra folder (with the meta data @Greg_Deckler mentions) called [ReportName].Report where the PBIP file was saved. Within this folder is a file called 'definition'. This if opened in notepad is where the datasource can be edited. Once this is edited you can then save the report back to PBIX file and this fixes the issue.

jtrock's avatar
jtrock
Frequent Visitor
2 years ago

This has been happening at our organization as well.

 

Reports that were created in Power BI Desktop using a Power BI semantic model selected from a workspace have been working as expected.

 

However, we have several reports that were created in Power BI Desktop in the past where we selected Analysis Services from the Get Data menu option, and then entered our SSAS Server and Data Model name to directly connection.  Every once in a while, one of these PBIX files, regardless of how far in the past they were made or modified, when opened in Power BI Desktop today, will now show an AtScale data source.

 

There are only two people at our organization that have access to these PBIX files, I'm one of them, and neither of us even know how to specify an AtScale data source.  Furthermore, the last modified date on the PBIX file was back in March 2024.  So, I believe this is something in a recent version of Power BI Desktop that is starting to misread the connection strings in old PBIX files.

 

I tried changing the .pbix extension to a .zip, unzipping the archive, and copying over the Connection data/file from a known good PBIX to an impacted PBIX and then re-zipping and changing the extension back to PBIX, but I no longer have any luck with this process like I did years back when trying to change out a data source fron Analysis Services to a workspace semantic model without having to rebuild the report in the past.

 

The only fix appears to be rebuilding the report.  Has there been any update to this issue?