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

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
rborges
New Member

Specified culture is not supported error

I had a datasource that worked just fine. After a while I noticed that my scheduled refreshes started failing.

 

The datasource and visualization building is made on desktop, and uploaded to app.powerbi.com .. but on the desktop the refresh works just fine.

 

However, it keeps failing on the webapp (which destroys my realtime dashboards) due to some "Specified culture" not being supported..

 

12321.PNG

 

To simplify searching, I'll include the error in text.

Error on the DatasourceThe specified culture is not supported.
URI de ClusterWABI-NORTH-EUROPE-redirect.analysis.windows.net
ID de Atividade95d16016-344c-17f0-8fbc-12cc9bb33050
ID do Pedido3dc10eea-cc3a-b543-e9d0-bbc516a81881
 
Have any of you encountered this before? I've tried everything I can.. have latest version of all power BI software and gateway, no errors on the tables, no problems on the dataformats.. but i can't get past this.
Need helps 🙂
1 ACCEPTED SOLUTION

I've also reported the issue to PowerBI dev team via Frown .

 

I spent quite some hours but narrowed down to a solution that I now share with you:

 

#"Sorted Rows" = Table.Sort(#"Capitalized Each Word",{{"Column1.DATA_EMISSAO", Order.Ascending}})

 

This was my problem.

 

I had parsed the Date I was using and afterwards was sorting the table using it... for some reason, PowerBI did it right and threw no exception, but on the webapp it stopped the refresh.

 

After removing this from every table of the dataset, it worked flawlessly once again.

 

I have contacted PBI team and can hand them a sample with the problem, so they can see it for themselves that it works after removing this specific step.

 

Thank you for your help anyways.

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

I followed steps wise process and after removing the code to convert epoch time to date and time it worked with refresh.

I have removed this line of code

= Table.AddColumn(#"Filtered Rows1", "DateandTime", each #datetime(1970,1,1,0,0,0)+#duration(0,0,0,[timestamp]/1000))

 

pedramr
Employee
Employee

I am opening a bug on this at our end. In the meantime, I suggest that you contact our official support team.

I've also reported the issue to PowerBI dev team via Frown .

 

I spent quite some hours but narrowed down to a solution that I now share with you:

 

#"Sorted Rows" = Table.Sort(#"Capitalized Each Word",{{"Column1.DATA_EMISSAO", Order.Ascending}})

 

This was my problem.

 

I had parsed the Date I was using and afterwards was sorting the table using it... for some reason, PowerBI did it right and threw no exception, but on the webapp it stopped the refresh.

 

After removing this from every table of the dataset, it worked flawlessly once again.

 

I have contacted PBI team and can hand them a sample with the problem, so they can see it for themselves that it works after removing this specific step.

 

Thank you for your help anyways.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors