There are several things you can do to troubleshoot and resolve problems before logging a case with product support. The general guidance here is designed to help you to understand the problem and know where to look for possible errors and potential solutions.

Before you call support:

If you cannot find a solution in the product help, then follow the general guidance in this topic.

Understand the problem

Understanding the problem may help you to find a solution, and will enable you to provide Qlik support with the information needed to process your case more effectively. Ensure that you understand the problem and can describe it as fully as possible before seeking further support:

Questions to ask Answers - that may lead to a better understanding of the problem
Who experienced the problem? What type of users were affected and how many?

This can help you to determine if it is a global issue, a configuration problem, a component problem, or due to user configuration.

What happened after an action was performed? Pay attention to any symptoms, behavior, and error messages.
This can help you to identify which component is causing the error, and which log files to use.
When did the problem first occur? When is it triggered, and what user action or system action causes it?
For example, a scheduled Qlik NPrinting task fails, an error is thrown when attempting to edit a template, or document metadata is not generated.
Have you experienced this issue before? If yes, how often has the problem occurred?
Where did the problem occur first? Describe where in the system or environment the problem appears?
For example, in the Qlik NPrinting Designer frontend, or in the backend (scheduler or engine).
Why do you think it happened? Gather the relevant log files. Compare log files that include the problem with those that do not.
For example, compare a successful, and unsuccessful task execution of the same report.
For log file locations, see the individual product help pages.

Use the log files

To troubleshoot and resolve issues effectively you need to understand how to use the log files. You also need to know when to use the default logs, and when to use the archived log files.

When you get an error message, the following steps can help you to identify which component has failed:

  1. Read the error message carefully as it can tell you which component has failed.
  2. Navigate to the default log files for the failed component.
  3. When you have found the correct log file, search for errors to identify the issue.

Default log files

In Qlik NPrinting, the following log files are by default stored in C:\ProgramData\NPrinting\Logs:

  • nprinting_scheduler.log - log files for scheduled tasks, and scheduled reloads.
  • nprinting_webengine.log - log files for connections to apps and Qlik Sense, QlikView servers, authentication, and licensing issues.
  • nprinting_engine.log - log files for connections to apps, licensing issues, and metadata generation.

Qlik NPrinting application problems

Other resources

Once you have gathered all the information you need, use the following links to research other possible solutions: