Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
While preparing to upgrade Qlik Nprinting a number of our reports were sent via Nprinting without a trigger for that date and time. For example, one report was sent at 8:30pm (as per the trigger) but was then sent again 3 times at 9:06pm. There is no record of these executions in the Task list. A few other reports were sent that had triggers for a different day and time.
Does anyone have any ideas on why this would happen?
Thanks,
Peter
Ok so in that case, there might be another NP server running in your environment. Its possible that someone has recently spun up or re-enabled server with NPrinting running on it that had been turned off for some time perhaps.
I would suggest checking into that as this is not entirely unique.
NPrinting otherwise will not execute publish tasks or other executions without recording them in the task executions page.
Kind regards...
In the past when reports are unexpectedly delivered, this has indicated that another NP server, perhaps a test server, might be running on your premise.
To check for executions on your known NPrinting server, you can check the 'executions' link in the NPrinting web console.
All task executions are shown here, even those enable by an external API.
Kind regards...
Hi Frank,
I have checked the task executions and none of these reports appear in either test or production. There is nothing listed after 8:30pm which was the last scheduled Nprinting execution of the day.
Thanks,
Peter
Ok so in that case, there might be another NP server running in your environment. Its possible that someone has recently spun up or re-enabled server with NPrinting running on it that had been turned off for some time perhaps.
I would suggest checking into that as this is not entirely unique.
NPrinting otherwise will not execute publish tasks or other executions without recording them in the task executions page.
Kind regards...
Thanks Frank - I will talk with the infrastructure team who were performing the upgrade to see if this could be the cause