topic Re: NPrinting 17.6 November - Invalid parameter : STACK : in Qlik NPrinting

NPrinting 17.6 November - Invalid parameter : STACK :

Anonymous — Wed, 07 Feb 2018 10:44:30 GMT

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:18	Warn	WARN: error during report generation: Le paramètre n'est pas valide.
7 février 2018 10:47:18	Warn	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 :

Any idea where to look at ? Thanks a lot

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Chanty4u — Wed, 07 Feb 2018 12:17:58 GMT

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 ?

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Ruggero_Piccoli — Wed, 07 Feb 2018 13:18:09 GMT

Hi,

Could you share with us the complete log in English?

Thanks,

Ruggero

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Anonymous — Wed, 07 Feb 2018 13:55:53 GMT

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==".

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Ruggero_Piccoli — Wed, 07 Feb 2018 14:29:17 GMT

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.

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Anonymous — Wed, 07 Feb 2018 15:09:07 GMT

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..

Re: NPrinting 17.6 November - Invalid parameter : STACK :

mkelemen — Wed, 07 Feb 2018 22:20:52 GMT

Hi,

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

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

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Ruggero_Piccoli — Thu, 08 Feb 2018 08:32:31 GMT

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

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

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Anonymous — Mon, 12 Feb 2018 12:53:36 GMT

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

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Ruggero_Piccoli — Tue, 13 Feb 2018 08:27:52 GMT

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

Re: NPrinting 17.6 November - Invalid parameter : STACK :

craigleach — Tue, 16 Jul 2019 18:07:45 GMT

Emerson,

Did you ever get a root cause for this issue? I have a client with the same problem, they can output a report to Powerpoint but it fails when rendering to PDF. Qlik Support has not helped solve this issue.

Thanks,

Craig Leach

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Frank_S — Tue, 16 Jul 2019 18:33:53 GMT

Hi @craigleach

I would recommend upgrading to the most recent version of NPrinting to leverage the following improvements since NP 17.6.

We are now up to NPrinting June 2019 release. Upgrading will allow you to:

leverage hundreds of documented and internal bug fixes
performance and feature enhancements
vastly improved and superior logging error information.
Upgrade information: https://support.qlik.com/articles/000050323

If your customer still has the issue following the upgrade, I would recommend starting a new support case to investigate further. However, I suspect that upgrading will in fact. solve the issue as this does sound familiar as far as previous issues go. I haven't heard this one for awhile.

All documented bug fixes and feature enhancements are available within each set of release notes for each Qlik Product release including NPrinting. These are available on the Qlik Downloads site via the Qlik NPrinting download area.

Hopefully this guides you toward ultimate resolution of the issue.

Kind regards...

Re: NPrinting 17.6 November - Invalid parameter : STACK :

craigleach — Tue, 16 Jul 2019 18:38:08 GMT

Hi Frank,

Thanks for the reply. My customer is on the latest version of NPRINTING (19.9.5.0) and still has this issue. Also, I have a case open and have not received any useful suggestions or root cause. I asked here because this is the ONLY reference I can find to this exact issue.

Thanks,

Craig

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Frank_S — Tue, 16 Jul 2019 18:47:08 GMT

Hi @craigleach

NPRINTING (19.9.5.0) is actually the April 2019 release of NPrinting.

Never the less, that should be sufficient to mitigate the issue that they are seeing. I don't see any specific bug fixes for this issue in the June 2019 (19.19.4.0) release.

PM me your case number and I'll have a look into it for you myself and suggest a course of action with the support tech that is working with you on this.

Thanks.

Re: NPrinting 17.6 November - Invalid parameter : STACK :

Frank_S — Tue, 16 Jul 2019 19:18:15 GMT

Hi @craigleach

I've reviewed your support case and would like to mention that the tech you are working with is more than eminently qualified to manage the support issue you are experiencing.

The logging in April 2019 (which you provided on the case) indicates that you may have a couple of issues which your tech has pointed out:

- possible unsupported QV items in use ie: triggers, alt states, always one selected LB or MB properties.
- possible filter conflict.

I will continue to follow the support case but would ask you to continue to work in following the support process with your tech engineer directly, toward a resolution.

Once we are able provide that, it would be greatly appreciated if you could return here to share the root cause once we are able to nail it down for you.

Thanks in advance...