topic Re: Execution startup failed: Identity Parameter name: Missing parameter - Error in Qlik NPrinting

Execution startup failed: Identity Parameter name: Missing parameter - Error

Gabo77 — Fri, 15 Nov 2024 21:17:24 GMT

Hi guys... i have an error with NPrinting Job. This used to work with no issues but, suddenly it showing the "Execution startup failed: Identity Parameter name: Missing parameter" error message.

We have some others jobs working with no issues,that sends reports even to same users that the job with error... so,i cant find why is i'm getting this error.

Regards!

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Lech_Miszkiewicz — Mon, 06 Nov 2023 23:48:59 GMT

Hi @Gabo77

There are no "Jobs" in NPrinting May 2021 - are you refering to task?
1. Is that what you see in Task Execution Log?
2. What do you see in Engine log (use https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/Introduction/Introduction.htm to study where logs are)
Have you regenerated metadata sucessfully for the connection(s) used in this report?
Are you able to sucesfully run "Preview" of the report in NPrinting designer?
Have you got all entities in your report?
What has changed?
1. Did you upgrade Qlik Sense/QlikView?
2. Are you running supported configuration as documented on https://help.qlik.com ?
  1. this is always major issue which is often neglected - people setup unsupported configurations and when sudenly it stops working they are surprised. Help site provides detailed and long instructions on what is and what isn't supported
  2. the above comment relates also to the way your Qlik app is build and how objects used in your report are built

From your description it is not clear what could cause such error. We dont know anything about your setup, report template, filters/conditions used so we can only give you high level information what to check and I always start from the very basics - is everything built in supported manner. Check that and see how you go.

cheers

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Frank_S — Tue, 07 Nov 2023 18:23:55 GMT

Further to Lech's points, it is also possible that your source data has changed.

See articles below how to resolve that problem:

If the object ID has changed in any way, then you may need to replace the object in the NPrinting report with a new NPrinting tag from the updated table object.

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Gabo77 — Tue, 07 Nov 2023 22:26:24 GMT

Hi Lech... Thanks for you replay... i attached my responses in red.

There are no "Jobs" in NPrinting May 2021 - are you refering to task? - Yes, NPrinting execution task.
1. Is that what you see in Task Execution Log? - Yes... only that error message
2. What do you see in Engine log (use https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/Introduction/Introduction.htm to study where logs are) - I followed the LOG Engine instructions but, i was not able to enable it 😞
Have you regenerated metadata sucessfully for the connection(s) used in this report? - Yes, i recently do it without issues.
Are you able to sucesfully run "Preview" of the report in NPrinting designer? - Yes, it's working fine.
Have you got all entities in your report? - Yes, i generated a TEST Task to check if it works for my user onlye, and it works fine. From here, i assume that theres something with users or groups that are generating the issue.
What has changed? - Before the issue, nothing was changed.
1. Did you upgrade Qlik Sense/QlikView? - Nop
2. Are you running supported configuration as documented on https://help.qlik.com ? - The configuration was made 2 year ago, and it was working with no issue, no changes was made before this issue.
  1. this is always major issue which is often neglected - people setup unsupported configurations and when sudenly it stops working they are surprised. Help site provides detailed and long instructions on what is and what isn't supported
  2. the above comment relates also to the way your Qlik app is build and how objects used in your report are built

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Gabo77 — Tue, 07 Nov 2023 22:29:57 GMT

Hi Frank... i understand but... this can happens even if i'm able to execute "Preview" from "NPrinting Designer"??

Thanks in advance.

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Lech_Miszkiewicz — Tue, 07 Nov 2023 22:43:04 GMT

Hi @Gabo77

Thanks for your answers.

Have you checked this thread: https://community.qlik.com/t5/Qlik-NPrinting/Qlik-Nprinting-task-failed-with-error-Fatal-Execution-startup/td-p/2081492 ?

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Gabo77 — Wed, 08 Nov 2023 15:27:08 GMT

Hi Lech... Thanks for response...

Yes, i had already read it... but i dont know if this is my case. All users are a "real users" not only to deliver the reports... also, all my users in all my other taks has the "User" role assigned to each; in fact, all my users has the "NewStand User" and "User" roles assigned to each, and all other reports are working fine...

Regards!

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Frank_S — Wed, 08 Nov 2023 16:26:02 GMT

The entity checker only checks that the existing entities match.

It does not check if underlying formulas in a table column have changed/updated.

So you need to update each table individually as described in the links shared previously.

Kind regards,...

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Gabo77 — Mon, 13 Nov 2023 14:32:27 GMT

Hi all... finally found the reason for the issue.

For another report (only related to this report by the application) we need to implement "Section Access" process in order to filter data for some users, so we need to set the domain for these users. These users are selected for the report with error, in addition to others who do not have the domain configured... So, for some reason, qlik does not support to merge users with and with not domain setted on its parameters. Even when we have some other reports with this kind of merge, only this report causes error... By the way, the report with error, doesnt implement "Section Access" methods.

Thanks for all.

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Lech_Miszkiewicz — Tue, 14 Nov 2023 01:36:51 GMT

Well, thanks for sharing details of your scenario. You have touched very important thing which is realising that any change to source application can affect other reports. I always say that most of NPrinting development is based on properly planned and executed Qlik app development. It looks like maintanance of the app is also same important.

Section access requires domain account properly configured, as that is the only way NPrinitng can apply section access, right? So there is no surprise there that if you have section access you must provide users with domain account to be used for that section access process. If you are using the same set of users for other reports without section access then obviously domain account parameter does not have to be checked as it is not required when creating NPrinting report.

I guess the usual take away from here is answering the question: "What has changed recently which could cause this issue?". You would be able to troubleshoot it straight away once you would ask yourself that very question, right? (unless you were unaware about addition of section access)

anyway - I am glad you got this one solved.

cheers

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Gabo77 — Wed, 15 Nov 2023 16:45:35 GMT

Hi Lech... in my office, only i have access to modify Qlik reports and NPrinting tasks, but, in honor of the truth, the design for the Apps and Connections is one of out issues... This is because i simple followed the steps that i received in order to create my reports. I mean, when I was incorporated into the world of Qlik, my instructor created all our reports on the only 1 existing app, and didn't tell me anything about the risks or things to consider when doing this.

So, i believe that my next steps is to reorder all my scnearios... 😞

Re: Execution startup failed: Identity Parameter name: Missing parameter - Error

Lech_Miszkiewicz — Wed, 15 Nov 2023 22:30:19 GMT

Hi @Gabo77 - well - this is tough one as I assume you are not experienced Qlik Sense/NPrinting developer and you are learning those things on "life" environment. If that is the case - I dont blame you and I can only suggest few small tips":

looking at all your reports check if all your reports use the same connection to Qlik app. You can use many connections to the same Qlik app to maintain what is filtered in each of them.
1. you dont need to use section access for Nprinting reports - you can replace section access with user filters and to be honest that would resolve issue with your missing domain account. You would however need to have one admin user in your section access with access to all data and that user would need to be used as identity on NPrinting connection
2. when developping I usually work of the copy of the Qlik app (if you dont have dedicated Qlik DEV server) and in NPrinting i also create separate connection to such app so I can develop independantly from PROD solution (without DEV environments). Once you confirm that everything works you could just export/import-replace report in NPrinitng console.
3. Note that you can export reports in NPrinting console for backup purposes (it is good practice to do that before making any changes to template)
4. I also do daily snapshots of NPrinting repository so there is always an option to roll everything back - details how to do that are on help site
If you have many reports which have to have different user filters it is good practice to split connections (create separate NPrinting connections for them)
Even though there is section access in Qlik app you dont need to use in NPrinting. You can replicate its behaviour by applying user filters. It is actually more efficient way from report generation speed perspective.

Anyway - you probably do most of this anyway, but I just thought I would put it here in case someone tries to figure out what to do in similar situation.

good luck.

cheers