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: 
Anonymous
Not applicable

NPrinting 17.6 November - Invalid parameter : STACK :

Hello,

Since I upgraded NPrinting from 17.3 to 17.6 November, the report generation does not work anymore

The metadata have been reloaded (local mode)

I got this message :

7 février 2018 10:47:18WarnWARN: error during report generation: Le paramètre n'est pas valide.
7 février 2018 10:47:18WarnFailed report generation for report 049b9e72-a823-4bb5-a578-0774256bee21 user 9e9c57b7-d8d7-4acf-9c62-ea9d97002276 exception System.Exception: Le paramètre n'est pas valide. : STACK :

Any idea where to look at ? Thanks a lot

14 Replies
Chanty4u
MVP
MVP

is connection?

app?

reports all are available after upgrade ?

did you check ?  

if yes it will work orelse 

try to create app and connection report  for testing purpose and see is it working or not ?

Ruggero_Piccoli
Support
Support

Hi,

Could you share with us the complete log in English?

Thanks,

Ruggero



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.
Anonymous
Not applicable
Author

Thanks for your help !

Report work when I generate them using the Designer

Here is scheduler log :

Qlik.NPrinting.Repo 17.6.0.0 Qlik.NPrinting.Repo.Plan.ReportFailurePlanNodeExecutor 20180207T143428.316+01:00 ERROR SAG-QNP 0 0 0 9891fa7b-3203-4511-8c99-f7ccaf677792 cee7c39e-c125-4d92-afa0-fe026d39065f 049b9e72-a823-4bb5-a578-0774256bee21 0 0 Failed report generation for report 049b9e72-a823-4bb5-a578-0774256bee21 user 9e9c57b7-d8d7-4acf-9c62-ea9d97002276 exception System.Exception: Le paramètre n'est pas valide. : STACK :

Here is the engine log :


Qlik.NPrinting.Engine 17.6.0.0 Qlik.NPrinting.Engine.Consumer.ContentResolver 20180207T144717.090+01:00 WARN SAG-QNP 0 0 0 0 0 0 0 0 Navigator stuck or died on connection navigator=qlikview;documentpath="qvp://***.qvw";username=***;encryptedpassword="FweQUvUnu9LE1oVQNSv/zg==", forcing close of resolver. 1 unprocessed request(s) will be reenqueued. ERROR: Navigator navigator=qlikview;documentpath="qvp://***.qvw";username=***;encryptedpassword="FweQUvUnu9LE1oVQNSv/zg==" process died or has been terminated and can't be used anymore to resolve requests. Stack trace:    à Engine.Navigator.QlikView.QV11.QlikViewNavigator.Qlik.Printing.IContentNavigator.Filter(IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewNavigator.cs:ligne 197↵↓   à Qlik.NPrinting.Engine.Consumer.ContentRequestExecutor.ApplyFilters(IContentRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine\Consumer\ContentRequestExecutor.cs:ligne 107↵↓   à Qlik.NPrinting.Engine.Consumer.ContentResolver.Consume(CancellationToken cancToken) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine\Consumer\ContentResolver.cs:ligne 170. Inner exception: System.Runtime.InteropServices.COMException (0x80004005): Une erreur HRESULT E_FAIL a été retournée à partir d'un appel à un composant COM.↵↓↵↓Server stack trace: ↵↓   à Qlik.QlikView11.Doc.ClearAll(Boolean _LockedAlso, String _StateName)↵↓   à Engine.Navigator.QlikView.QV11.QlikViewDocument.ClearSelections() dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewDocument.cs:ligne 1173↵↓   à Engine.Navigator.QlikView.QV11.Resolvers.Filters.ClearAllSelectionsRequestResolver.Resolve(QlikViewDocument doc, ClearAllSelectionsRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\Resolvers\Filters\ClearAllSelctionsRequestResolver.cs:ligne 23↵↓   à Engine.Navigator.QlikView.QV11.Resolvers.Filters.BaseFilterRequestResolver`1.Engine.Navigator.QlikView.QV11.Resolvers.Filters.IFilterRequestResolver.Resolve(QlikViewDocument doc, IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\Resolvers\Filters\BaseFilterResolver.cs:ligne 50↵↓↵↓Exception rethrown at [0]: ↵↓   à System.ExceptionExtensions.Rethrow(Exception this) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Qlik\Qlik.Reporting.Common\System\ExceptionExtensions.cs:ligne 119↵↓   à Engine.Navigator.QlikView.QV11.Resolvers.Filters.BaseFilterRequestResolver`1.Engine.Navigator.QlikView.QV11.Resolvers.Filters.IFilterRequestResolver.Resolve(QlikViewDocument doc, IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\Resolvers\Filters\BaseFilterResolver.cs:ligne 62↵↓   à Engine.Navigator.QlikView.QV11.QlikViewNavigator.Qlik.Printing.IContentNavigator.Filter(IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewNavigator.cs:ligne 195. Inner stack trace: ↵↓Server stack trace: ↵↓   à Qlik.QlikView11.Doc.ClearAll(Boolean _LockedAlso, String _StateName)↵↓   à Engine.Navigator.QlikView.QV11.QlikViewDocument.ClearSelections() dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewDocument.cs:ligne 1173↵↓   à Engine.Navigator.QlikView.QV11.Resolvers.Filters.ClearAllSelectionsRequestResolver.Resolve(QlikViewDocument doc, ClearAllSelectionsRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\Resolvers\Filters\ClearAllSelctionsRequestResolver.cs:ligne 23↵↓   à Engine.Navigator.QlikView.QV11.Resolvers.Filters.BaseFilterRequestResolver`1.Engine.Navigator.QlikView.QV11.Resolvers.Filters.IFilterRequestResolver.Resolve(QlikViewDocument doc, IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\Resolvers\Filters\BaseFilterResolver.cs:ligne 50↵↓↵↓Exception rethrown at [0]: ↵↓   à System.ExceptionExtensions.Rethrow(Exception this) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Qlik\Qlik.Reporting.Common\System\ExceptionExtensions.cs:ligne 119↵↓   à Engine.Navigator.QlikView.QV11.Resolvers.Filters.BaseFilterRequestResolver`1.Engine.Navigator.QlikView.QV11.Resolvers.Filters.IFilterRequestResolver.Resolve(QlikViewDocument doc, IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\Resolvers\Filters\BaseFilterResolver.cs:ligne 62↵↓   à Engine.Navigator.QlikView.QV11.QlikViewNavigator.Qlik.Printing.IContentNavigator.Filter(IFilterRequest request) dans c:\Jws\workspace\NP-REL-17.6.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewNavigator.cs:ligne 195.

Qlik.NPrinting.Engine 17.6.0.0 Qlik.NPrinting.Engine.Consumer.ContentResolver 20180207T144717.090+01:00 INFO SAG-QNP 0 0 0 0 0 0 0 0 Forced to close a resolver for connection navigator=qlikview;documentpath="qvp://***.qvw";username=***;encryptedpassword="FweQUvUnu9LE1oVQNSv/zg==".

Ruggero_Piccoli
Support
Support

Hi,

The scheduler log was generated at 20180207T143428. The engine log was generated at 20180207T144717, 13 minutes later. Could you check and share the logs at the same time? Or attache the files. Thanks.

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.
Anonymous
Not applicable
Author

Hello,

It seems that I found the source of the error. It's the PDF generation.

The tasks work well when I set the output format to XLSX but failed when I set it to PDF...

Thanks for your help, I now need to find why the PDF generation is not working..

mkelemen
Creator III
Creator III

Hi,

I get the same error in 17.5 and it is caused by missing connection in page and level.

screen1.JPGscreen2.JPG

The fields exist and are visible to the NP user but I do not see them in NP anymore.

When I remove them the report runs.

BR,

  Matus

Ruggero_Piccoli
Support
Support

PDFs from Microsoft Office template are generated by an internal component, not by external PDF printer. So, if you have issues in generating PDF reports from Office templates, I suggest you to open a support ticked. Colleagues will help you to investigate.

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.
Anonymous
Not applicable
Author

I tried this but it didn't fix my problem. Thanks for the intervention.

Ruggero_Piccoli
Support
Support

If you are still having the issue, please open a support case.

When solved, if the solution is useful for the whole community, please share it here.

Thanks



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.