Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
10 years ago

Not a legal OleAut date..

Getting the following error while refreshing from an Oracle DB using the Gateway refresh...   The following exception occurred while the managed IDataReader interface was being used: Not a legal Ol...
Anonymous's avatar
Anonymous
Not applicable
8 years ago

This has been a very frustrating few days before and after Christmas figuring out why a dataset refreshes fine in Power BI Desktop but fails on the cloud service with the useless message "The gateway operation has been cancelled explicitly by the user or from a timeout." On another message thread for that language, there were suggestions about gateway issues and join cardinality, so all our time was spent chasing down that route. It took me rebuilding the dataset from scratch one table at a time, publishing to the service each time I added a table, then refreshing from the service, to find the culprit table, but I was still getting the wrong "timeout" message. So I created a dataset with just the one faulty table, and the error message finally changed to the helpful "not a legal OleAut date" message. Then, thanks to you guys, it was a quick fix to handle years 0016 and 0017 from the ERP.

svishwanathan's avatar
svishwanathan
Helper III
8 years ago

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

 

 

  • Evgeniy_A's avatar
    Evgeniy_A
    New Member
    7 years ago

    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

    • muneern's avatar
      muneern
      Frequent Visitor
      7 years ago

      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:

       

       

      I hope this helps someone else.