QlikView QMC command line execution stopped working

[SweJoCa]

Hi guys, 

I'm having a "massive" problem with an ETL that stopped working. 
I have two environments, one of them "Prod" and the other "Test". 
The "Test" environment has a "Test-edition" license (if this is relevant, I don't know)
This environment was recently updated to september 2025 SR1.
After that, one of the things happening was that a step in the ETL keeps failing, namely a task that utilises a command line as follows: 
"C:\Program Files\QlikView\QV.exe" "D:\QV\Production\Cobra\Binary\Cobra_Binary_Load_Export.qvw" /r
It is supposed to start a QV document at reload it. The document is a "simple" export task. 

I cannot for my life understand why the updating stopped the command line execution? 

Cheers
Jörgen

[marcus_sommer]

Was it a pure upgrade of the QV release or were there other changes, too? As far as other things were touched, like the OS/machine/VM/network ... there are a lot of possibilities. If so and there is a way to rollback to the previous state you should go with it and then changing everything step by step to reduce the complexity of the troubleshooting.

Beside this you need to monitor the failing process in more details respectively where does it fail? Is the trigger for the cmd executed and then the cmd did run and then the qv.exe was called and then the qvw opened and then the macro were called which may open an Excel ... 

[SweJoCa]

This was a pure upgrade. 
No changes to anything else. 
I do have a suspicion about the license - which is a test license that will not allow leasing the license at all. 
Here's the error message for that, if it can be of any lead: 

(2026-02-12 06:02:49) Information: The task "4 och 3b Cobra_Binary_Load_Export Reload (export PFR)" is starting

(2026-02-12 06:02:49) Information: Executing "C:\Program Files\QlikView\QV.exe" "D:\QV\Production\Cobra\Binary\Cobra_Binary_Load_Export.qvw" /r

(2026-02-12 06:02:49) Information: Executing commandline: "C:\Program Files\QlikView\QV.exe D:\QV\Production\Cobra\Binary\Cobra_Binary_Load_Export.qvw /r" in folder "C:\Program Files\QlikView".

(2026-02-12 06:20:58) Error: The process exited with non-zero ExitCode (-1073741819) at 2026-02-12 06:20:57

(2026-02-12 06:20:58) Error: The task "4 och 3b Cobra_Binary_Load_Export Reload (export PFR)" failed. Exception: || QDSMain.Exceptions.TaskFailedException: The process exited with non-zero ExitCode (-1073741819) at 2026-02-12 06:20:57 || at QDSMain.ExternalProgramTask.Execute(IExecutingTaskResult executingTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(CurrentExecutionArgs args)

[marcus_sommer]

To ensure that really the QV.exe caused the exit-code take a look if it has run - initialising a new session and then failing to open the qvw - or not. If it didn't run the system-access to QV has failed and if it run a license issue is likely (nevertheless there are further possibilities like the file-access is really forbidden or any section access or ...).

The license matter might be checked by calling the cmd manually - login with the service user and then executing it as batch-file. By changing the parameter from /r to /l may give further insights and messages because it's not a background-process anymore else opened the GUI (and left it open afterwards). A next step may be to licence the desktop client manually or fetching the licence from the productive system.

More suitable would be to contact Qlik to get a temporary migration-licence. The use of a test-license is very sensible but depending on it's limitation it wouldn't allow a complete environment-check.