Forum Discussion

morbu's avatar
morbu
Icon for Helper I rankHelper I
8 years ago
Solved

Culture is not supported error message

Hi,

 

I've been working on a PBI Solution that's worked for quite some time. It consiste of Google Analytics data and many Excel files stored on OneDrive for the respective App Workspace.

 

I get the following error message

 

I've followed a few of the tips in previous treads with similar issues but don't seem to get anywhere.

I've tried the following troubleshooting:

- made sure that all data columns have the relevant data type
- made sure that there are no errors in Power BI Desktop when refreshing
- republished the solution with a new dataset name

- changed regional settings to English(UK) in Power BI Desktop

Anybody experienced this and can advice?

  • morbu's avatar
    morbu
    8 years ago

    Sorry for late response.

     

    The problematic step was not specifically in the Dim_AssetTypes table. The table name always changed when I tried a new scheduled refresh in PBI Service, always with the similar "Culture is not supported..." error message

     

    We ended up going back to one of the previous PBIX versions in the end (stored the PBIX on OneDrive so we have file-versioning) and redevelop some of the work, instead of using time on troubleshooting this.

2 Replies

  • v-ljerr-msft's avatar
    v-ljerr-msft
    Icon for Microsoft Employee rankMicrosoft Employee

    Hi morbu,

     

    Here is a similar thread which mentions that some problematic steps in your query could also cause this issue. From the error message provided above, the problematic step should in your Dim_AssetTypes table/query. So could you go to check the steps there, or try removing and recreating the table/query in Query Editor to see if it works?

     

    In addition, if the issue persists, I would suggest you create a support ticket on Power BI Support page for better assistance. :smileyhappy:

     

    Regards

    • morbu's avatar
      morbu
      Icon for Helper I rankHelper I

      Sorry for late response.

       

      The problematic step was not specifically in the Dim_AssetTypes table. The table name always changed when I tried a new scheduled refresh in PBI Service, always with the similar "Culture is not supported..." error message

       

      We ended up going back to one of the previous PBIX versions in the end (stored the PBIX on OneDrive so we have file-versioning) and redevelop some of the work, instead of using time on troubleshooting this.