Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Import SSAS Tabular Database: Unexpected Exception

I have a SSAS Tabular database on premise.  I try to Import this database into PowerBI Desktop, however, whenever I select one of the tables in this database I get Unexpected Exception occurred as an error message.  In this database there are several dimension tables and one fact table.  The error comes up whenever the fact table is selected.  Note that If I try to do the same thing but using  Live Connection mode it works fine.

 

The fact table is of course much larger in size than the other tables but from this error message there's nothing indicative of a size problem.  I have included a screenshot below.

 

11 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Anonymous,

    What is version of your SSAS and what is the edition of the SQL Server instance?  Do you get same error when you connect to different SSAS databases?

    Regards,
    Lydia

    • Anonymous's avatar
      Anonymous
      Not applicable

      SSAS: 13.0.1601.5 (64 bit)

       

      SQL Server: Microsoft SQL Server 2016 (RTM-GDR) (KB3179258) - 13.0.1711.0 (X64)   Jul 29 2016 16:16:44   Copyright (c) Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor) 

       

      I created another database under the same ssas instance.  This database contains the same Tabular model I was trying to Import before without success.  However in this case I shrunk the fact table size to only 1K rows (whereas the original had 3.6M).  When I do 'Get Data' and 'Import' through Power BI Desktop it works fine.

      • Anonymous's avatar
        Anonymous
        Not applicable

        Anonymous,

        Based on your test, the issue is related to the size of your fact table size.

        I note that your SQL Server is RTM version, I would recommend you install SQL Server 2016 SP1 and latest CU for SP1, then check if the issue still occurs.

        Regards,
        Lydia