topic Re: not a legal oleaut date - cannot refresh in Report Server

not a legal oleaut date - cannot refresh

AlexanderAT — Thu, 11 Oct 2018 09:40:08 GMT

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

Re: not a legal oleaut date - cannot refresh

hansvanhoeij — Tue, 23 Oct 2018 09:42:54 GMT

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

Re: not a legal oleaut date - cannot refresh

Anonymous — Mon, 26 Nov 2018 10:36:50 GMT

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.

Re: not a legal oleaut date - cannot refresh

Zunair — Mon, 17 Jun 2019 15:58:25 GMT

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.

Re: not a legal oleaut date - cannot refresh

Anonymous — Tue, 18 Jun 2019 09:38:55 GMT

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?

Re: not a legal oleaut date - cannot refresh

Zunair — Tue, 18 Jun 2019 12:43:59 GMT

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.

Re: not a legal oleaut date - cannot refresh

JPNOP — Tue, 13 Aug 2019 08:47:49 GMT

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 ?

Re: not a legal oleaut date - cannot refresh

Anonymous — Tue, 13 Aug 2019 08:58:23 GMT

JPNOP

I would use switch for that:

https://docs.microsoft.com/en-us/dax/switch-function-dax

In that scenario you could simply replace any value before or on that date and then specify what you want as an output :)

Hope that makes sense

Re: not a legal oleaut date - cannot refresh

Maryann — Fri, 20 Sep 2019 15:11:29 GMT

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?

Re: not a legal oleaut date - cannot refresh

hansei — Fri, 18 Oct 2019 19:41:43 GMT

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.

Re: not a legal oleaut date - cannot refresh

saj — Tue, 24 Mar 2020 10:08:56 GMT

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.