Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Truist_np
Contributor
Contributor

DeskTop HeapSize Changes for QlikView Task

Hello Team,

In our QlikView Environment, there are many task and one of task is failing . The error I get is as below.

Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The sourcedocument failed to reload.. Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from 

 

One of Window Desktop Heap size:

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

I got recommendation from Qlik Support to Change the desk top heap size  to 6144 or 8192.

I am going to implement this changes in Dev, Test Server first as it contains Risk. Can anyone guide what precaution and back up should I take before implementing this changes.

Thanks,

Niharika

 

1 Solution

Accepted Solutions
Lucas_Gatling
Support
Support

Niharika,

No backup necessary in  QV environment as this is a Windows Registry change. The only backup maybe I would suggest is just have a snapshot of your Windows Server environment taken prior to making the Registry change. That way if something errors out you can revert the entire server back to before the change was made.

If the issue is solved please mark the answer with Accept as Solution.

View solution in original post

1 Reply
Lucas_Gatling
Support
Support

Niharika,

No backup necessary in  QV environment as this is a Windows Registry change. The only backup maybe I would suggest is just have a snapshot of your Windows Server environment taken prior to making the Registry change. That way if something errors out you can revert the entire server back to before the change was made.

If the issue is solved please mark the answer with Accept as Solution.