Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi experts,
Why this is happening? Sometimes in production I have problem. Look, 2 hours nothing happen, then it continue...:/
Don't ask me how big app is, it is not solution.
Thanks,
Jasmina
I won't ask you how big the app is. But I will ask what the normal time is between 2 tasks?
I would advice to restart the server if this has been a while. And send logs to Qlik Support to let them see whats up.
This is nothing we on the forum can really help you with is my guess.
hehe,
Okay. No, this is one task, just sometimes stop. I cannot find what is problem. Restarting services is just partly solution...:/
This is risk for my report.
Thanks anyway,
Jasmina
Hi,
Check the Qlik NPrinting log files to see if there are more information because we have not enought details from the screenshot.
The app could be small, but check if the report template has a lot of Pages, Levels, cycles...
Be sure that all the Windows services are up and running. In particular check that the Engines are online.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.
First warning in nprinting_scheduler_log is:
Qlik.NPrinting.Scheduler 18.0.4.0 Qlik.NPrinting.Scheduler.SchedulerCore 20180810T075238.999+02:00 WARN BI Nprinting Task Identity 0 0 0 0 0 0 0 0 Engine 233fb149-df62-4787-adbb-24cf295026ec has reached heartbeat timeout. Last recorded heartbeat: 10.8.2018 5:52:21 - Offline thresold: 00:00:15
And other warnings...
Also has this:
Qlik.NPrinting.Scheduler 18.0.4.0 Qlik.NPrinting.Scheduler.Service.ContentRequestDispatcher 20180810T111500.225+02:00 WARN BI 0 0 00000000-0000-0000-0000-000000000000 0 83bdf8f4-95f9-4fb2-b23e-ef0fc40a9952 0 bca36f79-9b3f-456e-a46e-ad06dbd9175a 00000000-0000-0000-0000-000000000000 Cannot find an executor for response with request id bca36f79-9b3f-456e-a46e-ad06dbd9175a, type Qlik.NPrinting.Common.Scheduler.ArtifactGenerationResponse
Yes, this report is big, 10 pagest (take levels, take about 15 tables...)
But, this software should not have problem with size...:D
Jasmina
Hi,
In general, the software has not problem with size, but if, for example, you have not enough hardware resources, it can take a long time.
You are using 18.0.4.0. I would to suggest to keep your installation aligned with latest version in order to benefit of all solved bugs.
The message:
Qlik.NPrinting.Scheduler 18.0.4.0 Qlik.NPrinting.Scheduler.Service.ContentRequestDispatcher 20180810T111500.225+02:00 WARN BI 0 0 00000000-0000-0000-0000-000000000000 0 83bdf8f4-95f9-4fb2-b23e-ef0fc40a9952 0 bca36f79-9b3f-456e-a46e-ad06dbd9175a 00000000-0000-0000-0000-000000000000 Cannot find an executor for response with request id bca36f79-9b3f-456e-a46e-ad06dbd9175a, type Qlik.NPrinting.Common.Scheduler.ArtifactGenerationResponse
can be:
- the answer of an aborted task. I mean somebody pressed the Abort button in the task executions page
- you restarted the Scheduler service but some old stuff remained in the Messaging service queue so it re-appears. Restart also the Messaging service will remove all the old messages from the queue.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.
Don't say me that.
I made upgrade to june 2018, and it has a bugs. So I turned back to version april 2018.
June 2018 made confusion for columns. I should make again reports, exactly create new tables, then import in template.
Other problem I had, reports were failing with message (failed to render, getlayout() method time out....something like this)
What I should do now? Restart services every day?
Jasmina
Hi,
June 2018 solved the bug about columns order:
Wrong column order, colors, and hyperlinks with Qlik Sense February and April 2018
Qlik Sense tables added to report templates from Qlik Sense February and April 2018 connections, with modified column orders would generate errors. Reports would show incorrect column order, and color or hyperlinks were applied to the wrong columns.
and this bug fix will be part of all next releases.
In general, all bug investigation and fixes are done starting from latest release. So, in case you are experiencing a bug, it will be solved in a newer version. We don't add bug fixes to old versions like April 2018.
If you have other issues you need to open a support ticket by adding all the details to reproduce them, the versions of the software you are using and the log files. We cannot do a good investigation with partial log files and without a remote connection.
Of course restarting the services every day is not a solution, but we ha a lot of installations that are working without this need.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.
Thanks Ruggero,
I was writing to our regional support in Croatia, so I will wait to Monday for their response. If we don't get any feedback, I will write to official support page.
Thanks
Jasmina
Hi,
Ok. Paste the solution here if possible when solved.