0x80040E4E Error - OLE DB or ODBC

[Anonymous]

Hello all.

I have this strange error. I say strange because I can refresh the data on the Query Editor but I can't connect it to the model when I do "Apply". I get the 0x80040E4E error and I have literally no idea why. I just know it started occuring after I grabbed data from a folder and I created a function to get the filename in a column.

Any thoughts?

Thanks in advance!

ErrorFuntion

[jlopezfilizzola]

This error seems generic.

I recommend those encountering it to search for the error in their transformations or data manipulation. In my case, I had a duplicate in a one-to-many relationship field on the 'one' side, causing Power BI to flag it as an error.

The error '0x80040E4E' was displayed multiple times, while the data error was only shown once. Exporting the execution log to Visual Studio Code helped me identify and resolve the issue (on the transactional side).

[martin_mang]

Hi, 

I have the same issue. In the Power Query I am able to refresh and test the solution and as soon as I Apply changes in the main Power BI window I get these errors. 

Data model setup: 

- I am importing all data from a Jira connector. It has worked like this for years, no major SW updates have not occurred

- There are numerous transformations and calculated measures/colums done through M language and DAX

- I am using Import

- SW version 2.116.622.0 64-bit (aprill 2023)

What changes have occurred recently: 

- We removed 6 fields from the Jira datamodel on connector level and I have removed these fields from my datamodel (did it twice to make sure I did not make a mistake on the first try with the pbix file). 

- We added one new data field  in Jira and it has been made available in the datamodel.

What I have tried so far: 

- Clearing Chaces in the Desktop file. 

- Tested if I kill off a certain tables connections if this will eliminate the issue but NO. 

- Tested datatypes - most of the model is tied together with Jira Issue Key and that is as Text.

- Checked if I remove the new data field from the connector, if this rolls back the issue. But that did not change the situation. 

Any reccomendations what to try further?

[chloesouss]

I had the same issue ! Failed to save changes to the server. Error returned: "OLE DB or ODBC error: [DataFormat.Error] The external table is not in the expected format. An unexpected error occurred.  

What can i do to solve it ?

[VishaalPatel]

What worked for me was file --> options -->> Data Load --> Clear Cache on all options

[Radovan]

this worked for me,

in PowerQuery I calculate integer from datetime (example: "2023-02-07 14:08:52" = "44964")
then if i set column format in PowerBI to date i get error "0x80040E4E Error - OLE DB or ODBC"
if i set the format to whole number everything works correctly

so i guess problem is with data format...

hopefully it will help someone.

[QuantumMatrix]

Mine was a integer on my calendar table that got accidentally switched to date format.
Took me a half hour to hunt that table down and fix it.

[darrenfishell]

I'm pulling from a Dataflow and getting this same error and the same vaguely helpful error message. 

Would be excellent if the error identified the fields in question.

Whatever is going wrong here is also not being caught by Table.RemoveRowsWithErrors() either.

[divsforeal]

I had the same issue, i had duplicated a table iun power query and this issue poppedup.

It worked for me when i cleared everything in the duplicated table advanced editor and replaced the content from first table(which i duplicated from), then it worked.

Hope this helps.

[Anonymous]

I followed these steps

Step 1: Go to the Model section from the left side of the Power BI Desktop

Step 2: Delete all the relationships amongst the tables that have been created by Power BI itself while you were working with the Power Query Editor

Step 3: Click 'Refresh visual and data' option in Home (besides the Transform Data button)

It worked and loaded the new data and also applied the automations done in the query editor.

[marshow]

That did the trick! I wasn't certain how to determine which relationships were auto-created so I ended up deleting all the relationships and reconnecting only the ones I needed. The refresh went through after that - thank you!

[dovile0401]

Omg this helpes me as well! I was getting same error and each time I Refresh it occurs on different data sets. I deleted auto-created Relashionships and then the Refresh went thourgh. Thank you!

[Anonymous]

It works...!

[SQL_Injection]

This worked for us as well. In addition to the OLE ODBC error we were getting a note about not being able to find data sources we had deleted months ago and were not mentioned anywhere in the model. Thanks!

[AmyH]

This saved me so much work, thank you!

[Anonymous]

Brilliant! This worked for me. 😅

[Anonymous]

Thank you!! 

[dufu]

Hey there, I ended up through a naive search on the same issue. The 'Solution' post gave me the right indication. It turned out be cause by the filename of the csv files, I was collecting from a sharepoint. Renaming the files, using alphanumeric characters only, solved it for me.

[Anonymous]

I solved this issue ,Re-install Oracle Client 

[Anonymous]

Hi,
I came across a similar problem but its source was duplicate data on a column that created a relationship with a different table. Even worse, he didn't appear on the table causing the error.

[arslaan29]

I am trying to get data from Google Analytics to Power Bi but for page and page views field I am getting ' failed to save modifications to the sever . Error returned: 'OLE DB or ODBC error: [DataSource.Error] There was an internal error.. ;. Can you please help me with this issue