QlikView Navigator process stuck messages
Last updated: 7/31/2026Possible cause
A QlikView process health check generates a report if there are processing errors that cause excessive CPU usage. When this happens, the process is monitored and terminated if it appears locked.
Example error state messages:
2015-12-02 18:13:58,935 [34] WARN Engine.Navigator.QlikView.QV11.QlikViewNavigator.[25064]::navigator=qlikview;documentpath=C:\nprinting\global\dashboard.qvw - QlikView CPU monitor: process seems stuck due to cpu usage of 76.05 % in 1238ms. Waiting for idle for 2000ms
2015-12-02 18:13:59,111 [34] WARN Engine.Navigator.QlikView.QV11.QlikViewNavigator.[25064]::navigator=qlikview;documentpath=C:\nprinting\global\dashboard.qvw - QlikView CPU monitor: process is stuck due to cpu usage of 65.00 % in 1414ms
Back to normal message:
2015-12-02 18:13:59,111 [34] WARN Engine.Navigator.QlikView.QV11.QlikViewNavigator.[25064]::navigator=qlikview;documentpath=C:\nprinting\global\dashboard.qvw - QlikView CPU monitor: process returned to normal a normal cpu usage of 12.06 % in 1302ms
Proposed action
This situation is expected to correct itself. If the monitor shows normal usage, nothing is performed, otherwise QlikView is closed and reopened to allow further report generation. If you continue to get error messages for the same document, check that the connected QlikView documents are accessible by the Qlik NPrinting Engine. Also check that no errors occur when you open the document in QlikView manually.