Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We had a problem recently in one of our QlikView environments where the Tasks (in QMC) would appear to be running but not actually doing anything. By looking at Task Manager on our Publisher server I quickly found that there were 10+ qvb.exe's although there was only one task running in QMC. We stopped / started QlikView Distribution Service causing these orphaned qvb.exe's to be killed and then the genuine jobs could run as they were no-longer waiting behind a stuck queue.
We have 10 "Max number of simultaneous QlikView engines for distribution".
Has anyone else experienced similar issues? Does anyone know why qvb.exe's are likely to become orphaned? Other than regular restarts of QlikView Distribution Service is there anyway to prevent this happening again?
We will be raising a case with Qlik but I've always found the community a better resource so I'm asking here.
Hi
we are running Windows Server 2008 R2 64 Bit, what is your system?
By means of a registry change on the server, number of max. simultanous QVB.exes can be increased.
The change is described in this thread:
http://community.qlik.com/message/203910#203910 at bottom, (SharedSection=1024,20480,2048 instead SharedSection=1024,20480,768)
We have applied this change on our server, with very good experience!
However, note that every change in the server registry must be done very carefully and properly prepared & analysed.
You will have to re-setup your server if you enter any wrong values, because of possible crash at next system startup.
Regards - Marcel
Hi Shane
Which version are you running? We did a fix in this area which was released in 11.20 SR6.
Good that you will open a case where we can analyze why this is happening in your enviroment.
Hi Marcel. I've seen that thread. We don't require more simultaneous reloads, the issue is with the QVB.exe's becoming orphaned.
We're on version: Client Build Number 11.20.12577.0
This means you have the fix that was made. Please report this issue to Qlik Support.