Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Error while reloading the QlikView from publisher

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

12 Replies
Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist

Ok, thank you in advance Bill 

Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist

Hi Bill,

It's me again with a question about this old issue and related to OS Windows Server 2012 and 2012R2. I checked that the registry setting has the same values:

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

So I think we should do the same changes to Windows SharedSection=1024,20480,2048 when using this OS.

But I just want to make sure about this, have you ever made this change?

pat_agen
Specialist
Specialist

Hi Emanuelle,

this is a pretty old post but we just hit the same issue whilst migrating versions and servers, and in this case moving to a Windows Server 2012 R2.

Registry value has the default value as described above and changing it resolved the issues we were having when trying to run multiple concurrent tasks out of QMC.