topic Re: NPrinting ERROR: Not a legal OleAut date in Qlik NPrinting

NPrinting ERROR: Not a legal OleAut date

magnus_pm_olsso — Wed, 25 Sep 2019 18:40:54 GMT

I am experiencing a very strange error when trying to build an NPrinting Excel report. I am getting the attached error message (Not a legal OleAut date).

The absolutely strangest thing is that the error seems to be dependent on the contents of the table in the Qlik Sense app. Using the exact same report design (same expression) I can get the report to run. All is the same, just changing the underlying App script to get other content.

In this case it is an inventory report, if I just change the app script to display another warehouse everything runs.

I am completely lost and cannot fins a workaround. I have even tried to build a whole new app but as soon as I try to display this certain warehouse info I get the error.

Any help is appreciated...

Thanks

Magnus

Re: NPrinting ERROR: Not a legal OleAut date

BalaBhaskar_Qlik — Thu, 16 Aug 2018 14:01:19 GMT

May be when loading data from Data source, try like this: change the Date format in qlik sense.

Table:

Load Date,Name;

SQL

Select

to_char(Date,'DD/MM/YYYY') as Date,

Name

From ABC;

Re: NPrinting ERROR: Not a legal OleAut date

magnus_pm_olsso — Tue, 21 Aug 2018 07:04:23 GMT

Thanks for the hint, unfortunately the app or object doesn't even contain any type of date...

Re: NPrinting ERROR: Not a legal OleAut date

magnus_pm_olsso — Fri, 31 Aug 2018 12:57:37 GMT

Some further information on this issue. It seems like it has to do with a numeric field called "QtyOnhand". If I remove this field from the report, it runs without issues.

As I said, there are no dates at all in the report so the error is EXTREMELY strange. Any help would be so appreciated, I am getting nowhere with this.

Re: NPrinting ERROR: Not a legal OleAut date

jfkinspari — Wed, 19 Sep 2018 12:29:37 GMT

Hi Magnus

Did you find the reason for the error?

I'm also seeing it for a table object.

Re: NPrinting ERROR: Not a legal OleAut date

iam_hari — Thu, 27 Sep 2018 12:14:15 GMT

Hi Magnus,

Might sound a bit strange...but here is what worked for me.

In my case i had the same error, 1 dimension and 18 measures in a straight table.
I replaced the dimension with another random one, and,,,,, it worked again.
So in the end i made a duplicate from the original dimension and renamed it slightly and it works....

Not the cleanest solution but it worked for me.

good luck!

version: Qlik Sense Enterprise & Qlik Nprinting September 2018

Re: NPrinting ERROR: Not a legal OleAut date

czm — Thu, 27 Sep 2018 13:51:05 GMT

Hi Magnus,

unfortunately this is a bug of Qlik NPrinting September 2018 (also the Technical Preview is affected) that could arise with some localization settings (a double number could be wrongly interpreted as a Date, depending on the digit separator used). We are going to release a fix for this issue in Qlik NPrinting September SR2 (and it will be present as well in upcoming Qlik NPrinting November 2018).

Best regards
Carlo

Re: NPrinting ERROR: Not a legal OleAut date

tversweyveld — Mon, 01 Oct 2018 08:25:47 GMT

Hi,

Do you know when SR2 will be released?

Thanks!

Re: NPrinting ERROR: Not a legal OleAut date

czm — Mon, 01 Oct 2018 12:36:08 GMT

Hi,

I don't have any date to share at the moment unfortunately, but I suppose (just a personal educated guess) it will be available within the end of next week, depending on if we will address also another issue with it or not.

Thanks
Carlo

Re: NPrinting ERROR: Not a legal OleAut date

jorgecelis — Tue, 02 Oct 2018 14:27:50 GMT

Hello,

The same problem, a simple solution that I found is in the graphical layer of Qlik Sense, go to the graph that is failing, next go to each measure, and go to the "Number Formating" option, and select "Money" (all the measures that have the graph), then go to Nprinting and update the cache of the application that is failing, if the report is make from Pixelperfect should generate without any problem, if the report is in Excel then we go to edit the report, next select object table and deactivate the flag "keep source Formats", then apply the format to each measure as required, after this should be generated without any problem.

Re: NPrinting ERROR: Not a legal OleAut date

jorgecelis — Tue, 02 Oct 2018 14:42:05 GMT

Hello,

Re: NPrinting ERROR: Not a legal OleAut date

p_verkooijen — Mon, 08 Oct 2018 07:27:42 GMT

Hi Carlo,

Any new insights on a release date?

We have the same issue on a setup running the NPrinting Sept 2018 (18.29.7.0)

Re: NPrinting ERROR: Not a legal OleAut date

czm — Mon, 08 Oct 2018 08:29:33 GMT

Hi Paul,

as said unfortunately I don't have a release date. The build has been completed and comes with a couple of fixes (the second one delayed the release a little bit). There will be a futher system test phase probably within this week and then the public release. Probably it should be available within the end of next week.

Unfortunately I don't have (and probably won't have) any further information to share.

Best,
Carlo

P.S.: the issue is precisely on NPrinting September 2018. NPrinting June 2018 is not affected.

Re: NPrinting ERROR: Not a legal OleAut date

p_verkooijen — Mon, 08 Oct 2018 08:49:41 GMT

Hi Carlo, thnx for the response.

As mentioned we use the September release

Is there a downgrade path from September to June?

Re: NPrinting ERROR: Not a legal OleAut date

czm — Mon, 08 Oct 2018 09:32:20 GMT

Hi Paul,

no, there is no possibility to downgrade. As mentioned before the error is triggered by a double precision number within a table that due to the localization settings and the number formatting is erroneusly considered as a date.

There are two possible workarounds (I understand that could be unfeasible in some situations):
1) try a different number formatting and/or number separator (after changing the column property a reload of the NPrinting connection is needed)
2) replace the single column in NPrinting with the whole table object (eventually creating a Sense table with just the needed column), since the issue affects just column export. Also in this case the reload of the connection is needed (as well as changing the template pointing to the new object).

Given a screenshot of the table (even without headers and with all text cells blanked out) I could probably provide better suggestions.

Unfortunately the release process is outside of the control of development team, so even if we tried to speed up things I think SR2 won't be released earlier that the end of next week.

Carlo

Re: NPrinting ERROR: Not a legal OleAut date

p_verkooijen — Mon, 08 Oct 2018 09:45:07 GMT

Hi Carlo,

Thnx for the info.

Re: NPrinting ERROR: Not a legal OleAut date

marcos_herrera — Tue, 09 Oct 2018 14:40:00 GMT

Hi Carlo

Thans for the answer i have the same error with a customer afe upgrade to Qlik NPrinting Sep 2018 SR1, do you have any idea about the SR2 version release date?

Thanks

Re: NPrinting ERROR: Not a legal OleAut date

Ruggero_Piccoli — Tue, 09 Oct 2018 14:46:34 GMT

Hi,

We don't have any idea about the SR2 release date. It will be soon I think.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

Re: NPrinting ERROR: Not a legal OleAut date

marcos_herrera — Tue, 09 Oct 2018 15:31:04 GMT

Hi Friends

I have the problem with a Table (No Pivot) chart added on Qlik NP like a Table, the chart has One Dimension (Month) and six measures (Three with money format and three with number format), i'm triying assign Automatic format on each measure on the chart and then will reload the meta data and i will test the report generation

I Will comment the result

Re: NPrinting ERROR: Not a legal OleAut date

czm — Tue, 09 Oct 2018 15:41:31 GMT

Hi Marcos,

I think changing them to automatic won't change the situation but I'd be happy to be proven wrong. For sure exporting the whole table object (dragging the whole table object on the template instead of the single columns) is a possible workaround (if applicable for your situation).
Anyway the SR2 is in testing phase, when this step will be completed the release will be ready to go and this should happen soon, hopefully at the beginning of next week.

Thanks
Carlo