QlikView Desktop issues
QlikView instance conflict
Possible cause
Another QlikView process is already running. QV2QS requires exclusive access to QlikView Desktop for PRJ generation. The console displays Close any running QlikView instances and retry.
Proposed action
Close all running QlikView instances. If the process does not appear in the taskbar, open Task Manager and end any Qv.exe processes. Then retry the conversion.
PRJ generation times out
Possible cause
The QVW file is very large or the disk is slow. PRJ generation has a fixed timeout of 10 minutes per file. The timeout is not configurable through the CLI or wizard.
Proposed action
Verify that sufficient disk space is available, as PRJ generation requires temporary storage proportional to the QVW file size. Check that the QVW file is not corrupted by opening the file in QlikView Desktop. In batch mode, reduce the number of parallel workers with --batchWorkers 1 to free disk and CPU resources. Run with --logLevel DEBUG to capture detailed PRJ generation timing in the log file.
PRJ generation fails in batch mode with no error details
Possible cause
QV2QS cannot locate a QlikView Desktop engine. The bundled engine may not have been extracted correctly, and no system installation of QlikView Desktop is registered. Batch PRJ generation checks for an available engine before processing any files. If no engine is found, all files are marked as failed and the batch continues without PRJ folders.
Proposed action
Open the system log at %LOCALAPPDATA%\QV2QS\qv2qs.log and search for No QlikView Desktop found or Batch PRJ prerequisites. These entries record which engine was detected and whether the prerequisite check passed. If no engine is available, install QlikView Desktop on the system or verify that the QV2QS executable is not corrupted by re-downloading it. Run with --logLevel DEBUG to capture the full engine discovery path.
Could not open QVW or QVF
Possible cause
QV2QS found the QlikView Desktop engine but QlikView could not open the document. The console displays Could not open QVW or Could not open QVF followed by a diagnostic message. Three conditions produce this error:
- Section Access lockout — The document uses Section Access and the Windows account running QV2QS does not have ADMIN access in the Section Access table, or has USER access without Access Document Properties (Users) enabled in Document Properties > Security. QV2QS displays the running account (
DOMAIN\USER) in the error message. QVF files do not enforce document property restrictions, so this cause applies primarily to QVW files. - Unlicensed QlikView Desktop — A system-installed QlikView Desktop is detected but not licensed. QlikView silently refuses to open any document. This overrides the bundled pre-licensed engine because QV2QS prefers the system installation when one is registered.
- Corrupt or unreadable file — The QVW or QVF file is damaged, locked by another process, or stored on an inaccessible network share.
Proposed action
Check the error message for the most likely cause. If Section Access is indicated:
- Open the QVW in QlikView Desktop using an account with ADMIN access in the Section Access table.
- Go to Document Properties > Security and verify that Access Document Properties (Users) is enabled.
- Alternatively, run QV2QS under an account that has ADMIN-level Section Access.
If licensing is indicated, uninstall or license QlikView Desktop, or run QV2QS on a machine without QlikView installed to use the bundled pre-licensed engine.
If the file may be corrupt, verify the file by opening it directly in QlikView Desktop. Run with --logLevel DEBUG and check the log for detailed diagnostics.