Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
JustinDallas
Specialist III
Specialist III

Failed report generation for report 00000000-0000-0000-0000-000000000000

I forgot to give my version information:

  NPrinting: Version: 17.3.0.0

  QlikSense 3.1 SR1

Hello Folks,

I'm working with a Task that has a filter, and it's Report.  I'm testing the appearance, so I'm hitting the "Run Now" button so I can see what it looks like as well as the email message.

When I hit the "Run Now" button, I don't get an email, but I do see the following in the log (Sorry for the formatting):

Qlik.NPrinting.Repo 17.3.0.0 Qlik.NPrinting.Repo.Plan.ReportFailurePlanNodeExecutor 20171023T114951.063-04:00 ERROR QLIKVIEW 0 0 0 00000000-0000-0000-0000-000000000000 869e9aef-36d7-4501-8e44-e707916fdfd2 00000000-0000-0000-0000-000000000000 0 0 Failed report generation for report 00000000-0000-0000-0000-000000000000 user 00000000-0000-0000-0000-000000000000 exception System.NotSupportedException: Wrong content node response type↓↓   at Qlik.Reporting.Reports.Tree.Template.FormulaNode.ApplyEmptyResponse(EmptyContentNodeResponse response, TcTransformationContext transformationCtx)↓↓   at Qlik.Reporting.Reports.Tree.Template.TemplateLeafNode`5.ApplyResponse(IContentNodeResponse response, TcTransformationContext transformationCtx)↓↓   at Qlik.Printing.Trees.TcTransformation.ApplyResponse(IContentNodeResponse response)↓↓   at Qlik.Printing.TreeTransformationService.Process(IReportRequest reportRequest, IContentNodeResponse contentNodeResponse)

I thought maybe something might have gone awry so I regenerated the Connection, and I reset the field on my filter, making sure to use 'Numeric value is'.  However, I still get the aforementioned error.

What could I be doing wrong?  I assume that I will just have to recreate the report altogether.

1 Solution

Accepted Solutions
Ruggero_Piccoli
Support
Support

Hi,

From NPrinting 17.3 Designer Preview-Error: Wrong content node response type

The error message "Wrong content node response type" can be caused by invalid applied filters or a cycle that try to select an invalid value for the field (a value that doesn't exist in the field).

Example 1

Your source contain the Year field that contains the values 2012, 2013 and 2014 but you added a filter with Year = 2015 to the report

Example 2

you added to the report the filter Year = 2014 and the Country field into the Levels node. Remember that adding a field in the Levels node is like a filter. When the report is created it is possible that a value of Country has an empty data set for the year selected. For example, thare are not sales in Italy in 2014. This generate the error you saw.

We improved how this behaviour is managed in lates version and we are still working on it. So, first of all, upgrade your installation to September 2017 (or later when they will be available).

Then check the applied filters.

Refer also to Error "Wrong content node response type"

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT. 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.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.

View solution in original post

6 Replies
Ruggero_Piccoli
Support
Support

Hi,

From NPrinting 17.3 Designer Preview-Error: Wrong content node response type

The error message "Wrong content node response type" can be caused by invalid applied filters or a cycle that try to select an invalid value for the field (a value that doesn't exist in the field).

Example 1

Your source contain the Year field that contains the values 2012, 2013 and 2014 but you added a filter with Year = 2015 to the report

Example 2

you added to the report the filter Year = 2014 and the Country field into the Levels node. Remember that adding a field in the Levels node is like a filter. When the report is created it is possible that a value of Country has an empty data set for the year selected. For example, thare are not sales in Italy in 2014. This generate the error you saw.

We improved how this behaviour is managed in lates version and we are still working on it. So, first of all, upgrade your installation to September 2017 (or later when they will be available).

Then check the applied filters.

Refer also to Error "Wrong content node response type"

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT. 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.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
JustinDallas
Specialist III
Specialist III
Author

This is the solution.  I don't want it to be the solution, but it is.

Long story short, I had a filter that restricted records based on their [Completion Date] falling in a certain range.  If they fell into this range, I set a column (IsInWindow) to '1'.  However, none of the records ever met this requirement, so '1' was never an acceptable value for the column of

'IsInWindow'.  I do wish the system failed with a little more grace, but it's still my fault.

dwforest
Specialist II
Specialist II

So what to do if we want a blank report; I have such a need that displays YTD summaries with monthly detail. If the month has no detail, still want the YTD summary. Are you saying I'll have to build separate reports?!

Ruggero_Piccoli
Support
Support

The report will not be produced only if the dataset is empty or conditions are not met.

If you have the YTD summary it means that the applied filter for the year has a non empty dataset so the report will produced. The object with current month details can have its object filter different than the report or task or user filters.

For example:

- you apply the filter YearField = Year(Now()) to the report

- you apply the filter MonthField = Month(Now()) to the QlikView or Qlik Sense object as an object filter

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT. 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.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
dwforest
Specialist II
Specialist II

Thanks for information Ruggero!

I thought object filtering was only available for QlikView, using the object filter does exactly what i need and will help with another report I was struggling with that required different filters for different objects; Set Analysis can sometimes get you there, but this is so much easier!

Wish I could mark your response helpful, but guess that's reserved for OP only.

Ruggero_Piccoli
Support
Support

Hi,

Object filters are supported also for Qlik Sense objects starting from Qlik NPrinting September 2017. From its release notes:

Object filters for Qlik Sense charts

You can add object level filters also to Qlik Sense charts. Previously you could only add filters to QlikView charts. You can still add only one filter for each chart.

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT. 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.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.