not a legal oleaut date

AlexanderAT · ‎10-11-2018

Hello

I'm having a problem refreshing my report online. Everything works fine on the desktop version where I can easily update my dataset, but when uploading it and trying to refresh I get the following message:

Last refresh failed:

Data source error:	Not a legal OleAut date.. The exception was raised by the IDataReader interface. Table: ProfileScore.
Cluster URI:	WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activity ID:	d9bc7478-5268-4bda-b634-728909e93f60
Request ID:	8704eef6-6818-d9d5-fcad-ac50182d9685
Time:	2018-10-11 09:27:47Z

I have read the other post with the same issue but those solutions do unfortunately not work for me.

Anyone know how to fix this error?

Thanks

hansvanhoeij · ‎10-23-2018

Hi there,

Dit you check the actual datevalues in your table? You most probably have a date before 1/1/1900 in one of the date fields in the table you're trying to load.

Kind regards,

Hans

View solution in original post

Maryann · ‎09-20-2019

Is there a way to turn off this check. Technically they are valid dates. What if a museum wanted to categorize their artifacts by date? they can't?

Anonymous · ‎11-26-2018

Just for those who got this problem also, as i did.

As stated above, i checked my data and found 1 entry with the year 0033. Once i corrected that problem, my data refreshed OK.

Zunair · ‎06-17-2019

@Anonymous wrote:
Just for those who got this problem also, as i did.

As stated above, i checked my data and found 1 entry with the year 0033. Once i corrected that problem, my data refreshed OK.

This should be added as a #bug and be marked as error in PBI desktop since PBI service can't handle it.

Anonymous · ‎06-18-2019

Maybe, but isnt the problem the underlying data rather than the app?

@Zunair wrote:
@Anonymous wrote:
Just for those who got this problem also, as i did.

As stated above, i checked my data and found 1 entry with the year 0033. Once i corrected that problem, my data refreshed OK.
This should be added as a #bug and be marked as error in PBI desktop since PBI service can't handle it.

Maybe, but isnt it an issue with the data rather than the app?

Zunair · ‎06-18-2019

Sure the data has a problem, but it should be caught in the desktop app before it gets caught in pbi service. Especially since pbi desktop suppose to show the errors in the new error check chart.

hansei · ‎10-18-2019

I agree wholeheartedly with @Zunair . If the data is unacceptable in service, the desktop app should flag/warn/prohibit. At the same time, it would be preferable if it simply accepted valid dates.

saj · ‎03-24-2020

I agree, the error given by the Report Server (is our case) is inadequate. There is nothing other than a basic error message so it is a case of trawling through all tables with date columns!

Loading the PBIX in Power BI Desktop doesn't help too much as the refresh completes successfully.

hansvanhoeij · ‎10-23-2018

Hi there,

Dit you check the actual datevalues in your table? You most probably have a date before 1/1/1900 in one of the date fields in the table you're trying to load.

Kind regards,

Hans

JPNOP · ‎08-13-2019

Is there any way to convert dates before 1.1.1900 for the whole table? I have a bunch of tables with several columns including dates before 1.1.1900. Those dates come straight from ERP database and most of those cannot be changed in ERP GUI, (without manipulating the database).

Maybe some power query string? Table.ReplaceValue ?