Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Using Power BI - AI Insights - Text Analytics function getting error

When I data refresh in Power BI, getting the following error message - "OLE DB or ODBC error: [DataSource.Error] An error happened while reading data from the provider: 'Internal error CultureInfoNotSupported.<ccon>eo</ccon>,en, es, pt, fr, de, it, nl, nb, sv, pl, da, fi, ru, el, tr, ar, zh, ja". Not sure if any desktop setting missing at.   Notice e error it seems unique message "CultureInfoNotSupported" not much info even on bing or google searches.  Appreciate if any one can advise & guide me on it ASAP please. 

Status: Investigating

Hi @Anonymous,

 

May I know whether this issue still happen? Did this issue happen in Power BI Desktop or Power BI service?

 

Best Regards,

Community Support Team _ Caiyun

Comments
v-cazheng-msft
Community Support
Status changed to: Investigating

Hi @Anonymous,

 

May I know whether this issue still happen? Did this issue happen in Power BI Desktop or Power BI service?

 

Best Regards,

Community Support Team _ Caiyun

jose_guerrerop
New Member

I have the same problem. I am using Power BI Desktop

5ca-aj
New Member

I am experiencing the same issue since yesterday for one for my reports. Both in power bi online service and desktop. This is the error I am getting:

 

OLE DB or ODBC error: [DataSource.Error] An error happened while reading data from the provider: 'Internal error CultureInfoNotSupported.tl,pl, pt, ja, fr, es, ko, da, pt, nl, en, nb, de, ru, it, sv, fi'.

 

Do we know what is casusing this or how can I solve this? The report was running all fine for the past 1 month and suddenly I got this error since yesterday.

Cyprien_Bariant
New Member

Hi kvjkumar,

 

I experienced the same issue few days ago. I was using the detection language function as the input of the language iso code of the sentiment scoring function. 

 

When I removed the rows with "eo" (esperanto) as iso code, the error was no longer displayed. Even if only 8 rows of my dataset were detected as "eo" (and they weren't actually esperanto, but maybe the words contained where transparent), these 8 rows were the source of the error.

 

I hope it will help!