Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hei,
I have spotted that for some reason for few applications in Server that are reloaded via .cmd file in Task Scheduler the Command Prompt pop-up on trigger while for other applications the Command Prompt do not pop-up.
What could be a reason? How could I solve this issue?
The .cmd file contains this sentence:
"c:\Program Files\QlikView\Distribution Service\QVDistributionService.exe" -r="C:\QlikView\TEST.qvw" -out="c:\log\test.log"
Thank you!
Do you mean with task scheduler the windows tasks or something else? Are the cmd-files and the tasks which trigger them are really identically - sometimes there are nearly unvisible differences. To check you might copy one of the successful tasks - task + cmd - and adjust them to the unsuccessful one.
Maybe you could give some further details, for example why calling the distribution.exe (alternative would be the qv.exe) and why didn't use the qmc to trigger these tasks (directly or indirectly per execute-statement).
- Marcus
Maybe it's the call of the cmd which needs a parameter: command line - What does cmd /C mean? - Stack Overflow
- Marcus
It would be strange if the same command line works differently as the same statement works with other applications without pop'ing up the Command Prompt.
Do you mean with task scheduler the windows tasks or something else? Are the cmd-files and the tasks which trigger them are really identically - sometimes there are nearly unvisible differences. To check you might copy one of the successful tasks - task + cmd - and adjust them to the unsuccessful one.
Maybe you could give some further details, for example why calling the distribution.exe (alternative would be the qv.exe) and why didn't use the qmc to trigger these tasks (directly or indirectly per execute-statement).
- Marcus
I have copied the cmd and only changed file names.
Macrus, I have managed to export/import the task and that worked as a charm. Thank you for your insights!