Error while reloading the QlikView from publisher

[#1]

Hi all,

We are getting the below error mesage from the QEMC, while publishing the reports. This reports was working fine two days ago.  We have not made any change in the

server settings.

Please could you help us how to fix this issue.

(2012-07-03 07:58:09) Information: Failed to allocate new QlikView Engine. Retrying (2)! Current usagecount=4 of 4

(2012-07-03 07:59:09) Information: Failed to allocate new QlikView Engine. Retrying (2)! Current usagecount=4 of 4

(2012-07-03 08:01:09) Information: Failed to allocate new QlikView Engine. Retrying (2)! Current usagecount=4 of 4

(2012-07-03 08:04:10) Information: Failed to allocate new QlikView Engine. Retrying (2)! Current usagecount=4 of 4

(2012-07-03 08:08:11) Information: Failed to allocate new QlikView Engine. Retrying (2)! Current usagecount=4 of 4

Please let us know if any more information is required.

Thanks,

Sijo Joseph

[Bill_Britt]

Basically, you don't have a QVB available to do the task. If you look you can see that the 4 that is allotted is in use.

Current usagecount=4 of 4

How many processor do you have in the server?

Bill

[#3]

Thanks for the details.

Is this means we should only run 4 jobs at a time. If we run more than 4 will it fail / hang?

Please find the details updated in in our QEMC settings.

Max number of simultaneous QlikView engines for distribution - 4

Max number of simultaneous QlikView engines for administration: -20

Thanks,

Sijo Joseph

[Bill_Britt · Accepted solution]

Hi Sijo,

That is correct. However, you should only set this for the number of processors you have, but there is a limit set by Microsoft of 10. If you have more than 10 there is a registry setting that has to be changed.

Bill

[eurofactor]

Hello Bill Britt,

could you tell me which reg settings should be done?

Regards,

[Bill_Britt]

Please remember you are editing the registry and you need to make a backup before starting. I would take the time to look at the Microsoft Knowledge Base articles to get a better understanding of what you are doing.

Desktop Memory Heap Registry change:

Change the registry setting:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

Change the GDI and User handle max count in the registry to SharedSection=1024,20480,2048

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16

Default is 1024,3072,512 in x86 or 1024,20480,768 in x64

Read more on http://blogs.msdn.com/ntdebugging/archive/2007/07/05/desktop-heap-part-2.aspx

Read more about Desktop Heap on:
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx

[eurofactor]

Thanks a lot for the quick answer....

[Bill_Britt]

No problem, I hope it helps..

Bill

[Emmanuelle__Bustos]

Bill Britt

Or anyone else knows if this works for QVS 10 as well as QVS 11 ?

[Bill_Britt]

Yes, this should work on version 10 as well.