Reply
Member
Posts: 68
Registered: ‎05-26-2017

Re: Not a legal OleAut date..

I cannot thank you all enough...was tearing my hair apart 

 

Didnt understand why query would run on sql , refresh locally and then fail in the gateway

 

it was indeed dates

 

 

Thanks again

 

 

Occasional Visitor
Posts: 1
Registered: ‎10-31-2018

Re: Not a legal OleAut date..

[ Edited ]

Solution:

I had the same issue 

Data source error:Not a legal OleAut date.. The exception was raised by the IDataReader interface. Table: ...

In my case the issue of updating data set was:


in one table with Customers data we had birthday date - in date format obviously.

some of dates were incorrectly filled with data earlier than 1/1/1900 (for example "1/30/0992"

after filtration of the filed issue disapired.


looks like it some data filed parameter - which doesnot read that type of dates.
hope that helps

Highlighted
Frequent Visitor
Posts: 11
Registered: ‎01-23-2017

Re: Not a legal OleAut date..

Hi All,

 

I had the same problem -- but wasnt able to easily identify the root cause, since there were many dates that were at extreme ends of the range (e.g. Year 0001 or year 9999)

 

This is what I did to fix it:

  1. Added a custom column in the with the following formula:
    NewColumn = Number.From([Due Date])
  2. Convert custom column to decimal number
  3. Sort the table by this column

 

This then gave the following error, which I could use to identify the problematic records in the table:

 

Date Error.png

 

I hope this helps someone else.