Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I see this in the scheduled job logs:
(+++ 06:05:41) Information: Closing the document.
(+++ 06:06:01) Warning: Could not request the QlikView Engine process to quit.
(+++ 06:06:01) Warning: The QlikView Engine isn't responding to close command, it will be killed (Please ignore logged errors about the kill).
(+++ 06:06:01) Information: Closed the QlikView Engine successfully. ProcessID=+++
Its just a warning - do I need to watch out for anything?
Hi Alexander, I am aware of that, the real reason for not updating yet has to do with other settings and task in our environment.
Another task is running but max number of simultaneous QlikView engines for distribution is set to two. We came to the conslusion the tasks are too big for running simultaneaous but if adding the key would solve the problem than that would be even better.
We are on 11.2SR5
We didnt implement the solution because the problem doesnt affect any output. Its just the job taking some time to close down.
please attach the log reloading the document
The log doesn't explain a thing. The file is available after reloading, but the problem is another file cannot depend on succesfull reload from that file as it ended without being succesful. The file is huge and was reloading during another reload of another huge file. We skipped the dependancy and started reloading after the reload of the other huge file. It is a solution acceptable for now. But if the option of adding a key in the configuration file would solve the problem, that would even be better.
The setting I described earlier is available in 11.20 SR3. I suggest you try it.
I will Magnus. I will keep you informed.
Hi Magnus,
We are currently experiencing this issue with our 2 largest applications since upgrading to QV 11.2 SR11 from QV 11.2 SR8. Is the configuration setting <add key="SECONDSTOWAITBEFOREQVBKILL" value="60" /> still valid as I do not see it in the QVDistributionService.exe.config file.
Kind Regards,
Footsie.
Yes it can still be used. And it should not be in the config file to start with since this is one of our hidden settings.
Adjust the value 60 to what is required in your environment.
Patrick, did this work for you?